View Single Post
Posts: 451 | Thanked: 334 times | Joined on Sep 2009
#921
Originally Posted by MartinK View Post
Can you check if the position is updated if you restart modRana ?
Yes, it is.
Also, try to enable "Show gpsd debug output" in Options->Debug->GPS, modRana will start printing the information it gets from gpsd to stdout.
I ran gpsd with debugging, and when it reads data from a regular socket file, created by socat, it's updated fine...

This certainly also possible - modRana already has a worker thread (in the location module that resides in modules/mod_location.py that reads position data from GPSD. The worker thread could be modified to connect to BlueNMEAs socket and parsing the NMEA sentences it provides. There is just a single stable source (BlueNMEA) without the usual quirks of standard GPS devices, the parsing should not be that difficult, at least for basic location data (latitude, longitude, elevation, speed, direction(?)).
This might speed things up for the chroot... However it thus seems the fault is with VNC, if it sends uncompressed frames, then no wonder it can't keep up while moving as it's updated continually.

I never messed with VNC, never really used it. Will try to look into it...

Anyhow, I currently see two possibilities for improvement when using VNC:

Currently, I use 24-bit color profile, to make modRana useable with the VNC viewer, otherwise the colors got distorted. Other possible viewer profiles are: 256, 64, and 8 colors, or greyscale, and black-and-white. So would it be possible to limit modRana's colors to 8 or max 64 on startup programatically? This would decrease the amount of data sent drastically?

Second, have an option in modrana to update the display only let's say every second, so that this would also decrease the data sent significantly?

This might make modRana useable under VNC?
 

The Following User Says Thank You to 白い熊 For This Useful Post: