CYCLADES-PM FAMILY RELEASES



This document brings all new features and bug fixes regarding PM8/8i/10/10i/10DC/20/20i versions (Including BETA versions which have a letter after the version number).


V_1.9.0 Aug/04/06:  (official release; upgrade from V_1.8.0)

a) New features

·                Outlet-related commands (on, off, cycle, lock, unlock, etc.) process outlets in the order of the outlets in the command, instead of in numeric order.
·                Commands that have IPDU number as argument will also accept the IPDU ID.
·                Outlets can be defined as <IPDU id>.<outlet number in the IPDU>.
·                Outlet ranges whose first number is greater than the second number (example: 128-1) are accepted.
·                "voltage" command was created for future IPDU models with voltage sensor.
·                "humidity" command was created for future IPDU models with humidity sensor.
·                "hwocp" command was created for future IPDU models with hardware over current protection.
·                "dbsync" command was created to synchronize the user database in the slave IPDUs with the one in the master IPDU.
·                "factory_defaults" command can be issued for a specific IPDU (bug #7228). In this case, the user database will not be erased.
·                Loopback for admin password reset works in daisy-chain; the loopback connector should be placed in the OUT port of the last IPDU in the chain (bug #7324).
·                Corresponding boot code (version 1.2) supports code banking and can load opcodes bigger than 57344 bytes. It can only be upgraded with FlashLink.
·                Corresponding boot code (version 1.2) skips the menu interface if the firmware flash is empty (bug #7417).
·                Unnecessary outlet activation/deactivation will be skipped during hard boot, soft boot (in IPDUs that turn off the outlets during reboot), configuration restoring ("restore"), and configuration resetting ("factory_defaults") (bug #7405).
·                "help" command displays only the commands the current user (whether admin or not) can access (bug #7451).
·                Watchdog timer is enabled for all models that don't turn off all outlets during reboot.

b) Bug fixes

·                "cycle" command turns off all outlets in the list before turning on the first outlet.
·                "list" command in a daisy-chain is consistent even if the IPDUs are removed or change position.
·                Firmware upgrade works with XMODEM from TeraTerm, though it leaves some garbage in the command prompt due to an unexpected packet received from TeraTerm after the end of the transfer.
·                Current protection configuration is saved in flash (bug #7212).
·                "upgrade" command waits for the echo before bypassing characters (bug #7239).
·                "id" configures properly the IPDU ID when the ID reaches the maximum size (8 bytes, in version 1.8.0) (bug #7224).
·                Help for "current" command includes "reset" option (bug #7247).
·                Help for "interval" command includes displaying the current configuration if duration is not provided (bug #7358).
·                Help for "currentprotection" command is more descriptive (bug #7412).
·                Help for "name" command includes statement that the name cannot start with a number (bug #7418).
·                During soft reboot, reference to IPDU #0 is removed (bug #7215).
·                "assign" and "unassign" commands do not accept admin user as parameter (bug #7226).
·                An error is displayed for every wrong outlet name, number or range (bugs #7226, #7236).
·                Numeric parameters, such as outlet number or range, power-on interval, and alarm threshold, have their values checked more strictly (bugs #7220, #7221, #7222, #7227, #7238, #7245, #7264).
·                "restore" command works properly in daisy-chain (bugs #7234 and #7235).
·                "upgrade" command does not accept IPDU numbers that are greater than the number of the last IPDU plus 1 (bug #7290).
·                "upgrade" command in daisy-chain terminates when boot code resumes booting instead of upgrading firmware (bug #7260).
·                IPDU ID and outlet name cannot be duplicated in a daisy-chain unless they are set up separately before (bugs #7266 and #7267).
·                "restore" command uses the power-on interval value stored in flash to turn on the outlets (bug #7397).
·                Commands that request IPDU number (except "upgrade") return error message when the number is not found in the chain (bug #7398).
·                Commands that request usernames remove trailing spaces and don't allow space characters in usernames (bug #7409).
·                "buzzer", "syslog" and "currentprotection" commands require the "status" argument to display current status (bug #7420).
·                "cycle" command to a locked outlet will show different two different messages when trying to turn off and on that outlet (bug #7414).
·                Usernames with '%' are accepted without side effects in "list" and "status" commands (bug #7633)
 

c) Change Log

 
·                IPDU ID can be up to 16 bytes long.
·                Current alarm will have histeresis; it will be turned off when current reaches 1 Ampere below the threshold.
·                Current alarm threshold cannot be lower than 1 Ampere.
·                Power-on intervals are shown/set in 0.1 seconds precision (bug #7591).
 

d) Known Bugs

 

·                User-related commands (“adduser”/”deluser”/”passwd”/”assign”/”unassign”/”list”) may have problems when the user databases in the IPDUs are not synchronized (bug #7328).
·                Outlet number is still limited to 128, though other ways to define outlets (all, <outlet name>, <ipdu id>.<outlet number>) don't have this limitation (bug #7274).
·                Upgrade command for the last unit in the daisy-chain shows duplicate "Boot Menu" welcome message when user doesn't upload the firmware (bug #7809).
·                Copyright and product name in the banner were kept to assure compatibility with the former versions.
·                PM firmware upgrade sometimes fails with DSView® 3 software when chain has more than 4 IPDUs (bug #7935).

V_1.8.0 Jan/09/05 :  (official release; upgrade from V_1.7.1)

a) New features

·                Allow command "interval" with 0 as minimum value
·                New command "display" to provide LED with normal presentation or 180 degrees rotated
·                Command "id" now supported in chain

b) Bug fixes

·                Command "interval" was not accepting values between 48 and 57
·                Command "list" presenting garbage if the outlet list for a user was big
·                Commands addressing outlet 85 were causing the chain to be lost due to memory invasion
 
c) Change Log 
 
·                Command "ver" presents in addition the model number (e.g PM10DC = 24)
·                Limitation in the FW: no command can use outlet name in a range when the outlets in the range are NOT in the same box. Outlet numbers in a range can be used in any mode.

V_1.7.1 Oct/04/05 :  (official release; upgrade from V_1.7.0)

a) New features

·                Support again outlet name with characters between 21H to 7EH (but the first char in the name can't be numeric)
·                Characters ',' ,  '%' and '-' are reserved for internal use

b) Bug fixes

·                None
 
 
c) Change Log 

V_1.7.0 Sep/15/05 :  (official release; upgrade from V_1.6.0)

a) New features

·                Support to IPDU name (8 characters long)

b) Bug fixes

·                Status command with formatting problem in the Users field (missing a TAB)
·                Unassign command shows now the outlets out of the first IPDU being unassigned
·                Executing alarm command to set a given threshold followed by restore command would not recover the threshold saved in flash.

c) Change Log

·                Outlet names now allows only alphabetic characters

V_1.6.0  Jul/28/05 :  (official release; upgrade from V_1.5.0)

a) New features

·                Support to PM10i 32A, PM20i 32A, PM8iR 16A and PM10DC 10A.
·                Support to outlet names with 16 characters long

b) Bug fixes

·                Interval time was not accurate (bigger than it should be) affecting on, off and cycle commands
·                currentprotection command ignores parameters different from on/off
·                factory_defaults will turn ON all outlets w/o turning them OFF first

c) Change Log

·                PM10DC does not support the commands: alarm, current, currentprotection and buzzer.
·                cycle command has changed to OFF all outlets of one IPDU then ON all outlets of this same IPDU and then passes the command along to the next IPDU.
·                special cycle command for PM10DC model (cycle = off/on/off or on/off/on depending on the state of the outlet).
·                If PM10DC in chain with other PM models it should be placed last in the chain.
·                status all had a change in the layout (users placed in the last column)
·                WARNING: configuration from boxes running V_1.0.0 or V_1.1.0 will be lost when upgrading to this FW version. Boxes running V_1.2.0 up to V_1.5.0 will have their configuration preserved when upgrading to this FW version.

 V_1.5.0  Oct/25/04 :  (official release; upgrade from V_1.4.0)

a) New features

·                Support to PM10i 30A.
·                Display blinks when over current happens

b) Bug fixes

·                None

c) Change Log

·                None
 

 V_1.4.0  Oct/04/04 :  (official release; upgrade from V_1.3.0)

a) New features

·                Support to PM20i.
 

b) Bug fixes

 

·                Can't remove an outlet name by using command 'name' for a given outlet #(s)
·                List command doesn't show some of the outlets on the console
·                Separating commas are not deleted when users are deleted
·                "not V_1.2.0/1 or V_1.1.0 compatible" when executing 'restore' from pmCommand with a certain type of name being set for the outlets.
·                typo in 'deluser' help info
·                Delete a user gives four output of 'Username Deleted' 
·                Outlet name 8 chars long ending with a number, are not saved to flash after a save command.
·                As a regular user, type 'reboot' or 'assign' doesn't echo "Privileged Command" at the prompt.
 

c) Change Log

 

·                None


V_1.3.0  Mar/12/04 :  (official release; upgrade from V_1.2.2)

a) New features

·                Support to PM10i.
 

b) Bug fixes

 

·                Commands with outlets as arguments were not treating range properly.
·                Commands that require arguments when called without them were not returning proper error information or were getting lost

 

c) Change Log

 

·                None


V_1.2.2  Feb/23/04 :  (official release; upgrade from V_1.2.1)

a) New features

·                None.

 

b) Bug fixes

 

·                When registering one user's password greater than 8 characters the admin user would be deleted. Only powering off and back on would recover the unit.
·                Current reading for PM10 30A, outlets 5-10, was wrong
·                Daisy chain is not broken anymore when there's a session timeout
 

c) Change Log

 

·                Command upgrade uncommented
 

d) Known problems

 

·                When rebooting the unit (warm boot) the maxCurrent MAY present a wrong value. In that case, a "current reset" command would clear the wrong value. This problem does not appear in a cold boot.

V_1.2.1  Feb/17/04 :  (official release; upgrade from V_1.2.0)

a) New features

·                None.

 

b) Bug fixes

 

·                Upgrading from 1.1.0i to 1.2.0 could present problems in the outlet names, users and maxCurrent.
·                Buzzer could go off when upgrading to 1.2.0
·                Configuration was not preserved when upgrading from 1.1.0o to 1.2.0
·                Commands like status or off all could make the unit hang after an upgrade to 1.2.0

 

c) Change Log

·                None.


d) Known problems

 

·                When rebooting the unit (warm boot) the maxCurrent MAY present a wrong value. In that case, a "current reset" command would clear the wrong value. This problem does not appear in a cold boot.