| Type ID | Module ID range | Type | Remarks |
|---|---|---|---|
| 0 | 0 | controller | There should be one controller per CAN network, and it should use ID 0. |
| 1–255 | info | ||
| 1 | 0–255 | puzzle | |
| 2 | 0–255 | needy | |
| 3 | 0–255 | reserved |
| ID | Issued to | Module name | Remarks |
|---|---|---|---|
| 1 | redfast00 | Serial number module | |
| 255 | private use | Development | Used before receiving an ID from MOANA. |
| ID | Issued to | Module name | Remarks |
|---|---|---|---|
| 255 | private use | Development | Used before receiving an ID from MOANA. |
| ID | Issued to | Module name | Remarks |
|---|---|---|---|
| 255 | private use | Development | Used before receiving an ID from MOANA. |
During development, you may use the development identifiers. To participate in games, you should request a unique ID.
You can request an identifier in the ~obus channel on the Zeus Mattermost. Use this template:
**MOANA – Request for OBUS Module ID**
My name, for the "issued to" field:
Module name:
Module type: puzzle needy info (remove what does not apply)
Remarks: You see an armed time bomb but don't know how to disarm it. Your friends found a manual to defuse the bomb and you have them on call. This is the premise of the game OBUS, a hardware project by Zeus WPI.
OBUS consists of different modules (a controller, puzzles, needy modules, info modules) that are connected on a CAN bus. To make sure each module has a unique identifier, MOANA was created.