Date: February 2, 2023
Bios: 1.12.2 2.6.0 3.3.0, Os: 14.11.23.0, RLib: 6.2.2 MiniXML: 1.3.5
Derived from: 34.27.13
Netcontrol: 2.0.3/2.1.1
Note: available for controls with PPC-G2, PPC-P2020, ARM-A9 cpu.
Note: suite with >= RDE 3.55.0
Note: suite with >= RC3E 33.9.1-17
Note: suite with >= RC4E 1.0.0
Note: suite with >= RPE 1.7.8
build 14
•CORRECTION: Profinet: Eliminated problem on waiting for initialization of PROFINET communication board. Error that could cause control to hang.
•CORRECTION: RP2 with Profinet: Eliminated problem that could occur at switch on between CPU and PROFINET board. Error that could cause the system to lock up.
•CORRECTION: TCP: Eliminated problem on Keep Alive with times less 2 minutes.
•CORRECTION: XPL: Fixed error that could cause failure on file read/write.
•CORRECTION: Alarms file: Fixed diagnostic handling issued on redefinition when neutral language file is already loaded.
•CORRECTION: FLOAD: Eliminated problems that could be had on FLOAD after aborting one previously.
•VARIATION: BCC3 SYS_INFO command: Added OSE (boot loader) version information in the BCC3 message of bccSysInfo(507).
•VARIATION: WHO directive: Added OSE version information on normal and verbose request.
•IMPLEMENTATION: OSE_VERS parameter: Added integer parameter with OSE(Boot loader) version number:
•OSE_VERS PI[154] OSE version (in hex VVRRBBB) read-only integer parameter without bit access.
•IMPLEMENTATION: BIOS_VERS parameter: Added integer parameter with BIOS version number:
•BIOS_VERS PI[153] BIOS version (in hex VVRRBBB) read-only integer parameter without bit access.
build 13
•CORRECTION: CANbus diagnostics: Remove diagnostic information if stations not present (if it is not marked that the node must be present).
build 12
•CORRECTION: OBB: ELF offset error: Fixed report on wrong offset when loading some OBBs.
•CORRECTION: OBB: error on ELF read: Added more information about CRC error when loading OBBs.
•IMPLEMENTATION: Axioline: AXL F SGI2 1H, AXL SE UTH4 EF: Managed Axioline modules AXL F SGI2 1H and AXL SE UTH4 EF.
•IMPLEMENTATION: Nidec M753: Zero cycle to mechanical end of strokes: Managed zero cycle to mechanical end of strokes on Nidec M753 drives.
build 11
•CORRECTION: Retentive memory: memory loss at startup: Fixed an issue regarding memory loss that could have occurred if the control started without RTE.CFG or with a different size of retentive zones.
•CORRECTION: Monitor/Oscilloscope: stop on reload and task restart: Fixed an issue where monitors and oscilloscopes could be mistakenly stopped during a task restart. This issue reduced the number of monitors/oscilloscopes that could be used later.
•VARIATION: Report: removed unnecessary messaging: Removed some unhelpful messages in the report.
build 10
•CORRECTION: DeviceNet Master: body format: Managed all body formats of requests. Previously only 8/8 format was supported.
•VARIATION: LADDER: start/stop: Now it is possible to start/stop ladder programs from the debugger interface provided by RDE.
build 9
•CORRECTION: Monitor in write: bit write operation: Corrected bit write using the BCC monitor in write. Previously erroneous bit write by setting it to 0.
•CORRECTION: FAT32-FDISK initialization: Corrected FAT32 initialization execution using BCC FDISK command. Incorrect root initialization could cause visualization of random filenames and/or directories.
•CORRECTION: AF directive: Corrected visualization of the routine index in the list for the AF directive.
•IMPLEMENTATION: NIDEC Touch Probe Driver: Added specific handling for NIDEC drives.
•IMPLEMENTATION: FB_MASTER_CFG FB_SLAVE_CFG: Added two PI-type parameters for diagnostic purposes of FieldBus communication configuration status.
•IMPLEMENTATION: PROFINET/PROFIBUS diagnostics: Updated struct information returned in diagnostic registers specified using DIAGNO_R in PFB.CFG configuration file.
build 8
•CORRECTION: RPE Alarms: Fixed functioning problem in RPE alarm loading handling when defining the alarm file for language neutral.
•CORRECTION: ARM Watchpoints: Corrected handling on watchpoint of a variable accessed to a critical section (in disable interrupt) - Previously interrupts were reenabling for some instructions, then disabling again.
•VARIATION: Global variables - create, link and unlink: Improved multithreaded handling of these functions.
•VARIATION: Fdel command: Prevented RDE from timeout on delete operations of all files in a directory (e.g., rebuild of a directory).
•VARIATION: Ethernet IP: Changed descriptive service name to code 0x0100 to work with PLC-FANUC, which expected the first letter to be in lower case.
•VARIATION: PROFINET Alarm 989: Added time filter for generatingalarm 989 (if code other than 8).
•VARIATION: Canopen: Added retentive handling of initial command execution in case of failure due to 'Frame error' errors.
•IMPLEMENTATION: Alarm 1 - user log loss: Added diagnostic in report to better understand the reasons for alarm generation.
•IMPLEMENTATION: SYS_FLAG EthernetIp: Added flag to disable EthernetIp message data dump:
•SYS_FLAG bit .31 (0x80000000) --> disables EthernetIp message data dump (enabled by SYS_FLAG.25 and/or SYS_FLAG.26) leaving only received/sent message reports.
•IMPLEMENTATION: Naming axes for alarms: Added handling to name axes and use them as parameters in alarm descriptions.
BUILD 7
•CORRECTION: Retentive memory: Removed additional criticality on ARM-A9-based controls. This criticality could cause alarms (e.g., alarm 2).
•CORRECTION: EoE: Corrected issue where in some files (e.g., Kollmorgen) EoE communication would hang during initialization.
•VARIATION: DeviceNet master status_reg: Added node status information. In NODE_STATUS_REG added code:
•0x21 device configured and waiting for DeviceNet communication (can line not present).
•IMPLEMENTATION: TCP/BCC client: Added command management for logical registration of TCP/BCC clients. The list is available to the user application on the control via the R3 instruction bcc_get_tcp_clients_info or the OB function getTcpClientsInfo.
•IMPLEMENTATION: DeviceNet master CFG_FLAG: Added new keyword CFG_FLAG in the DNMSTn.CFG configuration file that allows certain errors or configuration commands to be disabled.
build 6
•CORRECTION: Retentive memory: Eliminated possible interference between parameter writes, persistent global variables and alarm history. Such interference could cause alarms (e.g., alarm 2) or failure to store data in the alarm history.
•CORRECTION: Break Point: In case of break point with condition, task and address data are now updated only if the condition is true.
•CORRECTION: Access to U64 variables via BCC: With ARM-A9-based controls, access to I64 or U64 type variables via BCC caused the control to hang.
•VARIATION: TFTP diagnostics: Added diagnostic in 'Too many open clients' report. Previously diagnosed as 'Disk Full' alarm.
•IMPLEMENTATION: TFTP close at end of file: Added the possibility to enable immediate socket closure after receiving the file completely instead of letting it close naturally by timeout (about 2 min). Enabling this feature is done in one of two ways:
•In the RSW.CFGX file, the tag <Immediate_close>true</Immediate_close> must be added in the TFTP service section.
•In the ASCII directive TFTP_SRV the parameter -IC must be added.
•IMPLEMENTATION: OBB - crc: Added handling for checking the crc of the OBB file during loading. The OBB must be compiled with RC3E >= 33.9.1-17. If the verification fails, the OBB is obviously not loaded and diagnostics are issued. CRC testing can be disabled with the appropriate flag in SYS_CFG_2.
•IMPLEMENTATION: OBB - SYS_CFG_2: Added a flag in SYS_CFG_2 to disable any CRC checking of OBB files during loading. The bit is retentive.
•SYS_CFG_2 bit .16 (0x00010000) --> disable any CRC checking during loading of OBB files (files compiled with RC3E >= 33.9.1-17)
build 5
•CORRECTION: CAN device reconnection: Reconnection now works even when from user application was trying to read/write objects on the device being reconnected.
•CORRECTION: SAFETY: Corrected parameters on diagnostic messages in reports.
•CORRECTION: DEVICENET SLAVE: Corrected handling on some configuration commands.
•CORRECTION: Alarm History: Correctly diagnosed alarm history size change. Now alarm 3 is still generated.
•CORRECTION: Axis inclusion/exclusion from powerset: Corrected handling on axis inclusion/exclusion and axis/powerset association to properly handle axis diagnostics in powerset.
•CORRECTION: Homing on RO-AXL_SE_STP2: Corrected handling execution of homing using MVA_ZC for axes defined on RO-AXL_SE_STP2 modules axis diagnostics in powerset.
•VARIATION: AF Directive: Also added the reference index of the 'attached function' at the bottom of the message. This index is used in diagnostic alarms type alarm 9901.
•VARIATION: NETCONTROL channel_12_13: Changed minimum number of fw netcontrol to handle the use or non-use of channels 12 and 13. Brought for hw SKW71 from version 2.0.2 to 2.0.3. Due to a problem present on distributed fw 2.0.2, using RTE 34.27.3 or 34.27.4 results in netcontrol no longer being usable. In this case you must do either a roll back to version 34.27.2 or upgrade to 34.27.5 in order to upgrade fw netcontrol to 2.0.3.
•VARIATION: ETHERCAT on ARM-A9: Increased the number of definable variables connected to ethercat (from 3000 to 6000). This variation is valid only for arm-a9 cpu.
•VARIATION: DEVICENET SLAVE: Increased timeout time before diagnosing non-communicating CAN board.
•VARIATION: PROFIBUS SLAVE: Managed profibus communication alarm if DP-on communication signal does not occur within 120 seconds of configuration.
•VARIATION: AXL_SE_STP2: Changed startup management to avoid unwanted diagnostics.
•VARIATION: Frequency Rule: When an illegal system frequency is set, the default frequency is used in addition to the alarm.
•IMPLEMENTATION: DEVICENET SLAVE: Managed data exchange with messages shorter than 9 bytes.
•IMPLEMENTATION: DEVICENET MASTER: Added management of DeviceNet communication as master on controls with integrated CAN channel(s).
•IMPLEMENTATION: AXL_SE_STP2: Checked at switch on if the component has firmware loaded or not. If not, configuration is, of course, not performed.
build 4
•CORRECTION: CO_SDO: Fixed error on CO_SDO directive that caused communication via ASCII to block when giving command to a node that must be present but the CAN line did not start.
•CORRECTION: FLOAD FoE IMD EC2x: Fixed handling on FLOAD to a /proc/bus/ecat/ethn/slave_xxx/foe/fw file. Now terminates correctly.
•CORRECTION: F_COPY FoE IMD EC2x: Corrected handling of F_COPY with recipient a /proc/bus/ecat/ethn/slave_xxx/foe/fw file. Now the operation ends successfully.
•VARIATION: Profinet - Bios 3.3.x: Avoided memory fouling in powerset configuration analysis handling. With the latest versions of bios on arm-a9 it was causing profinet-slave not functioning.
•VARIATION: NETCONTROL startup timeout: Changed RNC ready wait timeout.
•IMPLEMENTATION: Alarm 9901: Changed behavior of alarm 9901 if SYS_FLAG.4 flag is present. 9901 Illegal Funct. Task: tt Step: ssss. If this flag is present the Task number tt will contain a value > 1000 indicating the exact point at which the error was generated. Contact Robox for more information.
•IMPLEMENTATION: Photos on Interrupt SYS_CFG_2: Added the possibility to customize the photo interpolation handling of positions detected by fieldbus. By default these positions are calculated using the values of cv and ca and the elapsed time between the interrupt in question and the last rule execution. Using SYS_CFG_2.13 it is possible to disable the use of acceleration in the interpolation calculation. Using SYS_CFG_2.14 it is possible to enable the use of ideal values (iv and ia) instead of real values. The speed used is, temporally, that used in the tracking alarm threshold calculation (SA_IPP_IDX-1).
•SYS_CFG_2 bit .13 (0x00002000) --> Disables the use of acceleration in the interpolation of snapshots made on interrupt
•SYS_CFG_2 bit .14 (0x00004000) --> Enables the use of ideal units instead of real units in the interpolation of photos made on interrupt
•IMPLEMENTATION: AXL_SE_DI16_1_NPN AXL_SE_DO16_1_NPN: Added management to use modules: AXL_SE_DI16_1_NPN and AXL_SE_DO16_1_NPN
•IMPLEMENTATION: NETCONTROL channel 12-13 check: Added management check for minimum version to give the command according to the board type: if SKW71 minimum version 2.0.2, if HLK7628N minimum version 2.1.1
•IMPLEMENTATION: AH_FILTER_991 SYS_CFG_2: In BCC3 commands for reading alarm history, added possibility to put a time filter on alarms preceding the alarm "991 SYSTEM SWITCHED OFF in <xxx>". NOTE: The filter is active ONLY on the alarm history query BCC commands. This performance is not active either by using the AH_GET_DATA instruction or by storing the alarm history in the SYSTEM_LOG file. The filter value is imposed in the system retentive variable AH_FILTER_991 in seconds. This performance is enabled by using the retentive bit SYS_CFG_2.(15) = 1
•AH_FILTER_991 - filter time to prevent visualization of alarms preceding alarm 991. PR[35] read/write, retentive, nobit access.
•SYS_CFG_2 bit .15 (0x00008000) --> Enables use of filter on visualization of alarms preceding alarm 991
•IMPLEMENTATION: NETCONTROL AUX_SER_2_NC: Added the possibility to select the second serial as linux console on netcontrol modules HLK7628N. AUS_SER_2_NC 2. If the board does not support it or the bios does not support it the serial channel tunnel to the netcontrol board is not activated.
build 3
•CORRECTION: ALARM 9280 -> 9380: Changed alarm number 9280 to 9380
•CORRECTION: RPP: Handle enum on debug
•CORRECTION: ETHERNET IP: Corrections on TCP command handling
•CORRECTION: AXIOLINE: Correction on initialization
•CORRECTION: ENABLE_POWER CHOPPER_OK: Enabled management of ENABLE_POWER and CHOPPER_OK associated with digital output/input on local axioline modules
•CORRECTION: AXIS MANAGEMENT on reduced freq. fb lines: Managed diagnostic information only in the rule sampling where the axis is actually managed
•CORRECTION: FAT: Avoided crashing if on RP-0 RP-2 and Dongle the micro SD is formatted FAT16
•CORRECTION: TCP KEEP-ALIVE: Focused better on where to manage KeepAlive
•CORRECTION: NETCONTROL: Avoided handling DHCP services if LAN is disabled
•CORRECTION: ECAT EoE SDO: Avoided having errors on asynchronous messages (SDO) if there is EoE traffic on the same node
•CORRECTION: CAN: Corrected error introduced in osf 14.11.10.7 rte 34.27.2. did not transmit configuration SDO from COC file if node was present at switch on
•VARIATION: Info in report: Added author info on Beta versions.
•VARIATION: Monitor/oscilloscope management frequency: Increased monitor/oscilloscope management frequency from 200 to 800 even for A9 processor-based controls
•VARIATION: CAN diagnostic: Modified the generation of 'transmission errors'
•VARIATION: ECAT IMD20 RID20E: Accepted product code of RID20E also for devices configured as IMD20.
•IMPLEMENTATION: netcontrol sw update also from display: To perform NETCONTROL sw update, one must put the update file "robox_upgrade.tar.gz" in the /WEB/ directory of the uSD and use one of the following methods:
•The UPGRADE NETCONTROL directive.
•In the display menu 'NET.Config.''- under'Status' by selecting the item 'Upgrading RNC' and pressing 'change'
•By setting bit 5 (0x20) of the system variable NC_CMD to one.
•IMPLEMENTATION: NETCONTROL: Added management to use wifi channels 12 and 13 as well.
build 2
Note: Do not use RTE version 34.27.2 if using CANopen devices, use version 24.37.3.
•CORRECTION: SDO management: Added common device management on SDO (e.g., Multichannel Drive) to avoid possible interference problems between execution of asynchronous requests on different subdevices. Verified with Coe - to be tested with SoE
•CORRECTION: AXIO: Minor correction on byte reads of data.
•CORRECTION: TRD_AL_INFO: Deletion of 'Fault from EMCY' information present when emcy arrives with code 0
•CORRECTION: WAN directive: Fix minor error using Netcontrol fw < 1.3.0
•CORRECTION: Instruction FDEL: Given error 'EACCES (13) Permission denied' only when trying to delete a file on "/f@/" and not also when "/f@/" was a subdirectory (e.g. "/test/f@/job1.txt")
•CORRECTION: Netcontrol reboot: After a netcontrol-only reboot, subsequent commands no longer work
•CORRECTION: EthernetIP: Minor correction on IP address analysis read from configuration file
•CORRECTION: SYS_DUMP.29 RETENTIVE POSITION RESTORE: After loading the file into retentive memory, it no longer reset the control. Malfunction introduced in RTE 34.26.0.
•CORRECTION: PGV_RESET directive: After reserving global variable retentive memory delete no longer performed control reset. Malfunction introduced in RTE 34.26.0.
•CORRECTION: LADDER task reload: Functionality no longer functional since RTE 34.24.0. Returned operational again
•CORRECTION: EthIP: Respected time for sending message. Added message in report with requested time between 2 messages.
•CORRECTION: NETCONTROL OPCUA: Corrected starting problems on OPCUA Configuration.
•VARIATION: FOLLOW2: Using the function with variable master cycle, it became mandatory to set the master cycle value equal to the minimum cycle value. This is to avoid having fallacious movement predictions
•VARIATION: FOLLOW2: Miscellaneous optimization
•VARIATION: GET_HW_INFO: Added to the GET_HW_INFO instruction the possibility of specifying if you want the information of desired or current devices
•VARIATION: Profibus: Possibility to reset alarm 989 if the error causing it goes away
•VARIATION: Description of types of 'References': Changed description of some types of references from "CAN 402" to "C402"
•VARIATION: Axioline: Delayed the axio start until the rules start
•VARIATION: BCC monitors: Increased the number of manageable BCC monitors from 128 to 256 for ARM-based controls only( RP-0 and RP-2 and dongle)
•VARIATION: XML management: Unified support routines to read xml file (Global variable - OOW) minor correction on IP address analysis in configuration
•VARIATION: AXIO startup: Increased timeout on CR0 initialization command execution. Cleaned reception from any pending responses
•VARIATION: MVA_OPEN_LOOP SYS_CFG_2: Changed behavior of this function. Now as the axis is enabled (ENABLED_AX) the loop is no longer held open but IV = 0 is imposed. The previous behavior can be achieved by using bit 12 of SYS_CFG_2
•SYS_CFG_2 bit .12 (0x00001000) -> MVA_OPEN_LOOP management compatible with antecedent version i.e., the open loop is kept open at all times
•VARIATION: NOTE : It was chosen not to be normally backward compatible as it was felt that the most useful behavior using this function is the one implemented now
•VARIATION: POWER_SET DRV_FOLLOWS_COM_AX STATUS.10: Bit .10 (0x400) of the PowerSet status changes meaning:
•Before: all enabled axes have the corresponding feedback
•Now: all enabled axes have relative feedback and all enabled axes have the 'drive follows command value' bit. Note For axes that have not imposed the flag to use 'Drive Follows Command Value' it is assumed that the value is always True
•VARIATION: POWER_SET DRV_FOLLOWS_COM_AX PS_STATUS: In PS_STATUS directive added visualization mask information of (logical) axes that have the bit of 'Drive Follows Command Value'. Note the bit is forced to one for those axes that have not imposed the flag to use 'Drive Follows Command Value'
•VARIATION: Alarm 9203: Differentiated alarm output "9203 CAN_CH(ch) No Communic.(\e code )"
•code 0 indicates BUS_OFF errors of the line.
•code 4 indicates transmission errors. /n These warnings do not affect the functioning of can channel management, they only indicate the presence of anomalies on the can network. Any problems resulting from these anomalies, which could lead to problems on the can line are handled at the received message control level
•VARIATION: CAN diagnostics: Changed meaning to two registers in can diagnostics selected with CAN_DIAG_N = 1 INFO_Alarm ( 1 ). Now the R(idx+6) register contains error counters for BUS_OFF conditions and error in Transmission:
•R(idx+6) W0 Error counter of not possible transmissions.
•W1 Counter of BUS_OFF errors.
•VARIATION: CAN: In case of absent station at switch on and configured node reconnection, SDO commands from COCx file are not sent, which will be sent instead when node reoccurs
•VARIATION: CHECK_MV_FOLLOW2 CHECK_MVA_FOLLOW2 CHECK_MVA_FOLLOW2_M
•New functions to check if follow2 can be executed with the specified data. Functions return error code and if ok also maximum sync duration time
•VARIATION: RQ_RETMEM_SAVE_ONCE RQ_RETMEM_RESTORE_ONCE: Added file management to execute only once memory save/return in /DUMP/RETMEM_DUMP.STB./n The request file, which must be loaded in the /DUMP/ folder, is deleted after executing the requested operation, so that at switch on the next time the control starts regularly. So the procedure to save the retentive memory can be as follows:
•load in /DUMP/ a non-empty file named RQ_RETMEM_SAVE_ONCE
•turn off the controller
•turn it back on
•wait for the end of the save operation
•turn off the controller
•turn it back on
•start working again.
•NOTE for internal use: RETMEM.EXE program is available to do analysis of the file contents.
•IMPLEMENTATION: Fieldbus RPP: Added functions to get information about fieldbus nodes for use by RPP
•IMPLEMENTATION: LAST_OB_AF LAST_OB_AF_PAR: Added API variables for storing the address of the last executed routine as AF(attached function)
•IMPLEMENTATION: RID20E: Added management for Drive Robox RID20E. Drive code in RTE.CFG configuration is 67. Updated emergency management (reports and alarms) dedicated to this type of drive.
•IMPLEMENTATION: Drive RO-AXL_SE_STP2 on local AXIO bus: Added management for Drive Robox RO-AXL_SE_STP2 managed in position connected to local axio. These axes occupy the RID corresponding to the axis number they are associated with. They are managed in the same way as the other fieldbus type axes
•IMPLEMENTATION: RO-AXL_SE_STP2 drives on ECAT: Added management for RO-AXL_SE_STP2 managed Robox drives connected to AXL_F_BK_EC
•IMPLEMENTATION: Upgrade FW RO-AXL_SE_STP2 AXIO_STP2_FW_UPDATEL: Added directive AXIO_STP2_FW_UPDATE to be able to upgrade firmware of RO-AXL_SE_STP2 modules:
•AXIO_STP2_FW_UPDATE 0 slot filename
•slot axio slot numebr from 1 upt 63
•filename full filename in the controller flash card of the firmware to update. The file must be prevoiusly and obviously loaded into flash before
•IMPLEMENTATION: Alarm files in UTF8-BOM format: Avoided issuing diagnostic on first line of alarm files the file encoding was UTF8-BOM instead of UTF8
•IMPLEMENTATION: EC2B alarm 622: Added for Robox EC2B drive the alarm 622 generated with emcy FF80 01 0000003Dax
•IMPLEMENTATION: RPE_VERS pi variable: Added predefined variable of integer type containing the version of the RPE sw. PI[145] RPE_VERS version of RPE sw. Read-only variable with no bit access.
•The version format is:
•B3(RPE_VERS) -> vers
•B2(RPE_VERS) -> release
•W0(RPE_VERS) -> build
•IMPLEMENTATION: XPL_VERS pi variable: Added predefined variable of integer type containing the version of the XPL sw. PI[146] XPL_VERS version of XPL sw . Read-only variable with no bit access.
•The version format is:
•B3(XPL_VERS) -> vers
•B2(XPL_VERS) -> release
•W0(XPL_VERS) -> build
•IMPLEMENTATION: SYS_CFG_2.11 TCP Client: Added flag in SYS_CFG_2 using bit 11. SYS_CFG_2 bit .11 (0x00000800) -> Enable dump in report of TCP Client diagnostic messages. Assumed only at switch on of control.
•IMPLEMENTATION: BCC3 OOW (Only One Write) modality.
•IMPLEMENTATION: SYS_CFG_2 OOW ID using port: Added bit .10 in SYS_CFG_2 to enable use of TCP port in TCP client ID
•SYS_CFG_2 bit .10 (0x00000400) -> Enables the use of TCP port in the TCP client ID in the OOW session
•NOTE port usage in the ID is contingent on this flag and the one set on open request
•IMPLEMENTATION: SYS_FLAG_2 OOW session info: Added bit .2 in SYS_FLAG_2 to enable diagnostics in the report of when an OOW session is opened and closed. SYS_FLAG_2 bit .2 (0x000004) -> Enable dump in report of OOW session open/close diagnostic messages
•IMPLEMENTATION: variables OOW_STATUS OOW_OWNER_IP OOW_OWNER_PORT: The following system variables have been added for OOW:
•PI[149] OOW_STATUS OOW modality status. Readonly variable, bit accessible.
•bit 0 0x1 OOW session management enabled
•bit 1 0x2 OOW session opened.
•bit 2 0x4 Source TCP port is used togheter with source IP address as owner (supported only for TCP/IP)
•PI[147] OOW_OWNER_IP OOW owner ip address. Readonly variable, no bit accessible.
•Note1 : for instance the ip adress 10.0.14.147 will be shown as : 167775891 0x0a000e93
•Note2 : if the session is not opened 0 will be returned.
•PI[148] OOW_OWNER_PORT OOW owner tcp port. Readonly variable, no bit accessible.
•Note : if the session is not opened 0 will be returned
•IMPLEMENTATION: POWER_SET DRV_FOLLOWS_COM_AX STATUS.10
•Added performance to enable the use of bit .12 of the status_word (FB_STSW). In CoE CSP CSV and CST operating modes it means 'Drive follows the command value'.
•Depending on the implementations of the drives this bit is enabled in conjunction with 'operation enabled' after managing the brakes, while in others it is first returned 'operation enabled' and after removing the brakes this bit is enabled
•Enabling the use of this performance is done by the keyword -UDFC in the definition of CHANNEL_ENABLE_FEEDBACK in the RTE.CFG file
•The system variable DRV_FOLLOWS_COM_AX contains the mask of axes that are in 'operation enabled' and have the bit 'drive follows command value'
•If this functionality is not enabled for the axis, the bit for that axis is forced to true
•DRV_FOLLOWS_COM_AX pi[150] masks axes that are in 'operation enabled' and have the 'drive follows command value'bit not writable - non-retentive - bit access not enabled
•The presence of this performance affects the status of bit .10 (0x400) which now means: all enabled axes have the relevant feedback and all enabled axes have the 'drive follows command value' bit
•IMPLEMENTATION: POWER_SET DRV_FOLLOWS_COM_AX STATUS.13 STATUS.14: Added two new bits in the status bit .13 (0x2000) all enabled axes have the relative feedback bit .14 (0x4000) all enabled axes have the relative bit of 'drive follows command value'
•IMPLEMENTATION: POWER_SET CHANNEL_DRV_FOLLOWS_COMMAND CHANNEL_DRV_FOLLOWS_COMMAND_P: Added to the power_set lovs the following variables containing the axes mask of the status of the 'Drive follows command value' bit (real if enabled or 1 if not enabled)
•CHANNEL_DRV_FOLLOWS_COMMAND
•CHANNEL_DRV_FOLLOWS_COMMAND_P
•IMPLEMENTATION: NETCONTROL: Added management HLK7628N board. Added info on board type and RNC sw version to the report.
build 1
•FIX: SOCKET TCP: Fixed management of 'close' operation of a socket. Under certain conditions it could cause the communication management task to hang
•CORRECTION: RAMDISK: Fixed error that occurred when two ramdisks were defined and the name of the second was a subset of the name of the first. The configuration was being aborted
•CORRECTION: ECAT INIT: Fixed init command handling at the ethercat line. Now the init command is actually sent to the devices
•VARIATION: OPCUA: Stopped OPCUA Server from running on netcontrol before loading a new configuration file.
•VARIATION: SYS_LOG: Added mac information of devices with slave fieldbus and/or netcontrol to the device information field as well.
•VARIATION: OPCUA - NETCONTROL: Now the OPCUA server diagnostic report is also shown when Netcontrol is in CLI-SLAVE mode
•VARIATION: NETCONTROL - SSH: Enabled the use of SSH even when the Netcontrol board is in CLI-SLAVE mode
build 0
•CORRECTION: FAT32: Managed seconds in 'last write' and 'last access' times in files and directories
•VARIATION: NETCONTROL REBOOT OPCUA: Lengthened the timeout time to 150 sec in case of reboot in order to also handle the restart of a possible OPCSERVER
•IMPLEMENTATION: NETCONTROL Configuration File: Added check if the configuration specified in NETWORK.CFG is already present and active on netcontrol. If equal, the actual loading is not performed reducing NETCONTROL startup time
•IMPLEMENTATION: OPCUA CONFIGURATION: Added OPCUA server configuration management on netcontrol. Configuration defined in RDE (OPC UA Server). Note compiling the opcua server configuration modifies the NETWORK.CFG file and creates the two files: OPCUA_configurationName.BIN and OPCUA_configurationName.XML. The last two files must reside in the /WEB/OPCUA/ diretcory.
•IMPLEMENTATION: OPCUA Configuration Files: Added handling of loading OPCUA server configuration files only if they are different from those already on NETCONTROL board. If they are present we are limited to starting server with significant time savings
•IMPLEMENTATION: OPCUA - load and restart configuration file: When load and restart is selected in the load operation from RDE, after the flash file is loaded, a check is made if it is the same file present on netcontrol, if not, the new configuration is loaded and the OPCUA server is restarted. The time for this operation is approximately 40 seconds
•IMPLEMENTATION: OPCUA SERVER LOG: Added management to store diagnostic messages generated by OPCUA server in the system report. The dump of the messages can be conditioned by the SYS_CFG_2 flag.(9)
•IMPLEMENTATION: OPCUA SERVER LOG SYS_CFG_2.(9): Added flag in SYS_CFG_2 using bit 9: SYS_CFG_2 bit .9 (0x00000200) -> Disables the output of OPCUA SERVER diagnostic messages in the report. Flag cleared at switch on.
•IMPLEMENTATION: Alarm 9280: Added warning 9280. It is as an alternative to alarm 80 (generated by the same events). The selection of either alarm is made via FB_FLAG.
•IMPLEMENTATION: AXIO_EXCLUSIVE_RIGHTS directive: Added directive to enable exclusive rights of axioline modules
•IMPLEMENTATION: AXIO_RIGHTS_MANAGEMENT LICENSE: Added management in license file of keyword AXIO_RIGHTS_MANAGEMENT 0/1 to enable use of AXIO_EXCLUSIVE_RIGHTS directive. If keyword not present in the license file, the default value 0 (directive not enabled) is used.
•IMPLEMENTATION: STARTUP DIAGNOSTIC: Added a new method (in addition to the ADV button) to enable storage in the alarm history of the sequence of operations performed at switch on. Diagnostics is enabled if there is a non-empty file with the fullfilename: "/FA/ENABLE_STARTUP_DIAGNO"
