×

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

Bi-monthly release with minor bug fixes and improvements

iOptron GEM45 (with built-in hub) - USB issue

  • Posts: 163
  • Thank you received: 26
I've used a iEQ45 for a while but it kept failing to work reliably (the INDI drivers) and I wanted to upgrade so now I have a GEM45. It's the one with the iGuider cutout in the saddle (but not including the guider itself).

I can't get it to work with my Stellarmate.
Which is terribly frustrating since tomorrow is finally a clear night since -months- essentially...

Connecting via USB to my (windows) laptop: Succes!
- I get images from the iPolar camera.
- I can connect my camera to the saddle USB hub and control & download images.
- I can control the mount with AstroPhotographyTool and with iOptron Commander.

Now with EKOS on Stellarmate on a Rpi 4B -just- executed an update and dist-upgrade.
If I select mount driver GEM45 and connect the mount over USB: No succes.
Start -> immediately the diver crashes. it tries to restart. Then Kstars crashes

File Attachment:

File Name: log_23-20-25.txt
File Size:31 KB


- please help me out! I'm starting to feel forced to move to use NINA, APT or Voyager -
Last edit: 3 years 1 month ago by Bart.
3 years 1 month ago #67164
Attachments:

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

  • Posts: 245
  • Thank you received: 56
Hoi Bart

I have the exactly the same mount the GEM45G without the guider (and also happen to live just outside Leiden). Looking at your log I can see that ttyUSB0 is not found, so I think it is just a basic connection issue.
Last night I had first light and the mount and Indi worked flawlessly.
Are you attaching to the USB connector on the back of the mount or the connector on the saddle?
Are you using a USB3 port on the Rpi4?
When you use the "Scan Ports" function from the Indi mount control what do you see?
Which other devices do you have connected to the Rpi4?
I use the persistent mapping technique to ensure I never get issues with devices fighting over the USB ports.
The following user(s) said Thank You: Craig
3 years 1 month ago #67184

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

  • Posts: 163
  • Thank you received: 26

Replied by Bart on topic iOptron GEM45 - Driver fails

Hi Richigarrod, thanks for your response!
Waar in de buurt van Leiden woon je? Ik woon zelf in Woubrugge.

I have connected the USB-B connector on the base of the mount to the USB3-A connector on the Raspberry Pi.
It's a bit odd that it has no problems connecting to my windows laptop, that's why I checked if it's responsive via APT etc.
When I 'scan ports' it finds the ttyUSB0. I selected 115200 baudrate.

Maybe the USB connection from my Moonlite compatible focuser may have interfered with the USB connection.
I have had it interfere with the iEQ45 before, where my mount mistakenly connects to the focuser before connecting to the (Bluetooth) mount.
I'll try a *fresh* Stellarmate install and do -nothing- except for connect to the mount...
3 years 1 month ago #67186

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

  • Posts: 1957
  • Thank you received: 420
Goedemorgen Bart,

What happens if you open a terminal and type

dmesg -w

and then connect the GEM45 to your Stellarmate? I seem to recall another thread on this forum where some other device was connected and no Linux device was created and it turned out to be an outdated kernel. Is there a possibility for you to update your Stellarmate?


HTH, Wouter
The following user(s) said Thank You: Craig
3 years 1 month ago #67192

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

  • Posts: 245
  • Thank you received: 56
I live just outside Roelofarendsveen (in de polder).

Trying connecting to the connector on the back of the mount (the USB A type connector) not the one under the saddle.

If you setup the persistent serial mapping you wont get USB competition issues. I am happy to help you get that setup.

If you create a profile with just the mount and a camera simulator you should be able to see if it is a simple USB issue.
3 years 1 month ago #67197

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

  • Posts: 163
  • Thank you received: 26

Replied by Bart on topic iOptron GEM45 - Driver fails

Goedemiddag Wouter, Rishigarrod,

Indeed, I use the port on the base of the RA axis body (USB-B). Lower left in the image.

Thanks for this help, I'll try this evening first to try it with a fresh install of Stellarmate.
I'm using the latest or the second-latest version now, so I don't expect an outdated kernel.

Then if that's successful, connect more equipment & work on persistent port mapping.
I found this topic on that: indilib.org/forum/ekos/7878-persistent-serial-port-mapping.html

Cheers!
Bart
3 years 1 month ago #67202
Attachments:

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

  • Posts: 163
  • Thank you received: 26

Replied by Bart on topic iOptron GEM45 - Driver fails


Ok... Ok...
-Fresh- Stellarmate (1.5.6). Only the mount connected via the USB on the base. The handcontroller is connected as well, not the GPS.

[ 15.450752] Bluetooth: RFCOMM TTY layer initialized
[ 15.450778] Bluetooth: RFCOMM socket layer initialized
[ 15.450803] Bluetooth: RFCOMM ver 1.11
[ 33.410819] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 174.710516] v3d fec00000.v3d: MMU error from client L2T (0) at 0x36c1000, pte invalid
[ 189.354767] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 190.264834] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 190.265441] usb 1-1-port1: attempt power cycle
[ 191.514769] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 192.424711] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 192.425209] usb 1-1-port1: unable to enumerate USB device

This is with exactly the same USB cable that connected perfectly to my laptop.


I am sorry if this is going to sound sad, but I literally have had -no- night of worry free imaging (before it was mostly my iEQ45-GTN for which there is no -proper- driver available).
This hobby is getting very frustrating this way.
I understand and -highly value- all the nice work the developers, debuggers and you guys helping out on this forum are putting into getting a more robust system, but somehow I've only experienced trouble with it and I need to get some encouraging results after all this time.
3 years 1 month ago #67214

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

  • Posts: 163
  • Thank you received: 26

Replied by Bart on topic iOptron GEM45 - Driver fails


I did:
{Scan Ports} --- 2021-01-09T09:47:49: [WARNING] No candidate ports found on the system.
{At start} --- 2021-01-09T09:47:27: [ERROR] Failed to connect to port (/dev/ttyUSB0). Error: Port failure Error: No such file or directory. Check if device is connected to this port.

And with dmesg -w:

[ 34.330671] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 196.794345] usb 1-1.1: new high-speed USB device number 3 using xhci_hcd
[ 197.704907] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 198.654852] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 198.655353] usb 1-1-port1: attempt power cycle
[ 199.914819] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 200.824885] usb 1-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 200.825402] usb 1-1-port1: unable to enumerate USB device
[ 240.580302] v3d fec00000.v3d: MMU error from client L2T (0) at 0x2981000, pte invalid


Do I need a powered USB hub or something?
Last edit: 3 years 1 month ago by Bart.
3 years 1 month ago #67215

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

  • Posts: 1957
  • Thank you received: 420

Is this with the mount plugged in to the raspberry pi? If not, please do that and see if that solves the issue. If it does solve the issue then you will indeed need a powered USB hub.
3 years 1 month ago #67217

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

  • Posts: 163
  • Thank you received: 26

Replied by Bart on topic iOptron GEM45 - Driver fails


Yes, of course. And with the same USB cable as I used before on my laptop.
And of course the mount is switched on.

I tried to connect also to the handcontroller with the supplied cable and my USB - Serial (FTDI) adapter.
That did recognize in dmesg, but the driver can't talk with it...

This is the full dmesg -w log, including the rest of the equipment:
Warning: Spoiler!
3 years 1 month ago #67219

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

  • Posts: 245
  • Thank you received: 56
Are you able to connect other equipment to the same port on the the Rpi4. It almost looks like a hardware issue.
Very frustrating but there has to be a logical explanation.

What power supply are you using for the Rpi4? Maybe its a power issue.
The following user(s) said Thank You: Craig
3 years 1 month ago #67220

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

  • Posts: 163
  • Thank you received: 26

Replied by Bart on topic iOptron GEM45 - Driver fails

Yes, the USB ports on the Rpi4B seem to work fine when I connect my ASI1600 including the EFW (so a bit of power draw seems no problem).
I can connect my 'ScopeFocus' which even draws power for a stepper from the USB also and this is no problem.

When I connect the mount USB to the Rpi and the ASI1600 to the USB hub (in the dovetail saddle), effectively daisy-chaining the ASI through the mount, it also doesn't register.
And in some attempt I disconnected the telescope from the mount all together, in case any electrical connection between the two would be the issue. Didn't work either.

Re-checking the connection with my laptop: Success.
Not all -Universal- Serial Busses are created equal? :silly:


Edit: And I am using the Raspberry pi supplied 5.1V, 3A power supply. That sould be sufficient in any case.

In fact, In the current Stellarmate installation I've upped the voltage according to:
[In /boot/config.txt]
over_voltage=6
arm_freq=1750
max_usb_current=1
Last edit: 3 years 1 month ago by Bart.
3 years 1 month ago #67221

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

Time to create page: 0.762 seconds