×
INDI Library v1.8.6 Released (21 Aug 2020)

August 2020 release of INDI Library v1.8.6 introduces new drivers while providing fixes and improvements to existing devices and core framework.

No ASI Camera after Update - Suspect port mapping

2 months 1 hour ago
dmsummers
Gold Boarder
Gold Boarder
Posts: 241
Karma: 2
More
No ASI Camera after Update - Suspect port mapping #57582
@Avocette, regarding " the hub is powering the RPi itself through....one of the three charging ports":

A bit OT, but this is definitely a marginal power setup for Pi4 that could easily get you to odd instabilities. The Pi4 power spec is 3 amps. The actual power delivery to the Pi4 from your hub is dependent on the total power draw on the hub (all ports). Recommend you reconsider and power the Pi4 either direct from a separate 5v, 3amp PS, or from a 12v-5v (3 amp) buck converter connected between PPB and Pi4. Powering the PI4 from a hub charging port will be flaky (sooner or later). USB and wireless are the first to go on Pi4 when power is insufficient (my own experience with Pi4). Cheers, Doug

RASA11, Celestron CGX-L, ASI183mc Pro, 60mm guider + ASI290mm mini, ASI EAF focuser, PPB, Rpi4-4Gb+SSD, Powered USB3 hub, hardwire Ethernet.

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

1 month 4 weeks ago
Avocette
Expert Boarder
Expert Boarder
Posts: 151
More
No ASI Camera after Update - Suspect port mapping #57589
Hi Doug. The power spec of the recommended power supply for the RPi4 is 3A at 5.1V, and I have one spare that I have substituted in place of the 1.5A charger USB port from the hub from time to time. I also measured the voltage and current draw of the RPi4 in this actual configuration with a Sandisk Extreme SSD and the tp-link 7-port powered USB 3.0 hub being the only directly USB connected devices. The input voltage never dropped below 5.07V and with KStars running, mount slewing and camera imaging away the RPi4 current drawn peaked at around 550mA. I'm not discounting possible power issues, but they don't seem to be of infleunce here.

Currently running KStars/Ekos/Indi on a Raspberry Pi 4B 2GByte under Raspbian thanks to Astroberry
Sky-Watcher ED80 Pro with 0.85x FR/Corrector with Canon DSLR on AZ-EQ5 GT mount
Other Sky-Watcher scopes - SkyMax 150 Pro Maksutov Cassegrain and Explorer 150p Newtonian

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

1 month 4 weeks ago
dmsummers
Gold Boarder
Gold Boarder
Posts: 241
Karma: 2
More
No ASI Camera after Update - Suspect port mapping #57590
@Avocette: The danger is peak draw during startup. If you're monitoring amps from PPB, you probably can't be sure what the true peak is (I think it's more of an time sampled/avg peak). FWIW, I also see mild amp draw once the whole config is up & running, which the charging port might be ok to handle. Just wouldn't trust the 1.5 during startup, especially if anything is connected to the Pi4 USB3 ports.

RASA11, Celestron CGX-L, ASI183mc Pro, 60mm guider + ASI290mm mini, ASI EAF focuser, PPB, Rpi4-4Gb+SSD, Powered USB3 hub, hardwire Ethernet.

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

1 month 4 weeks ago
knro
Administrator
Administrator
Posts: 8398
Karma: 51
No ASI Camera after Update - Suspect port mapping #57594
I removed the EQMod cable and same results, so that's not it.

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

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

1 month 4 weeks ago
kross
Expert Boarder
Expert Boarder
Posts: 148
Karma: 2
More
No ASI Camera after Update - Suspect port mapping #57597
Hmm, well I guess it isn't as simple as I had hoped. It seems each of us has "that one device" that breaks things, but it isn't the same device for all of us.

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

1 month 4 weeks ago
kross
Expert Boarder
Expert Boarder
Posts: 148
Karma: 2
More
No ASI Camera after Update - Suspect port mapping #57601
Did a little research, and it seems the Pegasus PPB is controlled via USB-to-Serial internally (you plug a USB cable into it, but internally it has a USB-to-Serial adapter, and it shows up on the host computer as a serial device). So it seems USB-to-serial adapters aren't off the hook yet!

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

1 month 4 weeks ago 1 month 4 weeks ago by Avocette. Reason: additional info.
Avocette
Expert Boarder
Expert Boarder
Posts: 151
More
No ASI Camera after Update - Suspect port mapping #57609
You are quite correct - nothing is yet off the hook. Attached is my lsusb list from the original working version, pre-kernel-upgrade. The PPB is Bus 001 Device 004. The EQdirect cable has a Proflific brand serial adapter which I recall caused a number of problems in the past - we were all advised to avoid Prolific and choose FTDI instead. I guess I have to get used to running lsusb before starting up KStars and counting the entries before resorting to replugging everything!

Currently running KStars/Ekos/Indi on a Raspberry Pi 4B 2GByte under Raspbian thanks to Astroberry
Sky-Watcher ED80 Pro with 0.85x FR/Corrector with Canon DSLR on AZ-EQ5 GT mount
Other Sky-Watcher scopes - SkyMax 150 Pro Maksutov Cassegrain and Explorer 150p Newtonian
Attachments:

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

1 month 4 weeks ago
kross
Expert Boarder
Expert Boarder
Posts: 148
Karma: 2
More
No ASI Camera after Update - Suspect port mapping #57634

Avocette wrote: You are quite correct - nothing is yet off the hook. Attached is my lsusb list from the original working version, pre-kernel-upgrade. The PPB is Bus 001 Device 004. The EQdirect cable has a Proflific brand serial adapter which I recall caused a number of problems in the past - we were all advised to avoid Prolific and choose FTDI instead. I guess I have to get used to running lsusb before starting up KStars and counting the entries before resorting to replugging everything!


Interesting. Your Prolific USB-to-serial doesn't cause problems, but your FTDI one does. My EQDirect cable is based on FTDI.
$ lsusb
Bus 002 Device 004: ID 03c3:1604  
Bus 002 Device 003: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 006: ID 0bda:b812 Realtek Semiconductor Corp. 
Bus 001 Device 009: ID 03c3:1f01  
Bus 001 Device 008: ID 04b4:6572 Cypress Semiconductor Corp. 
Bus 001 Device 010: ID 1618:0921  
Bus 001 Device 005: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 003: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I might be barking up the wrong rabbit hole, but then again....

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

1 month 3 weeks ago
knro
Administrator
Administrator
Posts: 8398
Karma: 51
No ASI Camera after Update - Suspect port mapping #57850
I filed a bug report here: github.com/raspberrypi/linux/issues/3779

Hopefully we get some feedback on it.

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
The following user(s) said Thank You kross, Avocette

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

1 month 3 weeks ago
Avocette
Expert Boarder
Expert Boarder
Posts: 151
More
No ASI Camera after Update - Suspect port mapping #57881
I learned a new command (sudo lsusb) from your bug report, so I thought I would try it out. Before that I did a sudo apt update && sudo apt upgrade. I subsequently found that all my USB devices were listed both by lsusb and sudo lsusb. Has kernel 5.4 perhaps been fixed? My SSD installation seems to be working including the KStars 3.5.0 beta.

Currently running KStars/Ekos/Indi on a Raspberry Pi 4B 2GByte under Raspbian thanks to Astroberry
Sky-Watcher ED80 Pro with 0.85x FR/Corrector with Canon DSLR on AZ-EQ5 GT mount
Other Sky-Watcher scopes - SkyMax 150 Pro Maksutov Cassegrain and Explorer 150p Newtonian

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

1 month 3 weeks ago 1 month 3 weeks ago by maxthebuilder.
maxthebuilder
Gold Boarder
Gold Boarder
Posts: 371
More
No ASI Camera after Update - Suspect port mapping #57909
Looks like I have a similar problem...
Recently, I added a ZWO EAF focuser to my setup.
Tried it first with AZ-GTi, ASI294 and ASI120 on RPI 4 B (4Gb). Stellarmate 1.5.2.
All worked very well for several sessions.
Switched to Stellarmate 1.5.3 with the same hardware. Again, all worked very well for several sessions.
Today, I put my rig on a HEQ5 and boom... no ASI120, no EAF (they are connected to ASI294's hub).
After some troubleshooting I found a workaround.
(All my USB devices are connected to a USB3 powered hub).

-- if I disconnect HEQ5 EQDir USB cable from the hub and start the system up - everything comes up OK (except for the mount of course)
-- then I just connect EQDir cable and power on the HEQ5 and it comes up too

Strange thing is that it is not enough to power off the mount - the cable has to be disconnected from the hub.

Oh well... The workaround works.
Maybe it's a power-draw issue as someone suggested - tomorrow I'll try a separate power supply for RPI.
Currently I power everything with a single 12V/5A brick.

Thanks!

Max S.

RPI 4 B (4Gb) with SMate
Nikon D5500 H-a modified. Nikon D5500 stock
AT72EDII, TPO RC6
ZWO ASI294MC Pro, ASI071MC Pro
ZWO ASI120MC-S on ZWO 30F4
ZWO EAF x 2
SW AZ-GTi x 2
SW HEQ5

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

1 month 3 weeks ago
knro
Administrator
Administrator
Posts: 8398
Karma: 51
No ASI Camera after Update - Suspect port mapping #57916
I can confirm that ANY FTDI cable causes this problem. As soon as all the FTDI cables are removed, the system is back to normal operation with all USB devices accessible. I reported this on the bug report for the Kernel. It's not limited to EQDir, but any FTDI chip would cause the same issue.

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

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

Time to create page: 0.413 seconds