×

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

Bi-monthly release with minor bug fixes and improvements

Keep getting 'device or resource busy' error when connecting

  • Posts: 16
  • Thank you received: 0
The steps I mentioned are in an old laptop using Ubuntu Mate 16.04.
I also have a StellarMate. Which uses a Raspberry Pi. On that one everything works. Probably because all the software was installed and tested at the factory. It also has Ububtu Mate 16.04. If you give up maybe you'd like to buy a StellarMate. They are not expensive and they ship them quickly.
6 years 3 weeks ago #23834

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

  • Posts: 1309
  • Thank you received: 226
The command for rc.local is
rfcomm bind hci0 xx:xx:xx:xx:xx:xx 1 &
I found no need to uninstall bluetooth manager, and you do have to make certain the dongle is paired.
Check that rfcomm0 is active with
ls -l /dev/
And make sure the INDI driver is set to connect to /dev/rfcomm0
6 years 3 weeks ago #23836

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

  • Posts: 1309
  • Thank you received: 226
You might also check and see what's using /dev/rfcomm0 for anything unexpected.
sudo fuser /dev/rfcomm0
Take the ID number
ps -p ####

Don't give up yet. I went through all of this myself before discovering the conflict with modemmanager.
6 years 3 weeks ago #23837

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

  • Posts: 24
  • Thank you received: 1

I removed and re-detected the bluetooth dongle via Blueman and paired it all over again. Here's what fuser and ps return, and this is the screen when I try to connect the mount. Same story every time.

scott@AstroPi:~/Desktop$ sudo fuser /dev/rfcomm0
/dev/rfcomm0: 10447
scott@AstroPi:~/Desktop$ ps -p 10447
PID TTY TIME CMD
10447 ? 00:00:00 indi_eqmod_tele
6 years 3 weeks ago #23856
Attachments:

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

  • Posts: 1309
  • Thank you received: 226
I'm not sure.
At this point I would recommend trying from a vanilla installation once more. Don't use the setup scripts. I have not used those and can not account for such variables.
Before anything else take these initial steps
  • Install KStars, INDI-Full
  • Remove modemmanager
  • Pair, but don't connect the BT dongle with bluetoothmanager, or bluetoothctl
  • Bind comm port to BT device in the terminal
    sudo rfcomm bind hci0 xx:xx:xx:xx:xx:xx 1
  • Attempt to connect to EQMOD
6 years 3 weeks ago #23859

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

  • Posts: 24
  • Thank you received: 1

Figured it couldn't hurt, it's only time. I did all that, and the same result. No matter what way I install things here's what happens:

I can pair the BT with the BT manager.
I can see that linux is recognizing the serial port I created (/dev/rfcomm0 created with either the rc.local setup or via command line) and that indi is controlling it when EKOS is running.
EKOS errors out when trying to connect to the port.

Every single time :(
6 years 3 weeks ago #23949

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

  • Posts: 1309
  • Thank you received: 226
I am sorry you are having so much difficulty.
Could you post some logs and a screenshot?
6 years 3 weeks ago #23952

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

  • Posts: 24
  • Thank you received: 1

Here's a SS of it all in action. What logs would be good?

(EDIT) Here's the logfile from EKOS as well.
Last edit: 6 years 3 weeks ago by Scott Baker.
6 years 3 weeks ago #23956
Attachments:

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

  • Posts: 1309
  • Thank you received: 226
Did you remove modemmanager on this installation?
6 years 3 weeks ago #23957

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

  • Posts: 24
  • Thank you received: 1

Yes. The only change made. Clean install, installed all relevant Indi/Kstars stuff, removed modemmanager. No script install on this one (although now I don't think that is the problem)
6 years 3 weeks ago #23958

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

  • Posts: 1309
  • Thank you received: 226
What happens if you use the bluetooth manager to create a serial connection?
I predict it will create one on /dev/rfcomm1
Do you have any success connecting to /dev/rfcomm1 under those conditions?

Edit: Also when I check my Bluetooth Devices, I do not have the colorful connection bars associated with the device under my working configuration until after EQMOD has connected.
Last edit: 6 years 3 weeks ago by Andrew.
6 years 3 weeks ago #23959

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

  • Posts: 24
  • Thank you received: 1

It created /dev/rfcomm0 with the same results. Here is the SS and the logs from this attempt. I did notice that the permissions on /dev/rfcomm0 this time were different, but it still didn't work.

(EDIT) I should note, I had to disable the bind command in /etc/rc.local, I could not bind to a serial port with the BT manager if one was already created at boot.
Last edit: 6 years 3 weeks ago by Scott Baker.
6 years 3 weeks ago #23960
Attachments:

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

Time to create page: 0.433 seconds