UCM 7.016

[ident]

1. UL and DL commands previously used to disable status reports on UCM until log in This prevented commands from being reported in Monitor I/O after upload/download
2. UCM reports CT and C? Counter with 2 bytes counter value eg CT013412 means counter 1 has value 1234H
3. C! Command accepts 2 bytes counter value eg C!103412 means set Counter 16 to value 1234H
4. When firmware upgrade of UCM by RS485 bus fails, a scan u? Will report version 7.000 instead of 6.000 so that the UCM can still be upgraded by Bus. UCM Firmware 6 cannot be upgraded by Bus

This firmware upgrade is important due to the last point above. UCM firmware version 7can be upgraded by Bus as well as by direct connection (by USB, ETH02 or RS232). When the upgrade by Bus fails for any reason (except for lost ethernet connection), it should be possible to repeat the upgrade by Bus. However, for older UCM firmware versions the UCM which failed upgrade wiill report as version 6.000, so Comfigurator will not allow the repeat of firmware upgrade  because only firmware version 7 can be upgraded. The new firmware 7.016 will report its firmware as 7.000 instead of 6.000 so the upgrade can be repeated.

This same issue applies to KT03 firmware which can be upgraded by Bus. There is a new Firmware KT 7.016 which fixes this potential problem

[slychiu]

Clarification on how the UCM firmware upgrade by Bus can fail;

1. The upgrade can be stopped by pressing cancel
2. there may be an error message to stop the upgrade

These will require the upgrade to be started again
However it is quite unlikelly that the firmware upgrade will fail

If there is a loss of ethernet connection for UCM/ETH02 Comfigurator 3.6.5 will ask \"Do you want to continue from the last address\". If you select OK, the upgrade will continue so this situation is not a problem. This is the more likely scenario