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

Lux client connection error #11

Open
AndrewMusser opened this issue Dec 7, 2023 · 3 comments
Open

Lux client connection error #11

AndrewMusser opened this issue Dec 7, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@AndrewMusser
Copy link
Contributor

Describe the bug

The jsonWebSocketServer FUB reports error 50004 when a Lux client first attempts to connect. The ErrorString reported is THAT$'s NOT POSSIBLE. The issue only appears intermittently, and appears to primarily occur after doing a clean, rebuild, followed by an offline install. Note that this has only been tested/seen in simulation.

When the issue first appears, the jsonWebSocketServer.ClientInfo[0].ClientPort is continually incrementing, which shows the the ws connections are getting closed or dropped, and being re-established.

To reproduce

Follow the LPM bootstrap guide here: https://loupeteam.github.io/LoupeDocs/tools/lpm/guides/bootstrapping-a-project-with-lpm.html

Expected behavior

The client should connect automatically when the HMI is started, and the ClientPort should keep a fixed value. There should be no error on the FUB.

Additional information

Happens with version 1.4.0 of OMJSON.

@Joshpolansky
Copy link
Member

Joshpolansky commented Dec 7, 2023

From the original troubleshooting it looked like there was a connection timeout that wasn't getting reset. after fixing that, what is the new behavior?

Also, is this a bug in OMJSON or the websocket library?

@AndrewMusser
Copy link
Contributor Author

AndrewMusser commented Dec 7, 2023

The connection timeout fix was incomplete, as the timer wasn't being called before its .IN was forced back to TRUE. Currently experimenting with rearranging the timer logic to see if it fixes it.

The issue appears to be coming from the jsonWebSocketServer.c file in OMJSON.

@Joshpolansky
Copy link
Member

Is this solved now or is it still getting the error sometimes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants