Open APOS80 opened 4 months ago
Without tilt With tilt
Hope that helps
Thanks for reporting! I've got a demo version of Surpad working.
0.11m to 6555559m is a bit of a problem!
It makes me think that something changes with the NMEA message when enabling tilt.
Agreed. I suspect Surpad is parsing the NMEA in a different way. We are outputting (we believe) fully formed NMEA but there's always small changes. And different parsers can withstand varying levels of difference. AFAIK the lat/lon/alt NMEA sentences we output during tilt compensation is the same length and indistinguishable from non-tilt NMEA but obviously something is amiss.
Unfortunately I am out on vacation for a bit. I hope this doesn't block you from work for too long. I know you are capable of compiling the source so please poke at the problem if you have the desire.
I’m also going away for a while.
Sadly I haven’t solved the compiling part at this moment.
off topic: I’ve never done big stuff, only playing around with small stuff. As of now I’m trying to learn more SQL and Python for QGis work.
I wonder if it’s as simple as LF instead of a CR character or the other way around.
I've tried to replicate this a few times and can't yet. What version of Surpad are you using? What view are you in?
I'm using Surpad v20240612, with Everywhere firmware v1.3, using the Point Survey mode.
Data in and out of tilt compensation mode seem to work just fine.
I know there is a newer version of Surpad but my trial version is expired so I haven't been able to test it yet.
Also, in the release candidate we've removed an extra null terminator character from the output. But I can't say it fixed anything until I can replicate the problem.
I can try the release candidate and see if it works.
I was testing with v1.3 and I did not detect a problem.
What version of Surpad are you using? What view are you in?
I was in the measuring view
Surpad v4.2.220626.232644
I'm on v4.2.240104.164515. You might try upgrading. I'll see if I can find an older version of Surpad but after a quick search, it doesn't look possible.
I’m unable to upgrade my version as of now.
But are you sure the NMEA messages is correct after going into tilt?
Problem persists in v1.4
Everything is working for us. What version of SurPad are you using?
But are you sure the NMEA messages is correct after going into tilt?
Yes.
Subject of the issue
Describe your issue here. Additionally, screenshots are easy to paste into github.
Everything works well with SW Maps but not using tilt with Surpad.
Without tilt it works well but when enabling tilt Surpad thinks it’s thousands of kilometres away.
It makes me think that something changes with the NMEA message when enabling tilt.
Your workbench
Steps to reproduce
Tell us how to reproduce this issue. Please post any log files from serial output that may have been generated.
Expected behavior
Tell us what should happen
Actual behavior
Tell us what happens instead