Release Information HMS PDF

RELEASE INFORMATION
Project name Project No
Anybus-S PIR / PIR FO 7254

Software Software version Release date
Application Version 3.20 2012-05-16
This release contains:

• This document
• Application code – “7254-ETH_3_20_04.hex”
• Application code – “7254-ETH_3_20_04.hms”
• Application code – “7254-ETH_3_20_04.fwp”
• Application code – “7254-ETH_3_20_04.bin”
• Application code – “7254-FO_3_20_04.hex”
• Application code – “7254-FO_3_20_04.hms”
• Application code – “7254-FO_3_20_04.fwp”
• Application code – “7254-FO_3_20_04.bin”
• Firmware loader – “FL_ABS_PIR_V_1_00_03.hex”
• Ram loader – “RL_ARM9_V_1_01.bin”
• GSD file – “GSDML-V2.25-HMS-ABSPIR-20120514.xml”
• Production parameter eraser – “ERASE_PROD_DATA_V1_00_01.hex”
Reason for release:
This is a maintenance release adding PROFIenergy support and correcting some issues.
Supported hardware:
Firmware can be downloaded to ABS-PIR hardware with PCBs marked2222-1.2.1 and 2222-1.4.1. Firmware
can be downloaded to ABS-PIR FO hardware with PCBs marked2232-1.0.1(both AFBR and QFBR Avago
transceivers are supported).
Compatibility:
No known compatibility issues.
How to upgrade from previous versions:

It is very important that the following steps are performed in correct order; otherwise the module may be
unusable and must be sent back to HMS for recover.
Firmware upgrade:
FTP
1. Initialise the module.
2. Download the firmware file *.hms via FTP to the root directory.
3. Power cycle the module and wait until the watchdog LED flashes 2 Hz green. This may take up to 1
minute. Do absolutely not turn off the power during this time.
4. Update complete!
Anybus Firmware Manager:
1. Start Firmware Manager. Select transport path and set the module in “Service Mode”, then hit
“Next”.
Created: 2012-05-15
HMS Industrial Networks AB
Last saved by: Johan Häggström
RELEASE INFORMATION


2. Import Package *.fwp and hit “Next”. Wait until the firmware has been downloaded. (Do absolutely
not turn off the power during this time).
3. Update complete!
Known limitations:
• Module stops responding to IP unicast requests–If module is initialized with non-default IP
settings (i.e. IP address other than 0.0.0.0), changes done with AnybusIPconfig will not take full
effect and can cause the module to stop responding to http/ftp/ping requests. Functionality can be
restored by reverting the changes done with AnybusIPconfig or resetting the module.Internal ID:
0006111.
Created: 2012-05-15
RELEASE INFORMATION

Updated in version 3.20:
- New functionality
• PROFIenergy - The PROFIenergy profile [PESPEC] is created by the PI in order to reduce the
amount of power used by machines when production is not really active. For example, during lunch
breaks and over week-ends, the machines are very often running at full power consumption even
though the production is standing still. The target of the PROFIenergy profile is to give the operators
of the factories (for example) the possibility to easily set all machines at the same time in the, for
each machine, the most optimal power consumption mode, given the length of the production stop.
- Improved functionality
• Flash memory access synchronization – When issuing a Factory Reset command from the
PROFINET network, functionality to synchronize the flash memory access to the information of the
host application has been implemented. This to avoid informing the application that a power-cycle is
requested before an on-going flash operation has been completed. Internal ID: 0006835.
- Bug fixes
• Used buffers are not released when a socket is closed – The RECV_FRAG or the
RECV_FRAG_FROM buffers are not released if they are used by a socket being closed. This makes
other sockets block forever on a RECV_FRAG or RECV_FRAG_FROM command. This issue has
now been corrected so that the buffers are released if they are used by a socket being closed. Internal
ID: 0006824.
• Network status is overwritten when a socket is closed – The network status is incorrectly
overwritten if a number of operations are being executed on a blocking socket. This issue has now
been corrected so that only operations on non-blocking sockets update their socket status. Internal
ID: 0006786.
- Other changes
• Firmware version update – Version number of the firmware has been updated to 3.20.
Created: 2012-05-15
RELEASE INFORMATION

- New functionality
-Bug fixes
• IOPS for interface/port sub-modules not set to BAD on mismatch – If a mismatch is found for
interface/slot sub-modules the IOPS of the corresponding sub-module is not set to BAD. Internal ID:
0006712.
• Wrong status in ModuleDiffBlock when connecting – When connecting, using a master
configuration where a module does not match the plugged module, the Anybus reported status
“Substitute” for both module and sub-module in the ModuleDiffBlock. This is now corrected so that
status for module/sub-module is reported as substitute/wrong respectively. (Module state “wrong”
should not be used; recommended replacement is “substitute” for the module and “wrong” for each
sub-module). Internal ID: 0006711.
- Other changes
Created: 2012-05-15
RELEASE INFORMATION

- New functionality
-Bug fixes
• Slots gets tagged as used when the mailbox PNIO_IND_CFG_MISMATCH diff is fired for
unused slots–If a slot was plugged in the PLC configuration, but not in the device configuration, and
the PNIO_IND_CFG_MISMATCHmailbox was enabled the slots were tagged as used even when
responding with "NO_MODULE" with the mailbox. This has been corrected so that slots will not be
tagged as used when the host application responds with “NO_MODULE”.Internal ID: 0006635.
- Other changes
Created: 2012-05-15
RELEASE INFORMATION


- New functionality
• SSI call DisplaySerial always return factory-programmed serial number – Firmware always
returns the serial number which has been programmed at production test. This has been changed so
that if a new serial number is set with the I&M 0 mailbox, this serial number will be returned,
otherwise the factory programmed serial number will be returned. Internal ID: 0006176.
- Bug fixes
• Support of Avago AFBR transmitter for the FO devices– The firmware has been updated to add
support also for AFBR transceiver (not only QFBR which is the transceiver new modules are
shipped with). Internal ID: 0006327.
• DCP-set takes too long time – Sometimes when setting the station name, or the IP-suite, the
response from the module took more than 1s, which is not allowed. Internal ID: 0006264.
• Error message at first start-up with Fast Start-Up – When booting up the module in FSU-mode
with the IO Controller waiting for the hello message from the node, the connect request from the IO
Controller were received before able to properly handle it, resulting in an “Out of AR resources”
error. This has been changed so that the Hello-messages are not transferred until the module is ready
to handle the connection request. Internal ID: 0006263.
• DPRAM test of HW_CHECK incorrectly implemented – When executing the HW_CHECK
mailbox the DPRAM test will also test the handshaking bytes of the DPRAM. These can
result in that the host application will get an incorrect response mailbox. This has been
corrected so that the DPRAM test will not test the two handshaking registers. Internal ID:
0006536.
• Cannot plug new modules after initialization completed – After successful initialization of the
module in advanced mode, it is not possible to plug a new module in an unused slot. Correction has
been made to allow plugging of unused slots in run-time in advanced mode. Internal ID: 0006578.
- Other changes
• Firmware version number – Firmware version is always stored at a fixed location of the flash
memory. By doing this, it is possible to speed-up the production test procedure. Internal ID:
0006362.
Created: 2012-05-15
RELEASE INFORMATION

- Bug fixes
• HW_Check failure–The module got a fatal event during HW_Check due to a failed CRC check on
the firmware. The CRC check was done on the wrong area in the FLASH due to a faulty define
taken from another project. Internal ID: 0006178.
Created: 2012-05-15
RELEASE INFORMATION

• PNIO stack updated – The Anybus PIR / PIR FO now incorporates version 3.2.0 of the Profinet IO
stack.
• Presentation of OMA improved – The presentation of Optical Power Margin in the DPRAM is
now in accordance with the manual.
- Bug fixes
• Plugging a module with module identification number 0 causes a Fatal event - This value does
not seem to be accepted by the PNIO stack so a workaround will be needed. The issue has been
addressed by returning an error mailbox instead of going into fatal. Internal ID: 0004202.
• Change scaling for Rx Power on web-page - On the web-page the Rx Power is displayed in uW
while on the PROFINET side this is read out in dB. This has been fixed by now presenting the
power margin the same way as it is presented in Step 7. Internal ID: 0005340.
• Module crashes when webpage gets accessed – Under certain circumstances, such as large web
pages with incorrect SSI tags, the web server could stop responding. This has been remedied.
Internal ID: 0005430.
Created: 2012-05-15
RELEASE INFORMATION

- Bug fixes
• Incorrect ImFilterData in case of adaptation – If the Anybus module adapts it configuration to the
configuration which is used by the IO Controller the I&M filter data will be updated with the
information of the adapted modules. This is not correct behaviour since the Anybus module only
support discrete I&M for slot 0. This has been addressed so that adapting a configuration will not
add the adapted modules to the I&M filter data. Internal ID: 0005689.
Created: 2012-05-15
RELEASE INFORMATION

- Bug fixes
• MIB information mailboxes write data to FS even if data is not changed– If the power supply is
interrupted when using either of the mentioned mailboxes there is a risk that the file system gets
corrupt and the station name and IP-address are lost. Changed so that PNIO_SET_IM0_INFO
doesn't store any information in the flash. Updated mailboxes
PNIO_SET_INTERFACE_DESCRIPTION, PNIO_SET_SYSTEM_CONTACT_MIB2,
PNIO_SET_SYSTEM_DESCRIPTION_MIB2, PNIO_SET_SYSTEM_DESCRIPTION_MIB2 and
PNIO_SET_SYSTEM_LOCATION_MIB2 to only store the information if it is truly new.Internal
ID: 0005538.
Created: 2012-05-15
RELEASE INFORMATION

- Bug fixes
• No discrete I&M data for slot > 0 – For PROFINET devices the slots / sub-slots which contain
discrete I&M-data are listed in the ImFilterData. The Anybus module is not able to hold discrete
I&M data for all plugged sub-modules, therefore the firmware has been changed to only list the DAP
(slot 0, sub-slot 1) in the filter data – previously all plugged modules were, incorrectly, listed.
• Potential problem with function pnio_RecOutDataObjElemHandler() – The firmware could
potentially return the incorrect error code if the output data of a DAP-sub-module were accessed.
This has been corrected so that an “Invalid Index” error is always returned. Internal ID: 0005482.
• At FastStartup the module sends too few DCP.Hello messages – When FSU has been configured
the module shall send one hello message plus the number of configured repeats. The Anybus module
were transmitting one Hello message too few. This has been corrected so that the correct number of
Hello messages are transmitted when linking up.Internal ID: 0005487.
Created: 2012-05-15
RELEASE INFORMATION

- New functionality
• Fiber optic diagnostics – New transceivers capable of measuring temperature, voltage and signal
strength and with matching threshold alarms. Diagnostic values along with some of the alarms can
be read from the FB specific area or through SSI’s. In addition, there is also an alarm function
available towards the network side.
Created: 2012-05-15
RELEASE INFORMATION

- New functionality
• Add mailbox to be able to read the values possible to set with mailbox
PNIO_SET_IM0_INFO– To be able to use some of the values already programmed in the module
when changing the values. The module costumer must be able to read the values first. Added
mailbox PNIO_GET_IM0_INFO, also some minor changes are done to mailbox
PNIO_SET_IM0_INFO. Internal ID: 0004739.
• PNIO_SET_IM0_INFO, if the serial number is set to all 0x00 the default serial number should
be used – If the application uses this mailbox, but sets the serial number to 16 * 0x00 this is an
indication that the default serial number shall be used. Changed so that if the serial number field is
set to all zeroes, the default value for the serial number is used. Internal ID: 0004551.
- Bug fixes
• IP-config and Station-name disappears after power-cycle– Sometimes when restarting (?) the
module these parameters disappears. This is seen frequently with the ABS-PIR (FO?) when mounted
on an ABC.Added check of IP configuration in PNIO_cbf_save_ip_addr(). There will be no new
storage if already cleared and stored. Internal ID 0004565.
• Station name might disappear - If the IO Controller assigns the IP-address at start-up this be set
"non-remanent". In this case the Ethernet configuration file will always be written. If the module
would be re-started during the set of these parameters the file system will get corrupted and the
station name lost. This should be changed so that the Ethernet configuration is only stored if the
information is new. Added check of IP configuration in PNIO_cbf_save_ip_addr(). There will be no
new storage if already cleared and stored. Internal ID: 0004592.
• No module diff-block if incorrect I/O size configured – (applies only to Any-mode) If the IO
controller is using more I/O data than what is configured by the host application the Anybus module
will set these to BAD and go to STOP. According to the test centre this is not OK. The Anybus
module should return these slots with a Module Diff Block (wrong module). Internal ID: 0004598.
• Not possible to affect FW version – It is not possible to affect the Anybus firmware version
displayed for HICP, WEB (SSI) and Telnet (disabled). This information origin from constant
FBU_ANYBUS_SW_VERSION. A suggestion would be to fetch it from variable
PNIO_sPnioSettings.sIm0.abSwRevision.The firmware version for HICP, WEB(SSI) are now
updated through PNIO_sPnioSettings.sIm0.abSwRevision. Internal ID: 0004610.
• “Remanent” data is not erased by a Factory reset – If a Factory reset command is launched via
the PROFINET network the remanent data that stores the PDEV settings is not erased! This is
absolutely mandatory in order to be conform with PROFINET.Function Bsp_nv_data_clear() is
called when a Factory reset command is received. Internal ID: 0004779.
• Security issue; possible to kill the SNMP agent – This issues was found by a customer when
running the security test program Qualysguard. Added a filter that only forwards SNMP messages
that seems to be valid to the VxWorksagent.The timeout value when forwarding a SNMP message to
the agent until the next message can be forwarded is decreased to 100 ms (used to be 1 sec). All
telegrams that enter port 8060 is discarded. Internal ID: 0004780.
• Potential problem with FTP-firmware update – If a file is downloaded to the file system of the
Anybus module with FTP the file system could become corrupted if the power of the module where
removed directly after getting acknowledge of the file transfer via FTP. Changed so that the
downloaded file is closed before transmitting acknowledge. Internal ID: 0005052.
Created: 2012-05-15
RELEASE INFORMATION


• The mailbox communication becomes blocked – When the application uses the mailbox interface
extensible there is a slight chance that the mailbox interface becomes blocked. When this happens
the Anybus module will stop receiving, or transmitting, mailboxes to/from the application. If the host
application will continue to “re-transmit” mailboxes the Anybus module might generate a fatal error.
A correction has been added which guarantees that the Anybus module always reads the correct
value of the application handshake register (when the fault occurred the Anybus module would
incorrectly use 0 as value for the application handshake register). Internal ID: 0005087.
- Other changes
• Merged projects 7254-ABS PIR and 7257-ABS PIR FO – These two previously separated
firmware files have been merged into one trace, since they share most of the source code.From now
on they share the same source code, use the same software version, and functional specification. The
PHY type (copper of fiber optical) is defined through the build specification in Tornado. Differences
among the projects are the added I2C object used to monitor diagnostic information for the optical
phy1 and phy2, and the PHY drivers selected in the PNIO stack, besides than that the software is be
identical.
• Missing keywords IOxS_Length (GSD-file) – The two keywords IOPS_Length and IOCS_Length
are not defined for the <IOData> elements. According to the GSDML-specification V2.20 these are
optional, but according to a customer this might cause problems with some IO controllers that scans
GSD-files for these keywords.Defined the parameters IOPS_Length and IOCS_Length. Internal ID:
0004748.
Created: 2012-05-15
RELEASE INFORMATION

Created: 2012-05-15
RELEASE INFORMATION

Updated in version 2.02 Build 1:
- Improved/changed functionality
- Bug fixes
• Bug ID: 0004208
o Description:
Process alarm mailbox.
o Observation:
The PROFINET stack in version 3.0.0.0 does only support the user struct identifier values of
<= 0x7FFF and 0x8201. Currently the process alarm mailbox supports other values that
these which, if used, will cause the module to go to FATAL.
The process alarm mailbox should be updated so that the check of the user struct identifier
uses the new values which are to be supported.
o Solution:
Fixed so that only user structure identifier values of up to 0x7FFF are supported, else the
process alarm mailbox will return an error to the application.
• Bug ID: 0004239
o Description:
Certification issue: IOCS consumer status.
o Observation:
IOxS changed from bad to good slightly after the ApplicationReady telegram was sent.
This haven’t been a problem in the RTC1/RTC2 mode but showed up during a stack update
when in RTC3 mode. At the time a workaround, as discussed with Mr. Bullerschen, were
implemented.
o Solution:
When the device starts up in irt top (RTC3) mode a 2 step-application ready method is used.
IOxS must have changed from bad to good before the second frame is sent from the device
(ControCommand.ReadyForRT class 3 = 1).
The solution is to call PNIO_initiate_data_write() in the callback function
PNIO_cbf_ar_indata_ind () before returning. All prior PNIO_initiate_data_write calls will
have no effect in RTC3.
In RTC1/RTC2 mode a first data exchange in PNIO_cbf_param_end_ind() should be
sufficient.
• Bug ID: 0004503
o Description:
Maximum number of AR's for RT Class 1, 2 should be increased.
o Observation:
Should use same value as the PNIO Devkit application.
o Solution:
Maximum number of AR's for RT Class 1, 2 has been changed to two.
Created: 2012-05-15
RELEASE INFORMATION

• Bug ID: 0004191

o Description:
NMAP crashes the HICP- and SNMP server.
o Observation:
After completion of the NMAP security test the module stops responding to HICP- and
SNMP requests.
The isolated test case that makes this happening is 'Test case 3' (UDP scans) in the 'SDV-
7254-029 ABS-PIR Security test specification'.
o Solution:
Malformed mib2 requests, from external clients, did kill the Vxw-MIB2 agent listening on
port 8161. This port was intended for internal communication only, in this case between the
PNIO SNMP and MIB2 agent, and is considered to be an unnecessary "backdoor" which has
now been closed. SNMP requests on the well known port 161 is received and processed as
before. This problem was a PNIO stack issue.
An UDP telegram with no user data disabled the HICP server, it was interpreted same as
disabling the object by sending mailbox message HICP_CFG_CONTROL. The
hicp_fHicpEnable flag is now used to distinguishing the two cases from each other.
• Bug ID: 0004495
o Description:
Error when reading the input records of Interface and Ports.
o Observation:
According to IEC61158-6-10 (PROFINET IO PROTOCOL description) the submodules that
does not contain IO data are treated as Inputs without data, but with IOPS.
o Solution:
Read requests for input data from DAP, interface and ports give an OK response with no IO
data (lengthdata = 0) but with IOPS/IOCS status.
• Bug ID: 0004486
o Description:
Investigate the possibility to have the DAP with same module Id in two flavours.
o Observation:
According to Bullerschen it is allowed to have two DAPs (with and without PDEV) with the
same module id. Having it this way would solve alot of our problems.
o Solution:
The firmware as of 2.05 (or 3.00) supports having the DAP2 without PDEV.
Only the GSD file needs to be updated to support this.
• Bug ID: 0004474

o Description:
Issues with default gateway settings.
o Observation:
No RPC answers under certain conditions during the conformance test (case “FN 3”). The
problem got isolated andproduced by first sending an IP request that sets default gateway to
0.0.0.0 followed by a second request that sets it to some other valid value (not 0.0.0.0).
o Solution:
Created: 2012-05-15
RELEASE INFORMATION


Added fix in vxw_sys_end.c. This problem was a PNIO stack issue.
• Bug ID: 0004423
o Description:
The I&M information for the Interface and Port(s) cannot be set.
o Observation:
When trying to set the I&M information (if enabled) for the Interface (sub-module 0x8000)
and Port(s) (sub-module 0x8001-0x800x) an error message will be generated (0xB8).
According to Klaus Götz of Comdec it should be possible to set these if I&M is supported.
o Solution:
Changed so that I&M0FilterData is not added for Interface and Port SubModules.
Created: 2012-05-15
RELEASE INFORMATION

• Update to PAS ver. 3.09.01
• Update to PNIO stack ver. 3.1.0
- Bug fixes
• Bug ID: 0002834
o Description:
IRT-mode with a minimum bus cycle time (1ms) and a large amount of incremental data
causessomeproblems. The DUT ends up in OFF-lineonce in a while and finally remains in
that state. A restart of the master was always required to bring the system back.
o Observation:
There haven’t been any problems, or signs thereof, when running the module in IRT high
performance mode after implementation of PNIO stack ver. 3.1.0.
o Solution:
Update to PNIO stack ver. 3.1.0. The GSD-file has been edited so that 1 ms bus cycle time
now is supported.
• Bug ID: 0004094
o Description:
Handling of record index 0x8028 and 0x8029.
o Observation:
Should be supported.
o Solution:
Implemented functionality to handle read requests with index 0x8028 and 0x8029.
- Other changes
Created: 2012-05-15
RELEASE INFORMATION

- Bug fixes
- Other changes
• Bug ID: 0004017
o Description:
Profile Specific Type in I&M0 must be set to a valid value.
o Observation:
The migration guide says that for future certification test cases this should be set to any valid
value between 1..6.
o Solution:
Profile Specific Type is set to 0x0004 (Communication Module).
• Bug ID: 0004015
o Description:
Update memory configuration for SDRAM.
o Observation:
SDRAM has been changed to IS42S32800D-75EBLI.
o Solution:
Updated the memory configuration.
• Bug ID: 0003981
o Description:
Update to PROFINET stack ver. 3.1.0.
o Observation:
PROFINET stack ver. 3.1.0 has been released.
o Solution:
PROFINET stack updated to ver. 3.1.0.
• Bug ID: 0003934
o Description:
Change handling of HW revision.
o Observation:
FBU_GetHwVersion() should return HW func ID. Remove the use of GPIO 23,24 and 27.
o Solution:
HW func ID is used as hardware identifier.
• Bug ID: 0003877
o Description:
Serial number is byte swapped.
o Observation:
The serial number in the DPRAM is byte swapped. Representation should be in Motorola
format.
o Solution:
Representation is changed to Motorola (Big Endian) format.
Created: 2012-05-15
RELEASE INFORMATION


• Bug ID: 0003734
o Description:
The same mailbox message ID can be allocated twice at the same time.
o Observation:
When the module gets a unique message ID for a mailbox, it is not returned inside a critical
section which means that two different tasks can get the same message ID. It will still
allocate two different message IDs in a list but only one of them will be freed. This may
affect all mailbox messages that are sent to the application but in different shapes and
variations.
o Solution:
The fix is done in FBU_GetMailboxID( UINT8 bPool ).
Assign a local variable the real message ID inside the critical section and then return it.
- Bug fixes
• Bug ID: 0003617
o Description:
Module web server may fail to detect SSI tag.
o Observation:
This issue was reported for ABS-ETN 100 (ID 0003120) but concerns this module as well:
Under some circumstances the module web server may fail to detect an SSI tag.
o Solution:
Fix originate from "7188-ABS ETN 100" and concerns the SSI scanning function which
could miss an SSI command.
• Bug ID: 0003615
o Description:
Module hangs when mounting a RAM disc.
o Observation:
This issue was reported for ABS-ETN 100 (ID#3325) but concerns this module as well:
Solution:
Removed the possibility for a pointer (located in the uninitiated ram disc) accessing an
invalid memory location.
• Bug ID: 0003610
o Description:
No Network status in FB specific area.
o Observation:
The Network status register in the Fieldbus specific area (DPRAM address 0x700-701)
seems not to be implemented. The LINK/USE bits are never set.
o Solution:
Added support.
• Bug ID: 0003468
o Description:
The module enters FATAL when an invalid Station name has been set.
o Observation:
The Profinet stack will call the error callback with a FATAL indication when an invalid
Station name has been sent to the stack. Briefly the stack only accepts:
Created: 2012-05-15
RELEASE INFORMATION


* a-z
* A-Z
* 0-9
*-
*.
See function oha_is_valid_station_name() in oha_lib.c for further description.
There is no check when writing to the Station name or when reading it from FLASH.
o Solution:
Added checking of the Station Name during stack initialization. If the Station Name is found
to be invalid, it is reset to "".
Created: 2012-05-15
RELEASE INFORMATION

• Bug ID: 0002776

o Description:
No possibility to format the filesystem via bootloader jumper.
o Observation:
It should be possible to format the file system by closing the bootloader jumper. This
functionality was missed when the bootloader was implemented.
o Solution:
Increased the amount of FLASH in the setup section of the MPU and I-Cache in romInit.s.
The correct FLASH segment, the used sector field, is now affected by the erase operation in
Bl_Main.c.
• Bug ID: 0003542
o Description:
DNS_REQUEST causes a crash.
o Observation:
Sending mailbox message DNS_REQUEST (alias GET_HOST_BY_NAME) causes a
FATAL event.
o Solution:
Increased FBU_GHBN_STACK_SIZE.
• Bug ID: 0003548
o Description:
Mailbox SendTo does not work properly.
o Observation:
The Mailbox SendTo does not work properly for an UDP connection.
Reason is not known (maybe word-swap of IP address?)
o Solution:
Mailbox SEND_TO is rejected because a Connect request is performed earlier in the script.
Reading the Fieldbus appendix indicates that SEND_TO should not be used for connected
UDP sockets. (If the socket is connected, SEND should be used instead "writers remark").
The fix in this case is to remove the connect request in the script test_HOS_Socket.py.
Appareantly the network stack (InterNiche) for our native Ethernet modules does not do this
check since they accept a preceeding connect request. However the VxWorks network stack
does not.
• Bug ID: 0003263
o Description:
Issue with socket mailbox message RECV_FRAG_FROM.
o Observation:
Socket mailbox message RECV_FRAG_FROM contains no IP- or port number in the
response. This is true only in blocking mode, in non-blocking mode it works fine.
o Solution:
This issue was fixed for ABS-ETN 100 and is now also merged into ABS-PIR.
• Bug ID: 0003562
o Description:
HTTP server.
o Observation:
General python script (http.py) reports five failures. Refer to test report for which one.
It has not been investigated "what is why".
Created: 2012-05-15
RELEASE INFORMATION


o Solution:
Configuring the VxWorks network stack solved most of the problems. Lack of resources
was the main issue.
• Bug ID: 0003517
o Description:
SSI file types.
o Observation:
When a new SSI file type is added to http.cfg, files with the new file type is not scanned for
SSI tags until the Anybus is restarted.
o Solution:
The web server was started before the Anybus is initialised. An effect of this is that the
routine responsible for scanning http.cfg for new SSI file types (http_init) has already been
executed when the Anybus is initialised. Therefor the new SSI file types was not included in
the list that holds the file types.
The web server is now started in the same way as the other IT components.
• Bug ID: 0003539
o Description:
Possible issue with chip select?
o Observation:
There is an possible issue with the chip select signals according to some hardware
measurements that have been made. It seems like chip select can affect SDRAM/FLASH
respectively SDRAM/DPRAM simultaneously.
o Solution:
Further investigations indicated that the problem is related to the DPRAM buffer since chip
select is connected to OE. This problem can not be solved in software and is therefore
considered as resolved.
• Bug ID: 0003372
o Description:
Link LED starts flashing on unused port during the identification process of the Anybus
module.
o Observation:
Link LED starts flashing on unused port during the identification process of the Anybus
module.
o Solution:
Removed conflicting LED control found in the Ethernet Device Driver (implemented by
Siemens).
• Bug ID: 0003495
o Description:
Lack of limitations when plugging subslots 0x8000, 0x8001, and 0x8002 in various ways.
o Observation:
Test executed with the following errors:
• It is possible to plug subslots 0x8000, 0x8001, and 0x8002 in slot 0 although slot 0 has not
been plugged. Plugging subslot 0x0001 gives a correct error indication.
• It is possible to plug subslots 0x8000, 0x8001, and 0x8002 in slot 1 even though these
should only be valid in slot 0. The subslot limit for all slots except 0 should be within
0x0001-0x0004 according to spec.
Created: 2012-05-15
RELEASE INFORMATION


o Solution:
No information.
• Bug ID: 0003494
o Description:
Advanced mode - No config error is indicated when using a wrong DAP version.
o Observation:
No config error is indicated on the status LED when using a wrong DAP version. A check in
Simatic seems to give the correct result so it's probably only a matter of setting the DUT´s
LED in the correct state.
Test executed with the following errors:
• No configuration error present when re-initializing the DUT with DAP2-RT instead of the
current DAP1-RT configuration. The module indicates on-line.
• No configuration error present when re-initializing the DUT with DAP1-RT instead of the
current DAP2-RT configuration. The module indicates on-line.
• No configuration error present when re-initializing the DUT with DAP1-RT or DAP2-RT
instead of the current DAP2-IRT configuration. The module indicates off-line.
o Solution:
No information.
• Bug ID: 0003441
o Description:
PNIO_IND_CFG_MISMATCH - Module indicates config error after "substitute module".
o Observation:
A respond with "Module state” = “Substitute module” (0x0003) will cause the module to
indicate config error (no configuration error should be indicated on the module's status
LED).
Might be a bug too:

According to previous test instructions this substitution should cause step7 to indicate config
mismatch, but no signs of mismatch in step7 can be seen.
This is probably correct and the test instruction is obsolete, but please verify this when at it.
o Solution:
No information.
• Bug ID: 0003428
o Description:
PNIO_IND_CFG_MISMATCH - No info regarding "Desired Module-/Submodule
identifier".
o Observation:
The spontaneous “PNIO_IND_CFG_MISMATCH” mailbox do not give any information
about the “Desired Module-/Submodule identifier”.
Refer to Functional test report SDR-7254-027.

Test case: Configuration mismatch (modules in slot 1 and 2 are swapped), spontaneous
mailbox activated, Response = “Wrong module”.
o Solution:
No information.
Created: 2012-05-15
RELEASE INFORMATION


• Bug ID: 0003538
o Description:
Issue with Event-Triggered email messages.
o Observation:
When source data type for an email definition is set to WORD or LONG it is not possible to
trigger an email. The reason is that there is a byte swap when using these data types.
o Solution:
No information.
• Bug ID: 0003507
o Description:
Mailbox Pnio_Set_Port_Mac_Addr - Wrong error code when attempt is made after
initialization.
o Observation:
Mailbox Pnio_Set_Port_Mac_Addr - When the module has been initialized, any attempt
with this mailbox should give a response with message info 0x8202 instead of current
0x8F02 .
o Solution:
No information.
• Bug ID: 0003506
o Description:
Mailbox Pnio_Set_Port_Mac_Addr - No Fault information when using a PortNr not within
range (1 or 2).
o Observation:
A PortNr not within range (1 or 2) in Pnio_Set_Port_Mac_Addr gives the response message
invalid other (0xF), but there are no error cause to be read out in the fault information
register (Extended word 8).
o Solution:
Added return of fault information "invalid port number".
• Bug ID: 0003535
o Description:
Issue with mailbox SET_SMTP_SERVER
o Observation:
There is a byte swap issue with this mailbox. IP is written backwards.
o Solution:
No information.
• Bug ID: 0003516
o Description:
SSI Printf/Scanf.
o Observation:
Handling of floats does not work when using SSI tags Printf() and Scanf().
Solution:
Included missing VxWorks component that enables float handling.
• Bug ID: 0003504
o Description:
Mailbox GET_MAC_ADDR - No return of fault info when an invalid MAC selection is
requested.
Created: 2012-05-15
RELEASE INFORMATION


o Observation:
Mailbox GET_MAC_ADDR does not return any fault info when an invalid MAC selection
is requested.
o Solution:
Added return of fault info.
• Bug ID: 0003498
o Description:
No log of fatal implemented in GS_TrapFatalEvent().
o Observation:
No log of fatal is implemented in GS_TrapFatalEvent(). For more info, refer to the 7251-
ABS PRT project.
o Solution:
The "fatal.log" functionality is now supported.
• Bug ID: 0003308
o Description:
Hardware version number in GSDML file potentially incorrect.
o Observation:
Make sure that the HardwareRelease Value in the GSDML file matches the HW version set
by GPIO 23, 24, 27 (a valid range is 1-8).
o Solution:
HW version in GSD file is set to "V2" due to new hardware with support for one flash (i.e.
schematic version 1.2.1).
Created: 2012-05-15
RELEASE INFORMATION

- Bug fixes
• Bug ID: 0003498
o Description:
No log of fatal implemented in GS_TrapFatalEvent().
o Observation:
It is not possible to get a “fatal.log” file through the file system.
o Solution:
Implemented the “fatal.log” functionality .
- New functionality
- Bug fixes
- Other changes
• Adapted for new hardware – Note that it is not possible to do a software update on old cards. Refer
to section ‘Supported hardware’.
• Updated major version number – Set the version number to 2.00 since the update, from a
customer point-of-view, is major.
- New functionality
• Added complete IT functionality – Web-server/SSI, E-mail client and Mailbox socket interface is
supported. The following mailbox messages have been added:
o Web.
DISABLE_WEB_SERVER, ENABLE_WEB_SERVER. Internal ID: 0002860, 0002861.
o SSI.
REQUEST_SSI_DATA, WRITE_SSI_DATA. Internal ID: 0002889, 0002890.
o Mailbox socket interface.
SOCKET_NB, SOCKET_B. Internal ID: 0002871, 0002872.
LISTEN, ACCEPT, CONNECT, CLOSE. Internal ID: 0002873, 0002874, 0002875, 0002880.
SEND, RECV, SEND_TO, RECV_FROM. Internal ID:0002876, 0002877, 0002878, 0002879.
GET_SOCKET_OPTION, SET_SOCKET_OPTION. Internal ID:0002881, 0002882.
SEND_FRAG, RECV_FRAG. Internal ID:0002883, 0002884.
SEND_FRAG_TO, RECV_FRAG_FROM. Internal ID:0002885, 0002886.
o E-mail.
SEND_EMAIL, SET_SMTP_SERVER, GET_SMTP_SERVER, SET_SMTP_SERVER_NAME.
Internal ID: 0002887, 0002856, 0002858, 0002857.
Created: 2012-05-15
RELEASE INFORMATION


• Added Modbus/TCP functionality – The following related mailbox messages have been added:
DISABLE_MB_TCP, MB_CONN_TIMEOUT. Internal ID: 0002863, 0002862.
• Added miscellaneous mailbox messages – The following mailbox messages have been added:
CREATE_RAM_DISC, GET_DNS_SERVERS, SET_DNS_SERVERS, SET_HOST_DOMAIN,
GET_HOST_DOMAIN, GET_HOST_BY_NAME, DISABLE_VFS, CRC_FS.
Internal ID: 0003091, 0002869, 0002867, 0002868, 0002870, 0002888, 0002864, 0003092.
• Improved SNMP functionality – Added support for setting some SNMP MIB parameters, both in
the PNIO MIB and MIB2. The following mailboxes have been added for this purpose:
PNIO_SET_SYSTEM_DESCRIPTION, PNIO_SET_INTERFACE_DESCRIPTION,
PNIO_SET_SYSTEM_DESCRIPTION_MIB2, PNIO_SET_SYSTEM_CONTACT_MIB2 and
PNIO_SET_SYSTEM_LOCATION_MIB2.
• MAC address handling –Added mailboxes SET_MAC_ADDR and PNIO_SET_PORT_MAC_ADDR.
Removed mailbox USE_TEMP_SETTINGS and related stuff since it is considered to be obsolete.
Adjusted MAC selection field in mailbox GET_MAC_ADDR.
• HICP works according to specification – It is now possible to detect the Anybus even if it does not
belong to the same subnet as the HICP client. E.g. if IP-address equals 0.0.0.0 it shouldnowturnup in
the “Anybus IP config tool”.
• IP settings are cleared if IP address set with DCP (non remanent) – If the IP address is set with
DCP and the remanent flag (remanent=false means that the IP address should be temporary set) is set
to false, the IP settings, of the Ethernet configuration file, are set to 0. This means that the next time
the module start-up the IP address will be 0.0.0.0. Internal ID: 0003371.
• Reset to factory settings – Via the PROFINET network it is possible to reset the Anybus to its
default settings. After restoring the configuration files the module will automatically reset it self (i.e.
the application needs to reinitialise the Anybus). Internal ID: 0003373.
- Bug fixes
• Incorrect LED pattern – When the file system was formatted using mailbox message FORMAT_FS
the Watchdog LED was set to flash green 1 Hz even though the Anybus is not initialised.
Internal ID 0003089.
• Incorrect length for I&M requests – Each I&M request is associated with a so-called “block
header”. The “block header” contains two fields: a length and a version number. The length of
“block header” was not calculated correctly, it was two bytes to short. This has been corrected so
that the correct “block header” length is returned when reading I&M data. Furthermore the length is
now correct when an I&M block is written. With previous software the I&M data could not be
changed if a correct request were sent. Internal ID: 0003292.
• Incorrect default value for I&M Date – With I&M 2 the installation date of the device can be read
out. The default value for this parameter has changed in the PROFINET IO specification from
blanks to “YYYY-MM-DD HH:MM”, therefore the module has been updated to return this default
value instead. Internal ID: 0003294.
• Incorrect maximum length for Station Type – With previous firmware versions the maximum
length for the Station Type were set to 25 bytes. In this version the length is set to 64 bytes as
specified in the manual. Internal ID: 3295.
• Extended IP address suite validity check – When an IP address suite is assigned to the module the
validity check is extended to cover all the invalid cases defined by the PROFINET IO specification.
Created: 2012-05-15
RELEASE INFORMATION


Previously no validity check was used, which could cause the module to generate a fatal error if the
module were given an invalid IP suite. Internal ID: 0003180.
• Cannot log into FTP session – If the first command sent to a newly opened FTP session is not
“USER”, it is not possible to log in. Corrected so that it is possible to log in even if the first
command is not “USER”. Internal ID: 0003377.
- Other changes
• Internal software component PAS updated to version 3.07 – This is a maintenance update and is
not expected to change any behaviour in this firmware.
Created: 2012-05-15
RELEASE INFORMATION


• Removed compression of the image and thus speeded up the boot time.
• Support for “Advanced” mode.
• Bug ID: 0002776 & 0002777.
o Description:
No support for formatting of the file system.
o Observation:
It is not possible to format the file system via bootloader jumper or mailbox message.
o Solution:
Added support to format the filesystem via both bootloader jumper and mailbox message .
• Bug ID: 0002839
o Description:
IP-access configuration does not work correctly.
o Observation:
It is not possible to connect to the FTP server if ip_accs.cfg contains an access restriction
containing wild cards(*). For example: [FTP] 10.10.21.* or [All] 10.10.21.*.
o Solution:
Byte swap issue with subnet mask.
• Bug ID: 0002845
o Description:
IM1-4 is not supported.
o Observation:
An attempt to access IM 1-4 results in the response “Feature not supported” or ”Invalid
parameter”
o Solution:
Corrected some data fields from big to little endian.
• Bug ID: 0002850.
o Description:
Problem with application watchdog functionality .
o Observation:
Sometimes the Anybus does not start communicate via PROFINET if the Watchdog timeout
value is greater than 0 (i.e. watchdog monitoring is enabled).
o Solution:
Fixed by typecasting (iWdCounterOut - iWdCounterIn) to an UINT16.
• Bug ID: 0002892.
o Description:
PLC Run/Stop is not supported.
o Observation:
Altering PLC operation mode to STOP is not detected by the Anybus.
o Solution:
Added support for PLC Run/Stop.
Created: 2012-05-15
RELEASE INFORMATION

• Bug ID: 0002918

o Description:
Issue with HICP password protection
o Observation:
Giving a new password without already having one, results in a pop-up window from
“Anybus IP config tool” saying "Invalid password". However, the newly assigned password
is accepted and used by the Anybus.
o Solution:
This was rather a problem related to the Anybus IP config tool than the Anybus itself.
• Bug ID: 0002921
o Description:
Timing issues for request of DPRAM IN/OUT area.
o Observation:
Some times very long (~10 ms) access times were observed.
o Solution:
Changed the priority for some tasks.
• Bug ID: 0002934
o Description:
Problem when assigning IP address/Subnet mask in run-time.
o Observation:
When changing IP address to a new one, and then back to the original address, the Anybus
does no longer respond correctly to ping requests.
o Solution:
This issue got solved by adding two VxWorks components:
-END attach interface and
-END interface support
Created: 2012-05-15
RELEASE INFORMATION


• Bug ID: 0002782 resolved.
o Description:
Some tasks start earlier than they are supposed to do, which causes a race condition at start-
up that may cause problem.
o Observation:
The only concrete observation is that the watchdog LED sometimes flashes 2 Hz (indicates
uninitialised) even when the Anybus is initialised.
o Solution:
This was solved by adding a task with the lowest task priority in the system, which is
responsible for starting all tasks in a synchronized way.
o Description:
Configuration error when using only input modules.
o Observation:
The module indicates configuration error when using only input modules. However, data
exchange is working as normal (i.e. IO data is copied)
o Solution:
No information.
o Description:
The Anybus does not operate on PROFINET if all 16 slots are occupied. It works with 15
slots.
o Observation:
The Anybus remains in OFF-line mode if all slots are occupied.
o Definition of Maximum number of slots has been increased with one slot.
• Bug ID_ 0002844 resolved.
o Description:
IM0 information is byte swapped.
o Observation:
Byte swap problem exists for some IM parameters, for example Profile ID, IM supported
and Manufacturer ID.
o Solution:
Word parameters (2 byte integers) are byte swapped before copied to mailbox message.
o Description:
HICP password protection does not work
o Observation
Even if a password is set, it is still possible to modify IP settings with the Anybus IP config
tool.
o Solution:
An uninitialised variable was causing the problem.
Created: 2012-05-15
RELEASE INFORMATION


o Description:
The Anybus fails to enable the application interrupt when continuously write operations
have been done to the Application indication register of the DPRAM.
o Observation:
Application interrupts are no longer triggered when continuously writing to the Application
indication register.
o Solution:
Added check so that the application and the Anybus do not access the Application indication
register simultaneously.

• First release
Bugs that are found in this software release should be reported back to HMS support department.
Report product, software version, configuration, how to reproduce behaviour, and the effects of
the bug.
Created: 2012-05-15

Release Information HMS PDF

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Release Information HMS PDF

Caricato da

Copyright:

Formati disponibili

RELEASE INFORMATION

Project name Project No

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

This release contains:

Reason for release:

No known compatibility issues.

How to upgrade from previous versions:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 3.20:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 3.08:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 3.07:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 3.05:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 3.04:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 3.03:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 3.02:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 3.01:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 3.00:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 2.03:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 2.02 Build 1:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

• Bug ID: 0004191

• Bug ID: 0004474

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 2.01 Build 2:

Anybus-S PIR / PIR FO 7254

Application Version 3.20 2012-05-16

Updated in version 2.01 Build 1:

Anybus-S PIR / PIR FO 7254