×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Connecting indi via Bluetooth to a computer

  • Posts: 152
  • Thank you received: 28
Hi tseckler, I just checked to make sure the service for enabled, it was. Still the same issue. The port auto binds but when i try connecting to it in ekos, the port is unresponsive. I checked on my server to make sure the bt was connected and the bt manager shows a perfect connection??? Very weird.

Could it have anything to do with my auto indi server startup? Could it be an issue with the order in which things start up? To start up my indiserver automatically i did this:

Set up Rpi3 to Automatically Start indiserver

Connect all equipment to the rpi3 (heq5, guider, ccd, focuser etc etc) and power up rpi3. You will notice that the BT adapter’s red LED flashes which means it is NOT connected to the rpi3 yet.

To start indiserver automatically, open a terminal and type:

sudo pluma /lib/systemd/system/indi.service

and add the following to the file:

[Unit]
Description=Start INDI server at startup.
[Service]
User=username
Group=usergroup
Type=simple
Restart=always
ExecStart=/usr/bin/indiserver indi_eqmod_telescope indi_asci_ccd indi_gphoto_ccd indi_joystick
[Install]
WantedBy=graphical.target
WantedBy=multi-user.target

and save the file and then activate is via

sudo systemctl enable indi.service
6 years 9 months ago #17272

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
Pair and connect BT Adapter
To the file /etc/rc.local add this line of code.
Don't miss the trailing & in this code and sub XX's for adapter MAC address.
rfcomm bind hci0 XX:XX:XX:XX:XX:XX 1 &
6 years 8 months ago #17880

Please Log in or Create an account to join the conversation.

  • Posts: 125
  • Thank you received: 24
Sorry to revive this thread. I tried all the steps mentioned above and but i am unable to get the mount connected on ekos . Could some one suggest what I am doing wrong here.

Trying to connect BT2EQ6 on astroberry@RPI3

Attached screenshot of the error log
6 years 3 months ago #21516
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
I'm not sure. It should be available on rfcomm0
6 years 3 months ago #21527

Please Log in or Create an account to join the conversation.

  • Posts: 281
  • Thank you received: 29
Hi, I have tried all the different approaches as described in this thread, but got the same error message as described by tkottary.

I am also using the Rpi3, with the Shoestring BT adapter for the EQ6.

Would be great if someone with similar set up could describe once again how to set up!

Thanks in advance, Helge
6 years 2 months ago #22558

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
The last time I tried my Bluetooth adapter was after I remade it. I encountered that error and left it at that for the time being, assuming I made a mistake. But perhaps there is a bug?
Last edit: 6 years 2 months ago by Andrew.
6 years 2 months ago #22559

Please Log in or Create an account to join the conversation.

  • Posts: 281
  • Thank you received: 29
Hi Ilhoujin,

Thanks for responding! Are you also using the Shoestring BT Adapter? If I may ask, in one of your previous posts you were suggesting to add a 1 and the & behind the MAC address, -what is the purpose of the „1“?

Anyway, sounds like your solution was working, but not anymore - so it might really be a sort of „bug“.

Best, Helge
6 years 2 months ago #22560

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
Well I can't be sure if my problem was hardware or software because I rebuilt the device, and encountered frustrations.
I don't recall the full syntax reasoning for the 1. But the trailing & is required to allow the Pi to continue to complete the boot, because commands in rc.local are run at boot time and will hang on them while waiting.
The following user(s) said Thank You: Tarun
Last edit: 6 years 2 months ago by Andrew.
6 years 2 months ago #22561

Please Log in or Create an account to join the conversation.

  • Posts: 125
  • Thank you received: 24
In my case problem was Blueman . It was auto connecting the device on boot. So I made sure on reboot it wasn't auto connecting. Blueman was used only once to pair the device .

Now I run this below script after Login

sudo rfcomm bind hci0 <your mac address> 1
sleep 5
sudo chown <username> /dev/rfcomm0

also to note when i put the above script to invoke from my rc.local device wasnt wasn't connecting to mount ;that is something i need to investigate further. Hope this helps.
The following user(s) said Thank You: Jasem Mutlaq, Scott Baker
Last edit: 6 years 2 months ago by Tarun.
6 years 2 months ago #22567

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
My guess as to why it didn't work in rc.local is the absence of the trailing & character
6 years 2 months ago #22583

Please Log in or Create an account to join the conversation.

  • Posts: 281
  • Thank you received: 29
When just capturing the script line by line into the terminal, it works - which is a big relief!

But same is not working just from the rc.local.
6 years 2 months ago #22608

Please Log in or Create an account to join the conversation.

  • Posts: 281
  • Thank you received: 29
Would anyone happen to know how binding Bluetooth upon start up? Tried including the commands (bind, chown) in rc.local, but that does not work, just via terminal commands.

Or should I save script as a program and invoke via launcher?
6 years 1 month ago #22750

Please Log in or Create an account to join the conversation.

Time to create page: 0.450 seconds