2022-02-16, 09:23 PM
The split screen is some sort of a preview - running 2 avnav instances in one browser window.
You can reach it with http:/xxxx:8080/viewer/viewer_split.html.
Will be a bit slower as it really runs everything 2 times. In the future this will be completely integrated.
For the SK stuff . yes you can display everything from vessels.self in AvNav.
Just use the layout editor - it will show all pathes from sk that currently have data in them (so you need to feed SK with data first
).
If you miss some formatter or some nice settings for the gauges - this can easily be achieved with a few lines of js code.
For the pi CPU usage:
What else do you run on the pi?
AvNav itself should be low on CPU. If you use o-charts the ocharts plugin will use a complete CPU for some time as it pre-renders charts for faster display later on. But you have 4 CPUs (i.e. 4 kernels) - so also at most around 25% of the whole system.
But if you run the OP desktop stuff (or even a VNC server) - this really consumes CPU and memory.
You can reach it with http:/xxxx:8080/viewer/viewer_split.html.
Will be a bit slower as it really runs everything 2 times. In the future this will be completely integrated.
For the SK stuff . yes you can display everything from vessels.self in AvNav.
Just use the layout editor - it will show all pathes from sk that currently have data in them (so you need to feed SK with data first
).If you miss some formatter or some nice settings for the gauges - this can easily be achieved with a few lines of js code.
For the pi CPU usage:
What else do you run on the pi?
AvNav itself should be low on CPU. If you use o-charts the ocharts plugin will use a complete CPU for some time as it pre-renders charts for faster display later on. But you have 4 CPUs (i.e. 4 kernels) - so also at most around 25% of the whole system.
But if you run the OP desktop stuff (or even a VNC server) - this really consumes CPU and memory.