No need, I just made a change to Ekos where it will automatically switch to "client" upload if you're doing focusing/astrometry. After focusing/astrometry is complete, it will go back to local mode (if that was selected before).

What happens in both cases?

Then I have to reconnect.
EDIT:
No crash.

Why dont download the raw directly to kstars and do the dcraw/fits conversion there instead of doing cpu intensive tasks on the raspi?

I guess you're starting on the Raspberry PI? Do not forget to run INDI server with -m flag, e.g.

This way INDI server does not disconnect if it is sending large amount of data (up to 100 MB) to the client.

But I found issues with reading JPEGs/raw due to dcraw reporting bogus values, and I'm now trying to come up with some "hackish" method to work around that.

Ok, so I can read all image types either via FITS or natively now without any issues. The ONLY small issue is that the size is not reported for native images, only FITS. Tried to figure out the issue for a white before I gave up. The main problem was dcraw itself. So I downloaded and built the latest v9.26 and it worked fine. I made a dcraw package for raspberry pi that should be available in the daily raspberry pi image by tomorrow.

Thank you, Large Fine Jpeg works now, but it take exactly the same time to arrive like an raw/fits ~50 seconds. So this makes no difference to me with the exeption raw/fits high dynamik range vs. low dynamic range with jpeg comression artifacts. "Medium Fine jpeg" arrives in ~22s. "Small fine Jpeg" arrives in 13 seconds and I think I will stick with this. I did not yet try to use fits/jpeg in focusing/astrometry and how jpeg/compression artifacts may influence it , waiting for clear sky!

I found an workaround to get images as fast as directly connected to the client .

My last decision was simply to connect the dslr back to my kstars client and combine multiple indiservers because I just don't wanted to loose the fits preview. This of cause is no solution for everyone who has its setup real remote and not like me with kstars client and mount in the same room.

But then accidental I just stumbled upon the usbip driver in the modern linux kernel. It can redirect any connected usb device from the raspberryPi to any client pc running kstars.

So I plugged my usb mount and dslr back in the raspberryPi.

• Then on the raspi I exported those two with usbip.
• Then I imported them on the kstars client with usbip and my mount & dslr registered as if the would be normal local usb devices.
• Then I started one indiserver on the raspberryPi with the focuser only.
• Then on the kstars client I started indiserver with the raspberryPi-server AND mount & dslr driver as if they would be connected locally but the are via usbip.

Then I can start kstars and connect to the local server and everything works and image acquisition (fits) is fast as HELL
My first test running an hour is stable until now. It runs via LAN but I dont know how latency will influence usbip over Wlan.

Great!! I I am curious how WLAN would affect this setup as well.

did you by any chance find the time to test USB/IP via WLAN?

Yes, it varies from totally unusable to quite good depending on my wifi setup/enviroment. I used the EDIMAX EW-7811Un wlan stick and my TPLINK TL-WDR3600 Router driven by DD-WRT with very short distange, 4 Meters with glass door inbetween. Before you do your actual astro-session you should double check latency (ping) and speed test the connection. I had tests where the ping jumped between 120 and 2000ms and transferspeed stalled at 80KB/s wich made it unusable. I had to set my wifi "channel width" to "WIDE HT40 (40MHz)". 7MiB/s was the best value I got. OccasionallyI also have complete freezes of my USBIP client where kstars is running. I was not yet able to find the cause of this. My last 5 sessions where without any disturbances. Indi just run as expected.
It would be nice to hear from someone else denying any freezes on the client side.

greets
Paul

Thanks for your update, maybe I find some time to play around with USB/IP this weekend.