Dear Paul,

I just tried to set my KStars and see what is happening. The difference is after launching the sequence - in my case, the path edit field stays active and the images are saved to where I specify (just with that problem with slash/ backslash). Maybe I would try to use different version of KStars - I am using the 3.6.3 Beta now.

I am sorry I cannot give you any better answer.

BTW: I checked the wired connection of my RPi to the laptop today and it is just amazing compared to the WiFi connection. Waiting for a clear night to check it "in vivo".

Clear skies, Michal

Thanks for the response, the only thing I can think is that I am using a DSLR where the save options in EKOS settings are listed as RAM or SD Card. I wonder if it influences the possible save paths.
Regarding the wired connection are you referring to via an Ethernet network or direct to the laptop. If so which method and cable are you using? I am new to Linux and the world of RPi and I'm using a Windows 10 PC.

Okay, so I figured out how to connect to the RPi by Direct Ethernet - WOW this is so fast now!!

But, still have the same problem that any time I choose "Both" or "Remote" then start a shooting sequence, the selection defaults back to "Locally"

Even tried shooting with my guide scope in case it was the DSLR causing the issue, but that does the same.

I even went into the INDI control panel and set the values there, but nothing works.

Tried changing the folder to /home/pi and /home/stellarmate, still nothing.

Is there something I am missing?

EDIT
I disconnected my PC, then attached an HDMI monitor and Mouse/Keyboard to the RPi
Created a local profile with the same equipment, and repeated the experiments, photos get saved into my desired HDD partition which is of course the "Local" location now.
So the system basically works, but when set up for remote access, it has a problem.

Dear Paul,
nice to hear that you were able to establish the ethernet connection! I just was preparing to answer your question I am now in the situation that I must resolve somehow how to lead the ethernet cable from outside to inside via a closed window, but I think the fixed ethernet connection is worth it.
But as for your remote saving troubles, I really do not know what could be the problem But, by the way, the behaviour of my KStars is such that the parameters of the sequence do not depend on the edit field with path anymore when the sequence has started. I prepare the sequence, i.e., I enter the exposure time, number of images, name of the image files, path..., then I press that "+" button up above the scheduler (right half of the screen) and then I start the shooting sequence with the "play" button. From this moment on, the sequence is being captured regardless to what I change in the left part of the screen (so if I change the name, the path..., it does not affect the sequence being exposed). If I realize that, for example, I would like to change the name of files, I stop the sequence, I withdraw it from the scheduler and with the "+" button I add a new sequence with corrected parameters. This means that it should not be important if your path gets ineditable after the sequence started. At least in my KStars. I hope I expressed myself in an understable way.

Clear skies,
Michal

A bendable aluminum flat cable is sold in Japan to pass Ethernet through a window.
Is there any in your country?

www.elecom.co.jp/products/LD-VAPFSV05.html

Wow! I have not ever seen this, thank you for a tip!
For now, I think I will start with a regular cable, as the gum window sealings have certain tolerance, but definitelly it is not a long-term solution. Thinking about making an ethernet socket on the outer wall of the house eventually (dont tell my wife).

Best, Michal

Tkakura,
www.elecom.co.jp/products/LD-VAPFSV05.html

Thanks for pointing that out, I was just pondering the same question. In my case I actually live in Japan (Nagano) so I'll be ordering one of these.

In case anyone is interested, if you do an internet search for "window flat LAN cable" you'll see many suggestions

Dear Michal,
I don't want to be taking over this thread, just want to report my findings so others might learn.

A strange thing happened last night.

With the same setup, RPi with 1TB HDD, and remote control via Direct Ethernet, I started EKOS and created a new gear profile. In this case shooting a sequence, resulted in images being saved on the RPi HDD. Results were;;
My desired path name was "/media/stellarmate/data/Pictures", but due to the method used to append \Light as a folder name (which I believe is inconsistent with Linux syntax (?) ) the resulting storage folder was "/media/stellarmate/data/Pictures\Light". That final part "/Pictures\Light" does not indicate a subfolder, it creates a single folder with the full name of "Pictures\Light". Odd, but not a major problem and it proves that I have no problem writing to the disk.

HOWEVER, the weird part is that in this profile, I can ONLY save remotely now!! I mean that if I select either of the options including a remote save onto the Windows PC, the save setting just reverts back to Remote only at the beginning of the sequence.

I ran out of time, but I will test again tonight. Now I am typing this, I am wondering if the save path name becomes set in stone as part of the sequence. I.E. If you set up more than one sequence, you can predefine that sequence 1 is saved remote only, sequence 2 is set local only etc.

Maybe I just need to RTFM but up to now I couldn't find any detailed explanation. The fun of exploration, right!!

The issue *should* be resolved for Windows but there are now build issues on Windows that we must resolve first.

For remote connections, all data, including images, are transferred over the network, so usability depends on network speed.

The current INDI server does not have a "Save image to server" option, so you will have to save it on a remotely connected PC. (Because all data is transferred to the remote client when you connect remotely)

If you are connecting an astronomical device to the Raspberry Pi 4, add a USB3 SDD to the Raspberry Pi 4 and connect with KStars on the Raspberry Pi 4 → save to the USB3 SDD because it does not require a slow network connection. , is the fastest. (Operation is remote desktop such as VNC)

PS.
Even if you add the "Save images to server" option, all the data will be transferred to the remotely connected PC, so more functions are needed for comfortable operation. (A function to transfer images and streams as lightweight preview data when saving images and streams to the server, a function to proceed with work at the stage of saving to the server, etc.)

If 10Gbit Ethernet spreads, it will be possible to operate comfortably even with the current specifications.

I did some more testing and finally resolved my main issue.
As a reminder, I have my scope being driven by a RPi4.
The Pi is booting off a 1TB HDD, I've created separate partitions for the OS and data on the disk.
The only reason I didn't use an SSD was I just had the HDD spare in a drawer.
Everything is driven by KStars running on a WIndows 10 PC, now connected to the Pi by Direct Ethernet.
Reason for going the direct cable way was initially because I was getting broken connection on wifi, even with the PC within 2-3 meters of the RPi.
However, the speed increase is so much improved that I will use this method for the future wherever possible.
I have already set up Samba and WSDD on the Pi so after a session, I can bring the Pi indoors, plug it into my network and copy all the images over the network to my editing PC.
EDIT - by the way, this video was key for understanding the Direct Ethernet setuo
www.facebook.com/stellarmate/videos/stel...net/782246335916948/

I have now managed to resolve the issue of remote / local saving of data, it was simply a matter of finally understanding how EKOS works. This excellent video by Jasem was a real help in final understanding.

The set of videos in that playlist are a little out of date, but still close enough to understand the principles, I just wish I'd found them earlier.

In answer to T-Studio above, I am now able to save all data only to the HDD on the RPi, as far as I can tell, now that remote saving is set correctly, no image data is coming over the network during a sequence. Only the preview data. This is with KStars running on the PC, not via VNC. I have tested functions through VNC, but I prefer the direct connection for my situation.

As a newcomer to this software since October, I have had more than my fair share of frustrations - unfortunately the documentation that I have been able to find is not matching with the capabilities of the software. If I could make one suggestion for this project it would be to update the documentation and ensure that it is easier to find.

I will add it so that there is no misunderstanding.

When connecting to a remote server, all data is transferred to the connected client.

Only a light preview is transferred and there is no setting to process and store the actual data in the server.

The speed is slightly faster and the reason why it became usable is as follows.

・The network connection has been changed to wired.

・It is now possible to specify the directory of the Raspberry Pi server mounted on the client side using the SAMBA server.

You changed your network connection to wired so it's faster than wireless, but much slower than doing everything on the client on the server machine.

You can see a noticeable difference in speed when using AutoGuide with a client connection.


PS.

I live in Karuizawa, so if I can speak Japanese, I can explain in detail.

I also write about INDI on my blog.

tstudioastronomy.blog.fc2.com/