Date: November 11, 2009
Os: 13.18.558
RoboxLib: 3.04.0000
Derived from: RTE 33.19
Note: suite with >= RDE3.7.3
Note: suite with >= RC3E v33.3.4
Note: suite with >= RPE v1.3.0
build2
•CORRECTION: NVR 1-:-64
From version 33.18.06 NVR retentive registers included from 1 to 64 could be dirty
build1
•IMPLEMENTATION: RESET
Added alarm "995 Power OFF left out, SYSTEM has been reset" and diagnostic on report when a system reboot occurs and in the previous shutdown the logs had not been saved (omission of management performed on power failure) or after a hardware RESET.
•IMPLEMENTATION: EMCY_AL
Added directive (device command) to enable/disable the output of emergency messages from a specific station
•IMPLEMENTATION: POWERED_AX
Mask the axes whose power set is in power
•IMPLEMENTATION : QUICKSTOP in POWERSET:
Management of quick stop status in power set.
•IMPLEMENTATION : SWITCHING_OFF QUICK_STOP_SO
Added read-only parameters:SWITCHING_OFF and QUICK_STOP_SO
build0
•IMPLEMENTATION : DATE2TM
Directive (device command) to convert date and time to the time unit of the report
•IMPLEMENTATION : SYS_LOG
Added auto generation of SYSTEM_LOG.TXT file in case of system crash.
•IMPLEMENTATION : FLOAD BCC
Inserted flag handling in load command for loading in ram after flash loading(live changes)
•VARIANT : ROBOX ID STATION
Expanded management of the number of fieldbus nodes from 64 to 1024 (Robox station ID)
•VARIANT: ALARM 990
Improved output of diagnostics in case of rule blocking for an excessive time resulting in watch dog dropping
•VARIANT: ALARM 9104
In the case of rule frequency of fixed type (i.e., imposed by fieldbus) the alarm of rule too long is issued immediately as the rule duration exceeds the rule period
•VARIANT: SER_GAI
If a value of 0 is imposed on the SER_GAI parameter instead of setting the SER_CTHR threshold to the value of 1e99 (effectively disabling tracking alarm control), only the dynamic component is reset obtaining SER_CTHR = SER_THR
•FIX: SYSTEM EXCEPTIONS
Improved diagnostic handling (and avoided system blocking) in case of system exception while executing download sequence in BCC3 (responses to system commands, fdir, fsave, report, alarm history...)
