I make the assumption this is a build from Master? Maybe too close living on the edge as in Skysafari client, Toup items not up to date with 2.0.0 ?
Watchdog client was also updated for the same 2.0 API's
FWIW: A build out of tag v1.9.9 functions as it should, master is broken.
Are you running off the latest master pull built from source?
There are quite a few changes between master and tagged 1.9.9, indi-core included.
It seems one of the updates between 1.8.9 and latest broke the internal interface between skysafariclient.cpp and skysafari.cpp
Wanted to see how much affect binning the v2 NOIR to 2x2
Images shot through a 30mm x 120mm mini guide scope from my highly light polluted skies
File changes required
diff mmalcamera.cpp mmalcamera.cpp.orig
< // selectSensorConfig(0 /* What ever 0 means */);
< selectSensorConfig(4 /* What ever 0 means */); // Mode 4 = bin 2x2
> selectSensorConfig(0 /* What ever 0 means */);
diff raw10tobayer16pipeline.cpp raw10tobayer16pipeline.cpp.orig
< // assert(raw_width == 4128 || raw_width == 3264);
< assert(raw_width == 4128 || (raw_width == 3264 || raw_width == 2080)); // v2 Mode 4 raw_width = 2080
> assert(raw_width == 4128 || raw_width == 3264);
< // assert(xRes == 3280 || xRes == 2592);
< // assert(yRes == 2464 || yRes == 1944);
< assert(xRes == 3280 || (xRes == 2592 || xRes == 1640)); // v2 Mode 4 width = 1640
< assert((yRes == 2464 || yRes == 1944) || yRes == 1232); // v2 Mode 4 height = 1232
> assert(xRes == 3280 || xRes == 2592);
> assert(yRes == 2464 || yRes == 1944);
Plate solve result:
Solved in 12 seconds , offset 45.56' , FOV 98.78x74.21' , 1.81"/pixel
06:24:52 Center, apparent coord. RA=01h28m01s DEC=+03d24m12s PA=208.1, J2000 RA=01h26m51s Dec=+03d17m07s
Solved in 6 seconds , offset 22.39' , FOV 98.55x74.04' , 3.61"/pixel
18:06:53 Center, apparent coord. RA=01h26m16s DEC=+03d33m42s PA=214.0, J2000 RA=01h25m05s Dec=+03d26m35s
Image are near NGC520
Mode 0 no bin 10 second exposure, 16 set for GAIN
Is there a way to get Astrometry logging in Kstars/Ekos 3.6.0 32 bit?
Ekos configured for:
Now whatever is set for
Nothing shows up for Astrometry logging anyplace
The VNC server is launched at startup by systemd.
To find which VNC server is running, would you type
ps -aef | fgrep vnc
And report the output of the above command.
On my astroberry, I see the following
root 548 1 0 12:45 ? 00:00:00 /usr/bin/vncserver-x11-serviced -fg
root 558 548 0 12:45 ? 00:00:00 /usr/bin/vncserver-x11-core -service
root 593 1 0 12:45 ? 00:00:00 /usr/bin/vncagent service 15
astrobe+ 899 1 3 12:45 ? 00:00:02 /usr/bin/python2.7 /usr/bin/websockify --log-file=/var/log/astroberry/novnc.log --web=/var/www/novnc/ 8080 localhost:5900
astrobe+ 996 1 1 12:45 ? 00:00:00 /usr/bin/vncserverui service 16
astrobe+ 1027 996 0 12:45 ? 00:00:00 /usr/bin/vncserverui -statusicon 5
What SM version are you running? Is it 64bit buster based? If yes, what window manager are you running?
Have you seen the 'mutter' discussion?
And Alacant's hint on noxdamage switch could help with the server side.
On the viewer side, there is an 'options' dropdown where you can set various connection options that may also help.
Astrometry logging should look like the attached. I cannot get any of this detail logs with 3.6.0
Ok, I get it. The server is the PI, the client/viewer is the PC
You may want to try running straight Tight VNC Viewer
Latest version is here:
Instruction for install is here (using version from above) for viewer only.
When installed, launch it, put the IP address of your Stellarmate and I -believe- using the password and port given here:
Port 5900 is standard port for VNC client to server communications, no web browser.
With VNC viewer, it will be like have a monitor/mouse/keyboard attached directly to the stellarmate.
Sorry, I do not have Stellarmate so cannot verify.
The VNC server on the PI supports multiple formats for sending data to you VNC client.
The client can make the request for the format.
Where are you running the VNC viewer/client? On a PC/MAC/ to view the astroberry screen?
On your astroberry, what network config do you have?
Is your PI connected to a router or are you connecting direct from PC/MAC/other to the PI?
Being hardwired network with CAT5 I really would not expect much latency/delay.
I use TightVNC Viewer/client on PC, the image is example of the config items available.
One thing that would help is having functional logging for astrometry.
I am running Kstars 3.6.0 32 bit
Ekos: INDI + Alignment
Astrometry:: LOG_ALL, SeperateLogFile, /tmp/astrometryLog.txt
I can choose any of the LOG_ALL/LOG_MSG, etc and get no files in /tmp dealing with logging.
Is your astroberry running in wifi AP mode or client mode?
What VNC client are you using? Cheapest way is to go to 8 bit/256 color mode but your will lose dynamic range in any images viewed.
You can play with other settings also in the VNC client. The way I 'test' is to have a 'busy' background on the desktop then overlay another smaller window on top then grab the smaller window and move it around rapidly.
If you are running astroberry in wifi client mode, you can check your wifi link using utility 'wavemon'.