System State
The Command Group 0x00 summarizes all system 'High-Priority' commands and must be implemented by all boosters and drive consoles.
With Cmd=0x00/M=0b00 the power status of the respective device can be queried.
A query immediately after a Power Command can lead to inconsistent answers! After a Power Mode Command the device (specified by NId, e.g.: MX10, StEin, ...)) changes to the desired mode, but this is only reported AFTER the internal control loops have executed the change and it is verified by measurements. This process can take several 100ms depending on the desired change!
With Cmd=0x00/M=0b01 the port power status of the device can be set. The current status is 'acknowledged' by Cmd=0x00/M=0b11. The valid status is also included in the regular (approx. 500ms) power message.
The object ports are binary coded and this combinations are allowed:
| Port | Output |
|---|---|
| 0b00000001 | Rail 1 |
| 0b00000010 | Rail 2 |
| 0b0………. 00 | Track 3 ... 7 (Further MX10 in booster mode) |
| 0b10000000 | Booster output, resp. track output 8 at MX9/StEin |
Therefore, to switch ALL outputs with one command, port 255 (=0xFF, =0b111111) must be used.
If several outputs are switched at the same time, the confirmation still takes place individually for each of the 'existing' ports. So if e.g.: no further MX10 is available in booster mode, there will be NO ACK for these non-existent rails!
Applications (whether via PC interface or one of the internal bus systems) should ALWAYS wait for the ACK of the MX10 after a power mode change. ALWAYS wait for the respective ACK of the MX10, which basically makes a 'query' unnecessary.
Receiving
When receiving command 0x00 the 'Data' section will look like this:
| Device NID | Port | Mode state |
|---|---|---|
| 16 Bit | 8 Bit | 8 Bit |
Sending
When sending command 0x00 the 'Data' section will look like this:
| Device NID | Port | Mode state |
|---|---|---|
| 16 Bit | 8 Bit | 8 Bit |