-
Notifications
You must be signed in to change notification settings - Fork 40
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
Technic Control+ Hub gets disconnected on "notify" (raspberry pi 4) #21
Comments
Tried to delete vext and vext.pi. It got connected once again and after just a restart stopped working again. Here are logs without vext for the case it helps somehow:
|
Hi, I managed to get my 42100 to work using the fork from janvrany. |
I'm trying to connect to my 4100 excavator from raspberry pi 4, but it gets disconnected right after connection. What I discovered is that connection won't drop until "notify" message is sent to socket, but I can't find out why it happens. No error or other clue appears. I'm starting to think there is race condition because it got connected once and started controlling motors. After I turned off bluetooth on raspberry, turned it on again and restarted my script with no code changes, it doesn't connect again. Here are logs:
If I comment out line line 112 in
bricknil.ble_queue
(await self.ble.in_queue.put( ('notify', (device, char_uuid, bleak_received) ))
), it doesn't disconnect, but motors don't move.Can anyone help?
The text was updated successfully, but these errors were encountered: