CANNY 7.2 duo, System Registers
System resources are divided into an address group of read registers and an address group of write registers. Referring to the given registers from the functional diagram, you can get demanding information for practical application about the current status of the controller, and control its operation mode. The set of system registers located in the "System Registers" directory of CannyLab IDE registers list, which is available via "Input Register" and "Output Register" context menu.
Controller reset occurs as a result of any of the three events: when power up the controller, soft reset from the functional diagram. The controller is initialized after reset: the entire memory contents is cleared, input-output channels are reset to a neutral state, system software drivers are transferred to the initial state, power consumption is set to normal, a functional diagram execution starts from the beginning. The non-volatile memory content does not change at reset.
Information about the reset is available by accessing the address "Power On Detect Register"
|Power On Detect Register||
Forced reset of the controller is performed by writing a nonzero value to "Reset Register" address. In this case, the controller reset takes place immediately after the end of the execution cycle of functional diagram, in which there was such a record.
The controller has a built-in bi-color (green/red) LED. The functional diagram controls switching-on of each color by writing specific values into the appropriate registers.
|Green LED On/Off Register||
|Red LED On/Off Register||
|Note:||Turning the LED simultaneously in both colors is unavailable, so if functional diagram set simultaneous switching on of Red and Green LEDs, the LED turns green only (green priority).|
A functional diagram fragment, which turns on built-in Green LED for one second after each controller reset.
After reset, the controller starts working at normal power consumption, functional diagram will be executed continuously. Transition to Hibernation Mode carried out by the command of functional diagram will record a non-zero value to "Sleep Mode Enable Register". Transition to Sleep Mode takes place immediately after the end of functional diagram execution cycle, in which such recording was made, in the absence of conditions that impede this transition.
The duration of the sleep phase is 1024 ms. This means that while controller is in low power mode, or in the absence of conditions for transition to the normal power, the controller makes a pause of 1 second after each execution cycle of functional diagram.
|Sleep Mode Enable Register||
Returning controller to normal power can be done manually - immediately after the end of the execution cycle of functional diagrams, during which it was written "0" at "Sleep Mode Enable Register", or automatically by any of the following events:
- with changing of the electric potential in any terminal with the appropriate controller channel, configured as an active input / edges counter;
- when enabled from the functional diagram of any of the drivers CAN, LIN, UART/RS232 with changing of the electric potential on the corresponding drivers' terminal.
|Note:||Information about changes in the electric level at the controller contacts corresponding to the channels configured as an active input / edges counter, and changes in the electric level at the controller contacts corresponding to the activated CAN, LIN, UART driver, etc., is available to the user through a special controller status register - "Interfaces Activity Control Register."|
Information on the current power mode is available when accessing the address "Sleep Mode Control Register"
|Sleep Mode Control Register||
|Note:||When creating a functional diagram, using low-power mode should be considered as a side effect brought by the change in the time scale. This effect manifests itself in functional blocks increment time: delay start, stop and PWM generators in a low power mode occurs in leaps and bounds according to the time actually spent in the phase of "sleep" (default 1024 ms increments).|
A fragment of a functional diagram with typical low-power mode control: transition to the low power mode in the absence within 10 seconds conditions preventing it and automatic return to normal mode due to controller periphery activity or set ban to "sleep" from the diagram:
|Note:||Inversion of the output of the function block №1.|
Function Diagram actual run time
The time required for the controller to perform functional diagram in actual conditions depends on the number and type of functional blocks present in the diagram, the number of drivers involved in the system software and their activity. In practice, CANNY 7.2 duo execution cycle of a diagram contains about 450 function blocks and is actively interacting with CAN driver, lasts approximately 5 ms.
|Note:||When creating a functional diagram, the effect of execution loop duration should be considered. The effect is reflected in the fact that the increment of functional blocks time counters- start/stop delays and PWM generators occurs abruptly. Thus, when the actual cycle length of 5ms, all PWM generators actual period on the diagram is a multiple of 5ms.|
Information about the length of functional diagram previous execution cycle is available at "Last Execution Loop Duration Register".
|Last Execution Loop Duration Register||
The most accurate way to measure the total time of the controller operation, such as the implementation of the clock is the summation with accumulation of the values obtained at "Last Execution Loop Duration Register" during each execution cycle of functional diagram.
A fragment of a functional diagram that implements a high-precision seconds counter is suitable for use in real-time clock:
In the manufacture of CANNY 7.2 duo controllers, each of them is assigned its own identification number, which can be used later in the development of user diagrams to further protect them from unauthorized use.
Access to the device identifier is carried out via relevant special system registers.
|Device ID Register D1:D0||
|Device ID Register D3:D2||
During custom diagram development in CannyLab, the device ID, can be found by accessing device information available in the section "Device" → "Information" of main menu or by clicking the "Information" toolbar, where it is represented in 4-byte (32-bit) number, with the location of the high byte on the left.
For example, the identifier 0x563B8693 as followed: Device ID Register D1:D0 is equal to 0x8693, Device ID register D3:D2 is 0x563B.
Example - functional diagram illustrating an operation with the device identifier. In the diagram a value read from device identification registers is compared with the given and if they match, the network will display "ID is correct" saved "1".
In the manufacture of CANNY 7.2 duo controllers, each of them is assigned an identification number of their vendor (supplier), which can be used later in the development of user diagrams to further protect them from unauthorized use.
The device vendor identifier assigned by the controller manufacturer is the same for all controllers intended for one counterparty, or can be installed separately on a specific batch of controllers. To manufacture controllers with a specific vendor identifier, you must contact the manufacturer.
Access to the vendor identifier is carried out via relevant special system register.
|Device Vendor ID Register||
During custom diagram development in CannyLab, the device ID, can be found by accessing device information available in the section "Device" → "Information" of main menu or by clicking the "Information" toolbar, where it is represented in 2-byte (16-bit) number, with the location of the high byte on the left.
Example - functional diagram illustrating an operation with the device vendor identifier. In the diagram a value read from device identification vendor registers is compared with the given and if they match, the network will display "VID is correct" saved "1".
Interfaces Activity Control Register
"Interfaces Activity Control Register" - a synthetic register that show the current activity of the external interfaces of the controller present in the user diagram, or activated in the counter mode / the active input mode of the input-output channels. At those times when no signals are received or transmitted via the CAN, LIN, UART controller’s user interfaces and/or no changes in the electric potential occur on the controller contacts corresponding to the active input channels, the value "Interfaces Activity Control Register" contains "0".
The use of this register is convenient in the algorithms for controlling the energy consumption of the controller.
|Interfaces Activity Control Register||