-
Notifications
You must be signed in to change notification settings - Fork 17
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
Defend against abnormal events #205
Comments
I keep getting stuck in
Which is I am using the reference design: Anyone using that as well? It happens when I start Anyone can help me out? @nomis52 @peternewman ? |
@peternewman : Do you have the OLA RDM test suite still running? Is there any Ja-Rule board we can order somehow, alternatively, if the reference design is not supported? |
Yeah, I ran some through a Number 1 at the recent Lille Plugfest seemingly without issues (aside from with the device under test). Is that what you meant?
The company that made the original batch of Number 1's aren't doing so anymore unfortunately. The design is here, but I'm not sure if it includes a PCB layout: |
@peternewman , thanks for your reply. We've met actually in Lille ;-), I was the one of Constell8/KLSTR. The hardware schematics are there of the Number1. But we bought the development kit of Microchip, which the Number1 was based upon. But can't get it working with that... |
One thing I found during testing today, if you disconnect the IC line, the unit 'locks up' when used as an RDM controller with one or more responders on the line. This is because without IC we never enter the STATE_C_RX_IN_DUB but the UART is still receiving and Transceiver_UARTEvent() is called repeatably.
This is symptomatic of a general class of 'abnormal' failures. If something happens that we don't expect, we should enter the ERROR state and reset the unit.
e.g.
That last line should handle the failure.
The text was updated successfully, but these errors were encountered: