×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

eqmod communication error

  • Posts: 407
  • Thank you received: 74
Are you sure the cable isn't snagging on something ?

IMO Its sounds like a cable or power spike/drop off or adapter problem nothing to do with Linux OS - as you say you have been using it fine for several hours and over a year ok.
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
4 years 6 months ago #44329

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic eqmod communication error

Hi and thanks for the encouragement.
Yeah. The hub checks out ok. Alas I have no spare usb extension cable (hub to laptop).
Here's hoping it's that;)
Cheers
4 years 6 months ago #44332

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

  • Posts: 118
  • Thank you received: 19
I agree with stash check the power cable to the mount, I had issues like this a while back & it was the power supply to the mount at the connector that was the issue, there are many people that have changed the power connector including me, for a more reliable plug / socket connector at the mount end. A dead giveaway is the power LED whatcha that while slewing & moving the mount for a slight flicker as the indication as to the connector condition.

Regards

Alan
4 years 6 months ago #44344

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

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic eqmod communication error

I agree with checking for issues with power to the mount. But also try connecting the mount to the computer without a hub in between. I have found on my HEQ5 it was not very happy going through a (powered) hub, while direct to the my Pi was stable.
4 years 6 months ago #44346

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic eqmod communication error

Hi everyone and thanks for all the suggestions.

I traced it to the hub, but not what you'd expect. I removed the power from the hub and it now works reliably every time. Not seen that posted before so I hope others may benefit.

I've a DSLR, a zwo guide camera and an eq6.

Cheers,
Steve
4 years 6 months ago #44377

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

  • Posts: 118
  • Thank you received: 19
That’s strange because I’ve just had a problem with my Raspberry Pi 4 not seeing my ASI 120 MM-S and removing the power supply to the hub fixed that. It works faultlessly on my Raspberry Pi 3 B+ setup

Regards

Alan
4 years 6 months ago #44378

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

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic eqmod communication error

Happy my tip helped. It's possible it could be a ground loop issue causing instabilities with the powered hub.
4 years 6 months ago #44380

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic eqmod communication error

Is the loop thing where you connect the mount to a copper pipe hammered into wet ground?
4 years 6 months ago #44381

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

  • Posts: 118
  • Thank you received: 19
No it’s the ground line or 0 volt rail of all the equipment connected together , so the signals for the communication between the equipment can pass from one unit to the next. When the hub is powered via the same supply as the raspberry pi to its own separate power supply input, the noise on the supply line can loop around the common connection amplifying the noise even more until it interferes with the signals. A good example of this are the old fashioned HiFi systems which would produce a loud back ground hum which was difficult to remove. Or a PA system squealing with feedback as an extreme example.
The following user(s) said Thank You: alacant
4 years 6 months ago #44383

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

  • Posts: 281
  • Thank you received: 29

Replied by Helge on topic eqmod communication error

Hi,

I am connecting to my eq5 (AZ-EQ5) mount via Shoestring Bluetooth Adapter (BT2EQ5) for two years, now I cannot get the mount connected:

EQMod Mount : "[ERROR] Failed to connect to port (/dev/rfcomm0). Error: Port failure Error: No such file or directory. Check if device is connected to this port.

Compared to last time when it was working, I was running the regular updates, including KStars / INDI drivers.

I have attached the log file.

Would be great if anyone has an idea how to resolve / get back on track!

Best, Helge
4 years 4 months ago #46438
Attachments:

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

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic eqmod communication error

I was using my bluetooth adapter just last night without issue on an up to date system. So we could eliminate software bugs.
Ensure modemmanager is not installed on your system, and I like to put this into /etc/rc.local to bind it at startup. (XXs replaced with mac address of mount adapter)
# Bind Bluetooth to Mount Adapter.
rfcomm bind hci0 XX:XX:XX:XX:XX:XX 1 &
The following user(s) said Thank You: Helge
4 years 4 months ago #46455

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

  • Posts: 281
  • Thank you received: 29

Replied by Helge on topic eqmod communication error

Thanks for your recommendation. I double-checked the configuration - and it turned out the bind command was missing! No idea how it happened, but at the end, easy to resolve.

btw : I do the binding upon start via modification of the bluetooth.service file

(I still follow the procedure once shared by "tseckler" for the shoestring bluetooth adapter.)
4 years 4 months ago #46489

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

Time to create page: 0.333 seconds