Marc replied to the topic 'Bug connecting through a hub ...' in the forum. 1 month ago

Kevin says :

"Well one thing is certain, if the OS doesn't see the device, INDI never will. So this appears to be either an OS-level, or hardware issue, and not an INDI issue."
Agreed !

"What does dmesg say when plugging in the device?"
Nothing, as for the OS, the EFW plugged to the hub simply does not exist .

You say this happens no matter what hub you use, and both on Raspberry Pi, as well as your laptop? Is that correct?
Absolutely.

Now ...

I tried to plug 2 USB keys to the camera hub : it Works, the keys are both available Read/Write.
Same if I plug the USB keys to a separate hub.

So it appears the EFW **IS** the problem.

I tried this set up:

- Focuser and ASI290mm plugged to the camera hub (USB port 1 on the Pi)
- EFW on USB port 2
- Mount on USB port 3
- Wireless joystick on USB port 4

Everything works fine, but I still don't understand why the EFW on a hub isn't detected by the system.
And by the way ... ASI290mm and EFW on a hub both work ... Under Windows ... Which excludes any EFW related problem :(

- Marc

Read More...

Marc replied to the topic 'Bug connecting through a hub ...' in the forum. 1 month ago

It did work several months ago and I didn't change any piece of hardware since ... Plus, the Pi is powered by a 3000 mA source. More than enough IMHO.

- Marc

Read More...

Marc replied to the topic 'Bug connecting through a hub ...' in the forum. 1 month ago

Hi Kevin,

# First attempt, user "astro", filter wheel plugged to the camera hub, 2 cameras + EFW :

[astro@astra:~]$ lsusb
Bus 001 Device 009: ID 03c3:462b
Bus 001 Device 010: ID 03c3:1604
Bus 001 Device 004: ID 04b4:6572 Cypress Semiconductor Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# Second attempt, user "root", filter wheel plugged to the camera hub:

[astro@astra:~]$ sudo lsusb
Bus 001 Device 009: ID 03c3:462b
Bus 001 Device 010: ID 03c3:1604
Bus 001 Device 004: ID 04b4:6572 Cypress Semiconductor Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# Third attempt, user astro, filter wheel plugged directly to the Pi
[astro@astra:~]$ lsusb
Bus 001 Device 013: ID 03c3:462b
Bus 001 Device 011: ID 03c3:1604
Bus 001 Device 004: ID 04b4:6572 Cypress Semiconductor Corp.
Bus 001 Device 012: ID 03c3:1f01
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

As you can see, the filter wheel ( Bus 001 Device 012: ID 03c3:1f01 ) doesn't show up when connected to the camera hub.
Not even under the root account.

It is only visible when plugged directly (the third attempt).

- Marc

Read More...

Marc created a new topic ' Bug connecting through a hub ...' in the forum. 1 month ago

Hello everybody,

After a few months off, I'm back to deep sky imaging. So two days ago, after having updated everything, ( Fedora 34 and last GitHub version ) I had a very bad surprise.
Usually my setup for deep sky imaging is the following :

- one mount SW EQ6-R Pro
- one ASI1600mm Pro ( imaging )
- one ASI290mm ( autoguiding)
- one ASI EFW mini filter wheel
- one ASI EAF focuser.

I used to connect the ASI290mm and the EFW to the two port hub on the ASI1600mm, and the rest directly to the Raspberry Pi.
This setup used to work perfectly several months ago.

Now, INDI refuses to discover what is plugged to the camera hub, and after a few minutes, everything is freezzed
If I plug everything directly to the Raspberry Pi, it works again, except ... The Pi has only 4 USB ports :( ... So I'm left with a device with no possible connection, except if I chain a second PI. Any kind of separate hub has the same result. What's connected to the hub fails, what's connected directly works. And this with the Pi or directly with my laptop.

Some help would be appreciated. :)

- Marc

Read More...

Hi Jim,

Yes, I know copr.fedorainfracloud.org/coprs/xsnrg/, of course :)

All my Raspberry PIs run under Fedora.
This distro works really fine on PIs, i've been using it for years, and I love setting up my network both the old way AND with nmcli) ...

That would be nice to have those 'bleedings' (with the appropriate fedora-repoxx) under Raspberry Pi..

Last time I checked, I dindn't find them.

- Marc

Read More...

For what it's worth, my own experience :

SW EQ6-R Pro (eqmod)
ASI1600mm Pro
ASI290mm
ZWO EAF
ZWO EFW

Every hardware on a Raspberry Pi3 running Fedora. ASI290mm + ZWO EFW on the hub of the 1600mm
EQ6 and ZWO EAF on the others USB ports.

Kstars on a distant laptop, WIFI connected to the Pi under Fedora 33.
Every thing built from scratch, latest git (2021-04-10)

Everything works fine. Absolutely no problem detected (?)

Just one thing, I had to add the famous line giving some more memory to my own
/usr/lib/udev/rules.d/99-astro.rules

<


# Add some memory for ASI cameras
ACTION=="add", ATTR{idVendor}=="03c3", RUN+="/bin/sh -c '/bin/echo 256 >/sys/module/usbcore/parameters/usbfs_memory_mb'"

# EQMod Mount
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015", ATTRS{serial}=="EB30E0KY", MODE="0666", SYMLINK+="ttyUSB.EQ6-Marco"
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015", ATTRS{serial}=="EB46CW9V", MODE="0666", SYMLINK+="ttyUSB.EQ6-Greg"
>

I need it for the planetary software FireCapture which, by the way JASEM, is fully compatible with INDI, both the Linux AND the Windows versions.
(Starting with 2.7beta-02)

A new add to your list of compatible softwares.

- Marc

Read More...

Marc replied to the topic 'RTC module - want to get a good one' in the forum. 6 months ago

Have been using these for several months now, one of the Pis being used as a replacement. After 2 months without pluggin it, the clock is still accurate time and date...
Just a few seconds drift.

www.amazon.com/DS3231-Precision-Memory-A...id=1616597955&sr=8-1

Use :
modprobe rtc-ds3232
echo ds3232 0x68 > /sys/class/i2c-adapter/i2c-1/new_device

- Marc

Read More...

Marc replied to the topic 'KStars v3.4.3 Released' in the forum. 1 year ago

Hi,

As for me the problem was with the "Mojave Icon Theme". So I reverted to the genuine Icon theme, reinstalled the Mojave Theme and reverted again. The problem was solved.

- Marc

Read More...

Marc replied to the topic 'KStars v3.4.3 Released' in the forum. 1 year ago

El Corazon wrote:

Marc2b wrote: El Corazon says :

[2020-07-19T21:17:09.536 CDT INFO ][ org.kde.kstars.indi] - iOptron CEM60 : "[WARNING] Cannot unpark mount when dome is locking. See: Dome Policy in options tab. "

Just as the message says, go to the indi panel/your mount/options and simply click "Dome Ignored". Save and reload and you're done. ;)

- Marc



Done that, of course, but have been unable to test since it is cloudy again now. But if that is all that is required for fixing it, then that's easy enough, of course. Can you confirm, that that is all that's required, Marc? Doug's experience suggested something else.

Jo


Hi Jo,

If your nights are cloudy you can verify it works with the indi_simulator_telescope driver (Telescope Simulator in the profile editor )

- Marc

Read More...

Marc replied to the topic 'how do I setup 2 different guiders?' in the forum. 1 year ago

alacant wrote: Hi everyone
Internal EKOS guider.

I am currently using a zwo120mm on a 60mm f4 guide telescope for my sw130pds.

How do I make a profile and then switch to using a sw250p which uses a zwo120mini in an OAG?

Is there any way I can have<em> per profile</em> guide settings? Dither etc?

Cheers and TIA,
Steve


Open the Ekos panel, go to the mount tab. Select a new config ' Config #2/3'. Copy the same telescope values then put the new values in the guiding part of the form.
Click 'Save Telescope Info' and you're done. Now just switch between the configs by selecting 'Config #' when necessary.

- Marc

Read More...

Marc replied to the topic 'KStars v3.4.3 Released' in the forum. 1 year ago

Now, my own problems :

1/ I'm using Kstars with the dark theme "Black Body". When I quit and then restart, the soft comes back with an incomplete white menu and I have to set my theme again.
it is very unpleasant when you're in the dark and have your vision adapted because of the crude white light.

2/ I have 2 problems with indiwebmanager. (The last version including agent)

- I can't change the user from the default 'root' or it refuses my connection.
- If

I connect through indiweb, the indiserver and drivers are launched but everything stalls then. I'can't even unpark my mount.
If I start manually the indiserver and the drivers through an ssh cnx, everything works fine.

- Marc

Read More...