I run Kstars on PC in observatory and then connect through VNC with x11vnc. Even if connection gives up nothing happens because everything is running on observatory PC. Also I am connected through PowerLine adapter that gives me 100Mbit speed over 50m distance. So transfer of ASI1600 frame takes 3 seconds.
40Gbit?? You mean Mbit because there is no way to get that speed over wifi. Most likely you have unreliable connection which drops packets that can gives you slow transfers.
Read More...
Ok it was quite easy. I pushed changes that will now pass GPS start timestamp to SER recoder so if I didn't do any mistake it should work.
github.com/nouspiro/indi/tree/feature/qhy_gps_timestamp
github.com/nouspiro/indi-3rdparty/tree/f...re/qhy_gps_timestamp
Read More...
This line github.com/indilib/indi/blob/431869ffe40...serrecorder.cpp#L256 gets current computer time and write frame data to SER file.
On this line it is called new frame is pushed to Streamer github.com/indilib/indi-3rdparty/blob/da...hy/qhy_ccd.cpp#L2596
I think it would be quite straightforward put decodeGPSHeader() before call to Streamer->newFrame(buffer, w * h * bpp / 8 * channels, GPSHeader.start_sec + GPSHeader.start_us / 1000000.0);
Read More...
Yes SER does contain timestamps for each frame. Looking at code QHY driver does decode GPS info from camera but this doesn't seems to be passed down when recording SER stream. Only current PC time is used. Maybe "StreamManager" class could be modified that it scoop up this GPS timestamp.
Are you doing asteroid occulatations timing? I was experimenting with that and when I recorded GPS LED blink with my camera I found out that timestamp in SER file was within 5ms of blink start. I used chrony NTP client to keep my clock in sync. Doesn't that QHY cam burn timestamp into image?
Read More...
What exact problem are we trying to solve? Because SER already capture and save exact timing for each frame.
Read More...
Did they added credits in ASIAir app? bbs.astronomy-imaging-camera.com/d/13240...software-licences/29
Read More...
Hey I am working on XISF support in INDI. I have proof of concept done working. To test compile my branch.
github.com/nouspiro/indi/tree/feature/xisf_support
github.com/nouspiro/indi-3rdparty/tree/feature/xisf_support
KStars doesn't support it so you must fire exposure with indi_setprop. After you start KStars with simulator just run these two commands in command line
indi_setprop "CCD Simulator.CCD_TRANSFER_FORMAT.FORMAT_FITS=Off;FORMAT_XISF=On"
indi_setprop "CCD Simulator.UPLOAD_MODE.UPLOAD_LOCAL=On;UPLOAD_CLIENT=Off"
indi_setprop "CCD Simulator.CCD_EXPOSURE.CCD_EXPOSURE_VALUE=0.5"