This is by design actually.
The code is designed to emulate different frsky sensors. If you disable FLVSS, its stops reporting voltage as FLVSS. It still emulates a FAS-sensor though, so the voltage you see is from voltage/current sensor.
"There is no problem with the coordinates using this code and a Teensy 3.1 board.
The gps-coordinates is sent as 32 bit values. If the problem is isolated to gps-coordinates, I would start by making sure that these 32 bit values is handled correctly…"
"I don't know the correct terminology but basically the coordinates are expressed in degrees. This is what you see in mission planner. The coordinates are expressed as degrees with decimal points.
You can also use minutes and seconds to express the…"
"That's strange. I'm in the N/E quadrant, but the numbers I get is exactly the same in my Taranis as it's reported by Mission Planner (after a manual conversion from degrees in Mission planner to degrees and minutes in Taranis)."
"Unfortunately it seems like the the resolution of A2 is only 8 bits.
The current implementation is sending hdop /4. If you configure A2 with a range of 1024, you should get a close enough value of the actual hdop.
You don't need the scripts if you…"
"Thanks, I've implemented the byte-stuffing algorithm as you described it (I don't have the protocol specification). I did some quick testing and it seems to work, but please report if you find any abnormalities."
"Thanks for the report. I've changed the checked in version to look for the bmp's in /BMP now.
But remember that the code/scripts in master is experimental and will constantly change, and not always work. There are currently no stable release of the…"