×

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: 24
  • Thank you received: 1

The MAC address don't lie. I've verified it on other laptops, it's the correct BT device that's being connected. I've started with clean Ubuntu installs almost daily. With all the different things I've tried, I didn't want to take any chance of just continuing to work on a broken install.
6 years 2 weeks ago #23986

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

  • Posts: 1309
  • Thank you received: 226
What version of Linux are you using?
Ubuntu Mate is popular here, even recommended. I use LUbuntu because I find it's a bit lighter weight and I like the plain theme. Perhaps try a different distro?
6 years 2 weeks ago #23988

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

  • Posts: 24
  • Thank you received: 1

Ubuntu Mate 16.04.2 for Raspberry Pi. I do have a laptop with Linux Mint but...going to try that and see if I can connect.

(EDIT) I fired up my Linux Mint laptop and had ZERO issues connecting and controlling the mount via Ekos. First I removed modemmanager, then used the Mint BT manager, connected and paired with that, then just just a quick and dirty command line rfcomm bind to /dev/rfcomm0. Fired up Ekos and the mount connected immediately. Was able to slew with manual controls and even pick targets and slew to them in Kstars (although it was all off target, it worked).

So. There has to be some issue with the Raspberry Pi. Windows doesn't have a prob connecting, Linux Mint doesn't have a prob connecting, but no matter what I do in Ubuntu Mate on the Pi3, I get errors.

(SECOND EDIT)

So I have a second Rasperry Pi 3 running another home project. I took that SD card out, installed Ubuntu Mate on a new SD and tried again. Same exact results as the other RPI. So my BT dongle works with no issues in Windows and Linux Mint, but fails the exact same way on 2 different Raspberry Pi's running Ubuntu Mate.
Last edit: 6 years 2 weeks ago by Scott Baker.
6 years 2 weeks ago #23989

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

  • Posts: 983
  • Thank you received: 375

A few questions before we nail it ;-)
1. Do you have any custom changes to /boot/config.txt on you RPi system?
2. Do you use built-in BT or external dongle?
3. Can you connect to EQMod with miniterm /dev/rfcomm0 or any other serial terminal?
4. Can you connect to any other BT device with a serial terminal?

Regards

Radek
6 years 2 weeks ago #24009

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

  • Posts: 24
  • Thank you received: 1

My son and his GF are visiting for Spring Break so I broke the mount/scope down. I can bring out the RPI and test those things though, thanks for the suggestions. I'll just edit this post as I do the test. As for what I can tell you now:

1. The only changes I've ever made to /boot/config.txt is to add rfcomm bind hci0 MACADDRESS 1 &

2. I use the external dongle from Shoestring Astronomy LINK

3. I did try rfcomm1 once, but usually with the /boot/config.txt or even binding via command line it defaulted to rfcomm0.

4. I'll break out the RPI and try to connect my phone, I'd never considered something like that.
6 years 2 weeks ago #24010

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

  • Posts: 983
  • Thank you received: 375
I mean /boot/config.txt NOT /etc/rc.local. This is the place where you enable various overlays for RPi. One of them is to disable BT (internal), and this one can give you hard time. Just review the very end of the file and paste here these a few lines that are sitting there.

This might be the root cause of your problems. If you use Raspberry Pi 3 it has bluetooth built-in. Use it instead of an external dongle. If it is Raspberry Pi 2 you need to stick to a dongle, it does not have bluetooth device. In any case you need to pair the devices before successful binding. To do this start bluetoothctl in your terminal and run:
scan on
agent on
pair XX:XX:XX:XX:XX:XX
trust XX:XX:XX:XX:XX:XX

Either it is /dev/rfcomm0 or /dev/rfcomm1 depends on what is you bind command. I think now you mix internal BT device with external BT dongle. For RPi3 just disconnect the dongle and stick to internal BT device and bind it to /dev/rfcomm0 as you have already done.

I don't think you can just connect to your phone. You need a BT serial device. If you don't have anything like this at you hand just skip this step.


PS. If you will not be able to get it through let me know. I can do it for you remotely.
Last edit: 6 years 2 weeks ago by Radek Kaczorek.
6 years 2 weeks ago #24011

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

  • Posts: 24
  • Thank you received: 1

Ah yea I confused /etc/rc.local with /boot/config.txt. The only changes I make to config.txt is the normal headless settings. hdmi_force_hotplug=1 hdmi_group=2, and hdmi_mode=82. Nothing else is changed there.

As for the dongle, its the device that's plugged into my mount. I do use the RPI3's built in bluetooth to connect to my mount. I DO NOT use any external BT devices on the RPI itself.
6 years 2 weeks ago #24025

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

  • Posts: 1309
  • Thank you received: 226
Perhaps install a different distribution of Linux on the Raspberry Pi. That may eliminate specific hardware issues.
I run lubuntu. Give that a shot.
The following user(s) said Thank You: Scott Baker
6 years 2 weeks ago #24113

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

  • Posts: 1309
  • Thank you received: 226
I got this tip from the INDI Support FAQ
6 years 2 weeks ago #24163

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

  • Posts: 24
  • Thank you received: 1

I haven't given up, my kid and his GF were here for a week, so I packed the scope up. In that time I installed Lubuntu on the RPI3 and even tried it on my laptop but I just didn't like it, so I went with Ubuntu Mate there. I was hoping to get out late, late tonight for some imaging but I'll probably stick with my windows setup for that.
At least I'll have the scope up and ready to tackle this fiasco again :)
Last edit: 6 years 1 week ago by Scott Baker.
6 years 1 week ago #24291

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

  • Posts: 24
  • Thank you received: 1
I've tried a few different flavors of linux on my laptop and all can pair and connect and run Ekos/Kstars with very little trouble. Mint, Ubuntu Mate, Lubuntu and even Peppermint all do just fine, just like my windows machine. At least I have that going for me, I can always leave that laptop outside and VNC into it with my windows machine.

Raspberry Pi is a whole different story. I've tried Ubuntu Mate and Lubuntu on 2 different Raspberry Pi 3's, and nothing will allow me to connect. Bluetooth pairing works, binding rfcomm works via command line, and /etc/rc.local, but I get the same error I've documented previously in this thread. Every single time, no matter what steps I take to detect, pair and assign a serial port, all goes well up to the actual point where Indi tries to connect to the Shoestring dongle.

I'm going to try and find another RPI OS that may work, and in the meantime I'm just going to take my linux laptop back to Mint, it was my favorite flavor and I ran it for years. As for the raspberry pi 3 issues, it's beyond me. Doesn't make a lick of sense, and the same issue cropping up on 2 different machines and 2 different operating systems is mind boggling, especially with people claiming they get the exact same hardware to work on their machines.
6 years 1 week ago #24327

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

  • Posts: 24
  • Thank you received: 1
Another update:

I ordered a serial to usb cable from Amazon and made my own shoestring-style USB2EQ5 cable. I still have my Lubuntu OS running on the Raspberry Pi. Everything connected just fine. No issues I could see (Other than my lack of knowledge in actually operating Kstars/Ekos).

Telescope control was as expected, I could slew the scope around with Kstars or manually with the scope control window. I could lock back on the Sun (I'm indoors, was just making sure it all worked) and sync and track it.

Some day I'd love to figure out why the bluetooth dongle can't connect on the RPI, that will probably drive me insane. Seriously.

But for now, I'll deal with one additional cable on the mount and consider this a win. Now to learn how to actually use Kstars to do my imaging :)

Thanks to everyone who helped, if anyone ever comes up with additional info or suggestions on getting the BT2EQ5 working I'd love to hear it. I'm off to Kstars school in the meantime!
6 years 4 days ago #24505

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

Time to create page: 0.308 seconds