Hi 

Firts time using RPI4 with Astroberry and when trying to connect my equipment I was unable to connect the mount (EQ6R Pro). I am using a Pegasus EQMOD direct cable, the same that I use with NINA under ASCOM. I'ver set the same parameters such as 9600 baud rate and EKOS still unabel to connect to the mount. 
Any advise for a newbie

Thanks a lot

I have had this issue for three months now and tried everything and was unable to sort, I have since moved to NINA and Ascom, as INdI is just too glitchy as of late, too many upgrades all the while without sorting old issues, is ruining the software….
Good luck and hope you can sort….

Hi Bruno, which port are you connecting to? Can youplease post screenshots from the settings of driver?

Hi
EQ6 is connect via EQ direct cable (HC port at the mount and USB at RPI4) just like in ASCOM
Tomorrow afternoon I'll post the screenshots

Thanks

I still, and will continue to use, NINA and ASCOM on my main rig (all with an i3 Intel miniPC).
I've adquired the RPI4 (astroberry) for an ultraportable rig (ASI533 or ASI1600MM with 135mm lens) to be used with a SW AZ-GTi with EQ drivers but sometimes I'll use this rig with the EQ6R. Since I like all my rigs to be fully automated I'v decided to go for the astroberry for the portable one.

Thanks

I don't think a physical port, but setting in Ekos. Like /dev/ttyUSB or /dev/ttyACM

I'm experiencing the same issue.  KStars on Ubuntu 20.04.3 with EQ6-R working for years.  Haven't had good WX since last summer.  Tried to connect today both with 3.5.7 Stable and latest nightly.  Ekos doesn't recognize the mount.  I see the device show up in dmesg, but the only device/port Ekos sees is the Pegasus Falcon rotator - which it cannot connect to with EQMOD.  The only port listed in the "Ports" section of the EQMod Mount tab of the INDI Control Panel is the Pegasus Rotator port.  That's it.  (See picture).

What happened to the EQMOD driver in the last few months? 

 

If you plug the USB cable directly into your computer instead of the Pegasus hub, does the system then recognize the port?

Use 9,600 baud rate with an EQDir cable and 115,200 for a direct USB connection.

I've noticed glitches sometimes with other USB style connections so if you still have problems try with just the mount and put Scan Ports on. You might also need to reboot everything.

Here's the driver doco..
www.indilib.org/telescopes/skywatcher/eqmod.html

Did some more extensive troubleshooting.  Tried complete wipe and reinstall of Ubuntu 20.04.3 to no avail.  Discovered it's the pl2303 serial-USB module in the latest 5.13.0-28-generic kernel.  If I regress and boot to the previous 5.11.0-27-generic kernel, it works fine.  Here's the snippets from dmesg:

5.13.0-28-generic kernel:
[ 2.894277] usbcore: registered new interface driver usbserial_generic
[ 2.894292] usbserial: USB Serial support registered for generic
[ 2.907539] usbcore: registered new interface driver pl2303
[ 2.907574] usbserial: USB Serial support registered for pl2303
[ 2.907596] pl2303 1-6:1.0: pl2303 converter detected
[ 2.907602] pl2303 1-6:1.0: unknown device type, please report to This email address is being protected from spambots. You need JavaScript enabled to view it. 

5.11.0-27-generic kernel
[ 3.201216] usbcore: registered new interface driver pl2303
[ 3.201228] usbserial: USB Serial support registered for pl2303
[ 3.201243] pl2303 1-5:1.0: pl2303 converter detected
[ 3.201349] usb 1-5: pl2303 converter now attached to ttyUSB1

I tried sending the bug report to the listed email address, but it bounced.  Don't know how to fix the pl2303 module in 5.13.  Anyone have any idea who to contact?  Or how to build the 5.11 version of pl2303 into the 5.13 kernel?

Maybe a kernel bug? (seems to have been fixed in later kernel versions, according to the conversation)
lore.kernel.org/linux-usb/YgPK1r8nQuItp4...dconsulting.com/t/#u

Yes - looks like 5.13 broke it and 5.15.6 has it fixed.  I've reverted back to 5.11 for now, will wait for 5.15.6 to be production.