Product Concerned - Applicom PC Network Interface Cards Product Version - 3.8
Product Concerned - Applicom PC Network Interface Cards Product Version - 3.8
Service Pack 5
for applicom 3.8
Rev Date File Name
1.0 12/10/07 SP5_appPCNIC38.pdf
Description
• Summary
This Note describes you the new feature and correction included in the corresponding Service Pack.
• Cost.
The Service Pack is free of charge.
The two identical tag message was displayed in the very specific case
where the SuiteLink Toolkit creates 2 times an exact same tag. The
PCDDE Server has been changed following the suggestion of
PCDDE -
Wonderware in order to bypass this toolkit behaviour.
This modification will not impact the normal case (customer for which the
phenomenon does not appear).
The OPC server will now support the two following array syntaxes:
- DbxDRy_n returning a byte array containing n right bytes of each
S5 Syntax consecutive word of DB OPC Server
- DbxDLy_n returning a byte array containing n left bytes of each
consecutive word of DB
Note: This feature is not supported in PCDDE
2.1 Software
2.2 Protocol
UniTe TCP Bad status for client equipments access stored in DB PCI2000ETH
NDIS Very high percentage of computer CPU in relation with the applicom
PCI2000ETH
Communication industrial communication and not the additional Ethernet communication
Modbus TCP Bad module identifier send in Modbus frame for AuWriteReadMsg fct DLL
Diagnostic
Profibus DP DP equipments not displayed in diagnostic tool
Tool
3.1 Software
3.2 Protocol
6.1 Software
PCDDE - Memory increase when writing bit of word and byte of word
PCDDE -
- During a write of bit of word tag or byte of word tag, the PCDDE
memory was increasing.
AB Ethernet/IP
WHDDE WHDDE freezed when in the diagnostic interface the spy view display is
Logix 5000
requested.
Software References
[EMF Internal ref] : Corrections
Concerned concerned
Improvement in the Ethernet Communication mechanism of the
applicom solution.
After a item is written, the refresh in the OPC Client application is only
made after the value is confirmed by a read command. In order to avoid
high load on the network with sending a read command after every
write command, the OPC server gets the update of the value in a
normal update cycle (related to the group refresh period). For long
update cycles, the written value can need some time to be updated.
All
The “Send event after write” option will allow the OPC server to send to
the OPC client an event in order to update the written Item with the new
value after the confirmation that the write command was performed
succesfully. This allows a quick update of the value without network
overload.
Be Careful, the value is not confirmed in this case by a read request
OPC until the next update cycle has been performed.
When Symbols are defined in the OPC server (ImpSymb tool) to point
on specific data points, these symbols are defined by default under the
node SYMBOLS in the OPC tree. Now this node can be removed from
the OPC tree and all symboles are then defined directly under the
Topic name.
Please note also that the documentation has been adapted in order to integrate the modifications of the
applicom version SP5. The new version of the documentation has not been integrated in the SP5 installation
package. This version of the documentation is available on the applicom 3.8 Rev 5 CD-Rom or can be
downloaded on the website under the support section.
8.1 Software
Software References
[EMF Internal ref] : Issue corrected
Concerned concerned
[EMF 521] : Status Indicators of the card state at the bottom of the
All
console were updated every 100 milliseconds, now every 1 second.
[EMF 684] : In the configuration Console, when the project is saved, if
the option “DAServer” has been installed from the applicom CD and the
additional DAServer installation package was not performed the
following message will appear.
Could not open key < CLSID\{CFA7F1F7-4921-4234-009E-
F681B4C7A509} > in the registry ! All
This key must be created by setup. The DAServer is not correct
Configuration
console This message has been replace by the following one :
DAServer not installed. It must be installed separately and can be
found on the Wonderware Devices Integration Products CD.
[EMF 668] : After a card initialization from the applicom Console a
message "Impossible to initialize applicom cards" may appear even if
All
the initialization of the card is well performed.
Issue is corrected and no message is anymore displayed.
[EMF 675] : After selecting S-Bus Master as protocol for channel 1 the
applicom Board cannot be initialized.
All
The S-Bus protocol was not activated in this applicom Software
version.
[EMF 495 and 531] : an access violation (OPC crash) occurs in the
OPC Server OPC Server version DA 2.0 only, when deactivating an OPC group or All
the OPC server already deactivated
[EMF 607] : In the OPC spy tool, the format of write message was
All
displaying an error message for a successful write command.
[EMF 403] : In the OPC spy tool, a cyclic function in error displays a
All
message with its handle instead of its status.
[EMF 608] : Problem corrected in the IMPSYMB tool with OPC / DDE
Items importation from the .SCY file.
All
Previously, all items in capital letters that contain the 2 letters AT could
not be imported. Ex: TEMPERATURE.