-
Notifications
You must be signed in to change notification settings - Fork 0
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
Investigate "brownout" recovery issues #220
Comments
My theory is that the switch is browning out and that the event publisher is less robust than netcat |
What do you mean by "the event publisher is less robust than netcat"? |
The video feed recovers after a disconnect but the control software does not. You can see live video after a brown out, but joystick communication is lost |
Ok, but I don't know what you are getting at with "the event publisher is less robust than netcat".... |
Our event publisher and our usage of |
Robust meaning that it can handle more adverse conditions such as gaps in network activity |
raspivid->netcat->mpv connection can handle the switch power cycling, vs the eventpublisher->eventpublisher connection which cannot |
Running |
@FifoIronton Have you started looking into new thethers? Hopefully with a second conductor this wont be as critical an issue. |
Sorry about huge delay, still getting used to keeping up with Github, I need to adjust my email settings as not to get bombarded by miscellaneous messages. To do Saturday:
|
This seems like a big hack. Is there any way to create a current limiter on the just thrusters? I'd hate to see the tether get shorter, but it's better than brownouts I guess. As a side note; can you update the wiki to include the tether breakdown? |
I made a breakdown of the current tether options and put it on the wiki. As we don't have a finalised tether, it's more of a discussion than anything. |
With the new design this shouldn't be a problem moving forward for this year. Going to close this ticket and re-open it at a later date if necessary |
Currently the video feeds seem to recover when the vehicle's 12V bus browns out, but the control software does not. A few things need to be looked into:
service eer status
/systemctl status eer.service
show partial output butjournalctl -u eer.service
shows literally nothingThe text was updated successfully, but these errors were encountered: