PCAN-MIO

v3.4.10

Bug fix: In case the isolated High-speed CAN transceiver was used and the transceiver mode was standby or powerdown, messages were still received and could be forwarded

The CAN controller is deactivated if the CAN transceiver is set to standby or powerdown
Added support for the CAN transcevier module PCAN-Transceiver TJA1044-ISO (IPEH-001007)

Module crashed if a function block trigger was used and the triggered function block contained a conditional statement

Message gateway can now trigger function blocks in both modes "direct copy" and "message trigger" (was only "message trigger" before)

Readback of PWM dutycycle was incorrect if dutycycle was larger than 25% (internal overflow in calculation)

Data objects of receive messages with a timeout were set to their default values at startup. This caused a problem if "selfhold" (latch) was used in this type of receive message: module resets continuously after startup
Timeout after module shutdown was too short; sometimes module restarted again instead of staying asleep

Lower frequency measurement threshold was 6.25 Hz, now corrected to 2.5 Hz (maximum pulse time = 0.2 sec)
Several function blocks did not work correctly if negative parameters were used although negative values should be OK

In case more CAN IDs are received than message boxes are available (e.g. all 11-bit messages and more than 13 29-bit messages), it is required to use a double buffer for one type and a receiver for the other type via a single message box
In case IRQ latency is too high, the chance increases to lose one CAN message. Therefore, the bit rate for this condition was initially set to 125 kbit/s (1 bit time = 8 µs, minimum time for a CAN frame was 8 µs * 60 bit/msg ~ 0.5 ms). This maximum bit rate is now increased to 500 kbit/s (2 µs * 60 bit/msg ~ 120 µs time to process one receive message before overwritten by following message)