there will be no transfer on bluetooth… when we use the NMEA Format, is working.
When we use bluetooth connection there must always be a postion output, also when Reach RS has no position right now. So that our app know about the state, currently it’s like a disconnection, when reach rs has no valid position data.
Can you please fix it for LLH format.
Alternativ you could add a NMEA output with the missing datas for RTK: ratio, time, basedistance, that would be a better solution for us.
LLH and NMEA formats have its own specified structure. NMEA can be outputted without any position data as it has messages names which are always present in its stream. As for the LLH, there’re no such parameters and it can’t be streamed without coordinates.
Just want to clarify, that theoretically, it’s wrong to use 0.0, 0.0, 0.0 position when there’s no valid position.
As 0.0 0.0 0.0 is a real coordinate on the surface this can lead to issues with the positioning of the system.
I’d recommend you to use NMEA output if it’s vital for your project to have data input while no valid position available.
but not when all values are set to zero:
LLH: 2018/12/21 11:51:15.600 0.0 0.0 0.0 0 0 0.0 0.0 0.0 0.0 0.0 0.0 0.00 0.0
because Number of satellites of 0 is not a real thing or you could use the Navigation Status (Q=1:fix,2:float,3:sbas,4:dgps,5:single,6:ppp) with zero for none valid position…it would be very nice to implement that, because the workaround with NMEA has missing information like: Age of differential corrections and ar ratio.
it would be also possible to simply add a new NMEA Tag where the missing information are containing.
I think I was unclear in my previous message. Just wanted to say that it’s not right to use custom LLH message type in Reach as it creates a false impression that the device is working normally and has a valid position. That, in turn, can lead to issues in the operation of 3rd-party devices and software.