Forum Replies Created
- Posts
When I do a disconnect and reconnect I have a maybe 1 in 20 chance of getting an update (vs. last value seen). I have never seen an automatic update after the comm error.
I also sometimes see a log pause when connecting, like something is getting reset. After this reset I often see a locked GPS and lat/lon/etc.
If there is value to you in this I’m happy to provide data/debug. I’m also happy to get the GPS unit you recommended as a solution.
On the specific GPS unit I am using, this is something I have had for a long time and use it with various software and have a high degree of confidence in it, it also works great with the u-center software provided by ublox. It would also be interesting to know what GPS you have tested with and if any use ublox chips.
on the baud rate I am set at 115200. 2k is a fair bit of data, I may not be compliant with your timeouts.
thanks for the help.
I managed to connect, I get a lat/lon/locked/other info in the GPS control panel but I also get an almost immediate “Comm Error”.
Does Spike stop using the GPS after the “Comm Error”, or will it continue to parse the serial stream? Seems like it stops.
I suspect the GPS is sending sentences Spike can not parse, it would be nice if it would ignore those and keep looking for updated lat/lon/other data.
Software is Windows 10
Device is Reyax RY636AI (https://reyax.com/wp-content/uploads/2017/09/RY636AI.pdf)The string looks like this — $GPRMC,123456.80,V,,,,,,,123456,,*16
I changed my actual data with the 123456. The string does look a bit abbreviated, perhaps that is the issue?
