2018-06-21, 04:26 AM
(2018-06-20, 11:47 PM)Smartell Wrote: Paddy,Congratulations! Seems like NASAMARINE will have seen this problem before. I guess they had a bad firmware version at some point. They will surely fix it if you send it back, but they are in the UK. They sent me a new circuit board when mine flooded (out of warranty by the time I got up to the masthead to take it down) at a decent price. Neither the old nor new one had your problem. I hope they have improved the seal (the replacement one they sent me was different than the original) but I am tempted to tell you to disassemble yours and seal it up with silicone for good measure.
It works!
FINALLY, we got the bI@@dy thing working!
Soo...Thanks for all your support !
To sum it up:
it was the missing linefeed in NASA's implementation of the NMEA protocol that caused all this misery. Not too impressive effort by NASA i must say.
I will engage in a discussion with them to see what they come up with. They also use the old unbalanced version of NMEA with (+), (-) and (TX)
Note that i am using a cheap Prolific chipset RS232/USB adapter without any advanced loopbacks, just three cables.
The (temporary?) solution was to use Node Red with a serial connection that i first confirmed to work and then connected to Paddy's code above which worked rather splendidly.
Next (yes i like windmills) i will try to connect my Seatalk to the system too
And then i will try to get Sailgauge to work on my Samsung Gear s3 ... keeping busy
And then ...
Sent from my Moto G (5) Plus using Tapatalk