Open thetestgame opened 2 years ago
In the protocol there is no concept of heartbeat. The hubs have a very strange initial connection mode but aside of that it is a very simple protocol on the frame layer.
This is a bit strange considering that StartPower is one of the most basic commands.
I guess this is the hub shutting down. Question is why:
This is repeatable after sending only one command after the initial connect call. Also the Hubs I've tested with work fine otherwise with the controller or the Lego app. Far as I know I have a standard BT setup. Its stock with my DELL machine if its worth mentioning.
Have you had the chance to test it on another device? I have no trains, it worked last time I used it (tm) with a technic hub and motor and right now I am in an actual train so hard time supporting you 😂
Creating a trace file would be helpful. I could verify the correct encoding there and check the exact place the thing fails
Have you had the chance to test it on another device? I have no trains, it worked last time I used it (tm) with a technic hub and motor and right now I am in an actual train so hard time supporting you 😂
I have not. I'll try that later today.
Creating a trace file would be helpful. I could verify the correct encoding there and check the exact place the thing fails
Do you have a preferred tool for trace files?
Additional bit of information. It seems to disconnect/stop on its own regardless if I send any new commands. Also sometimes it keeps working flawlessly but its rare. When the abrupt stop happens the light on the hub is still on like its connected but the object has been disposed from .NET.
Which Hub ist it exactly? The train one with the motors or the default Lego two port hub?
I'm using the Lego two port hubs from the RC trains.
I do not have any and I do not remember special behavior for them. They are a late product like the technic hubs.
After a few seconds and one command being sent to a Lego hub it abruptly closes the connection. Is there a heartbeat step that needs to occur? This is currently guaranteed to happen every time I try with my current codebase.