-
Notifications
You must be signed in to change notification settings - Fork 7
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
No response to @PRS commands #18
Comments
@rpineau Which firmware version was this please? |
I believe these log come from people using the 3.0.0 firmware. |
I can’t remember what state that pull request is in. There’s a new build due out within a day or two, probably best to wait for that. I’ll email you when I release it.
Best regards,
Tim Long
|
ok, I can wait and retest once 3.1 is out (or a pre-version so that if this is still and issue it can be fixed before 3.1 is released). |
So now that 3.1.0-Beta.6 is out, I'm having another look at this. My eye is drawn to this part of the log:
You seem to be getting two responses to the When you send the second one, that's clearly not answered and that is (or was) a bug. I think this one should be fixed by PR #17 . There was a race condition where a command could get lost if it happened right as the XBee state machine was polling for an active connection. This race condition should now be eliminated. |
I'll re-run some test with log enabled and check if this is still the case. |
Hi Tim.
Based on a few lofs for 2 users I see timeout every time I request the shutter position 👍
as you can see I do get some of the inline messages, like the XBee online status and no actual :PRSxxxxx response to the @prs command, but I do get the same response as the previous command (which was a @prr in this case).
So there is either a timeout in the XBee communication with the shutter or in the firmware somewhere.
Is there a minimum amount of time required between commands ?
The text was updated successfully, but these errors were encountered: