|
This will be used by the Interlock Solution
Reference | Location |
---|---|
GitHub Repo | |
CANopen-stack: | |
CAN In Automation Web | CiA 301 Spec: |
CAN Open Wiki | https://en.wikipedia.org/wiki/CANopen |
# | Title | User Story | Importance | Notes |
---|---|---|---|---|
1 | CAN Bus enabled | Control of the node will be done over CAN-FD from the primary CANtroller of the interlock system. | Must Have |
|
2 | uController in node | a small uC will generally be required in order to handle the CAN bus and the desired sensors. The uC should be relatively generic, such that if it needed to be changed it could be replaced with a different device. | ||
3 | Safety | The device needs to be safe, and should exceed basic safety ratings. | Critical for Safety |
|
4 | Voltage Measurement | Nice to Have / Future |
| |
5 | Current Measurement | Being able to determine if the machine is on/off by current measurement will be useful. | Nice to Have / Future |
|
6 | Wiring | Much of the wiring in the device will handle high currents and high loads, and will need to survive for years. | Critical for Safety |
|
7 | Indicators | A user should be able to see the status of the device easily when near it. | Must Have |
|
8 | Termination | CAN bus needs termination | TBD |
|
9 | Contactor Unit | The system should use a NEMA General Purpose Contactor. |
|
# | Title | User Story | Importance | Notes |
---|---|---|---|---|
1 | GitHub based S/W | Future developers and maintainers will want access to the code. | Critical |
|
2 | CAN Library | CAN library should ideally be common between the CANtroller and CANtacter | Nice to Have |
|
3 | CAN Usage | The usage of the CAN bus should be very well defined and common between CANtroller and CANtacter | Must Have |
|
4 | Node ID | Each node should have a unique ID and should be able to | Must Have | |
5 | Prevent_Off_when_running | Cutting power to a high powered device while it is in operation can be damaging. | Must Have |
|
6 | 11bit vs 29bit addressing? | TBD | ||
7 | TBD |
Include any mockups, diagrams or visual designs relating to these requirements.
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
---|---|
Brooks Przybylek: Out of curiosity, why not a web server with an api and just have the interlocks on the network? I’m not sure how reasonable a load that’d be for the network but if you’re doing esp the hardware is there and no need to worry about wiring, power will be at the device anyway | Jack: a web server could always be added later... as a function of the controller. I wasn't planning to put one in the contactor box... as I'd rather not have power on/off to the machinery changed without the local controller being involved. (the CAN bus would be from the controller to the contactor) |