OMR_FINS driver does not read/write strings correctly from all memory areas

• Related Articles

• OMR_FINS Read/Write strings wrong from all memory areas

  Summary OMR_FINS Read/Write strings in wrong byteorder from all memory areas. It seems as the bytes are switched incorrectly. For example, see the following table: zenon displays PLC displays davis adiv test etts etts test var av av var Description ...

• When using the OMR_FINS driver and having option "First character is lo-byte" deactivated, when writing a string variable the OMR_FINS driver sends char null instead of last character.

  Summary The OMR_FINS driver sends char null instead of last character of a string when the option "First character is lo-byte" is deactivated. When having e. g. a string variable of the OMR_FINS driver with String length 10, when writing a string to ...

• FAQ: It seems that sometimes not all variables are correctly written to the PLC by the RGM module, although the system driver variable states that the recipe was written successfully and the option "write synchronously" is active. How can this be?

  When reading a RGM recipe immediately after writing a RGM recipe, with a driver that has the option "keep update list in memory" active, and recipe variables that have been read previously, it can happen that a read cycle is currently in progress, ...

• Checklist: Driver(s) cannot establish a reliable communication

  Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• Mitsubishi FX32 driver does not correctly write strings with an odd number of characters

  Summary The mitsubishi FX32 driver does not correctly write string values which have an odd number of characters DescriptionThe mitsubishi FX32 driver does not correctly write string values which have an odd number of characters Solution An issue has ...