Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: position is not valid at CourseApi #1845

Closed
s2tenacity opened this issue Dec 11, 2024 · 2 comments
Closed

Error: position is not valid at CourseApi #1845

s2tenacity opened this issue Dec 11, 2024 · 2 comments

Comments

@s2tenacity
Copy link

This error message is flooding my signalk once a second making it nearly impossible to watch the data I want to see (signalk-to-nmea2000) which I have filtered out.

Dec 11 15:16:20 Error: Error: position is not valid at CourseApi. (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:687:27) at Generator.next () at /usr/lib/node_modules/signalk-server/lib/api/course/index.js:8:71 at new Promise () at __awaiter (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:4:12) at CourseApi.setDestination (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:643:16) at CourseApi. (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:179:43) at Generator.next () at /usr/lib/node_modules/signalk-server/lib/api/course/index.js:8:71 at new Promise () at __awaiter (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:4:12) at CourseApi.parseStreamValue (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:172:16) at /usr/lib/node_modules/signalk-server/lib/api/course/index.js:152:34 at Array.forEach () at /usr/lib/node_modules/signalk-server/lib/api/course/index.js:148:35 at Array.forEach ()
Dec 11 15:16:21 Error: Error: position is not valid at CourseApi. (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:687:27) at Generator.next () at /usr/lib/node_modules/signalk-server/lib/api/course/index.js:8:71 at new Promise () at __awaiter (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:4:12) at CourseApi.setDestination (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:643:16) at CourseApi. (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:179:43) at Generator.next () at /usr/lib/node_modules/signalk-server/lib/api/course/index.js:8:71 at new Promise () at __awaiter (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:4:12) at CourseApi.parseStreamValue (/usr/lib/node_modules/signalk-server/lib/api/course/index.js:172:16) at /usr/lib/node_modules/signalk-server/lib/api/course/index.js:152:34 at Array.forEach () at /usr/lib/node_modules/signalk-server/lib/api/course/index.js:148:35 at Array.forEach ()

Can somebody please tell me how to fix whatever it is complaining about (or at least hide it)? It seems inconsistent when it happens and I have not figured out what triggers it to start or stop showing.

@panaaj
Copy link
Member

panaaj commented Dec 12, 2024

A fix was created for invalid course.nextPoint.position values received via NMEA.

#1840

@s2tenacity
Copy link
Author

Thanks for that info. It seems that when you have navigation running on a B&G chartplotter and then cancel the route, the nmea data stream produces invalid data.

If I restart a route the issue is cleared. I believe power cycling the chartplotter clears the invalid data stream as well. This is the data that confuses CourseApi.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants