• Replies 4 replies
  • Subscribers 585 subscribers
  • Views 167 views
  • Users 0 members are here
Options
Related

MODNETIBM Driver

Richard J

Anyone know what this driver  is (MODNETIBM), found a reference to it on the support Website but couldn't find it in the driver reference?

Is this just the same as the normal MODNET or there is something special about this one

Any one with the install file for this driver?

Parents

  • I don't have much info about MODNETIBM. It used to be in the Express Communications Wizard under Manufacturer: IBM, Model: Generic Modnet Device. I don't see any help file for it, or any mention of it in the MODNET driver help. The modnetibm.dbf file has different tag addressing definitions than standard Modnet, so your project may not compile if you change to the MODNET driver and your project is using Sxxxxx, Oxxxxx, or Exxxxx addresses.

    TEMPLATE                                    ¦UNIT       ¦RA¦BIT_¦LOW ¦HIGH     ¦COMMENT                 ¦
--------------------------------------------¦-----------¦--¦----¦----¦---------¦------------------------¦
0%U(1,1,99999)                              ¦1          ¦0 ¦1   ¦0   ¦0        ¦Output Coils Status     ¦
1%U(1,1,99999)                              ¦2          ¦0 ¦1   ¦0   ¦0        ¦Input Status            ¦
4%U(1,1,99999)[.%u(1,1,16)]                 ¦3          ¦1 ¦16  ¦0   ¦0        ¦Output Registers        ¦
3%U(1,1,99999)[.%u(1,1,16)]                 ¦4          ¦1 ¦16  ¦0   ¦0        ¦Input Registers         ¦
S4%U(1,1,99999)%R                           ¦0x80000000 ¦1 ¦16  ¦0   ¦0        ¦Read 4xxxxx as string   ¦
S3%U(1,1,99999)%R                           ¦0x40000000 ¦1 ¦16  ¦0   ¦0        ¦Read 3xxxxx as string   ¦
O3%U(1,1,99999)                             ¦41         ¦1 ¦16  ¦0   ¦0        ¦Input Reg, odd addr     ¦
E3%U(1,1,99999)                             ¦40         ¦1 ¦16  ¦0   ¦0        ¦Input Reg, even addr    ¦
O4%U(1,1,99999)                             ¦31         ¦1 ¦16  ¦0   ¦0        ¦Output Reg,odd addr     ¦
E4%U(1,1,99999)                             ¦30         ¦1 ¦16  ¦0   ¦0        ¦Output Reg,even addr    ¦

    I found a note that MODNETIBM is a "Special cache Modnet".

    You should be able to request the old driver installer from Aveva support. They may even have the driver specification document which would explain the differences from MODNET. If they don't have it, it is possible to manually extract the files from your old installation of Citect (or Citect v7.00 if that is the latest release of MODNETIBM). I don't know if it is compatible with newer releases, though. Let me know if you need help to do that.

    You could try making a test project to communicate with one of your devices using MODNET and just read a single tag. If it works, you could try changing all the devices in your project to MODNET (or one of the numbered variants like MODNET11. The E and O addresses may correspond with the G addresses in the standard MODNET driver.

Reply

  • I don't have much info about MODNETIBM. It used to be in the Express Communications Wizard under Manufacturer: IBM, Model: Generic Modnet Device. I don't see any help file for it, or any mention of it in the MODNET driver help. The modnetibm.dbf file has different tag addressing definitions than standard Modnet, so your project may not compile if you change to the MODNET driver and your project is using Sxxxxx, Oxxxxx, or Exxxxx addresses.

    TEMPLATE                                    ¦UNIT       ¦RA¦BIT_¦LOW ¦HIGH     ¦COMMENT                 ¦
--------------------------------------------¦-----------¦--¦----¦----¦---------¦------------------------¦
0%U(1,1,99999)                              ¦1          ¦0 ¦1   ¦0   ¦0        ¦Output Coils Status     ¦
1%U(1,1,99999)                              ¦2          ¦0 ¦1   ¦0   ¦0        ¦Input Status            ¦
4%U(1,1,99999)[.%u(1,1,16)]                 ¦3          ¦1 ¦16  ¦0   ¦0        ¦Output Registers        ¦
3%U(1,1,99999)[.%u(1,1,16)]                 ¦4          ¦1 ¦16  ¦0   ¦0        ¦Input Registers         ¦
S4%U(1,1,99999)%R                           ¦0x80000000 ¦1 ¦16  ¦0   ¦0        ¦Read 4xxxxx as string   ¦
S3%U(1,1,99999)%R                           ¦0x40000000 ¦1 ¦16  ¦0   ¦0        ¦Read 3xxxxx as string   ¦
O3%U(1,1,99999)                             ¦41         ¦1 ¦16  ¦0   ¦0        ¦Input Reg, odd addr     ¦
E3%U(1,1,99999)                             ¦40         ¦1 ¦16  ¦0   ¦0        ¦Input Reg, even addr    ¦
O4%U(1,1,99999)                             ¦31         ¦1 ¦16  ¦0   ¦0        ¦Output Reg,odd addr     ¦
E4%U(1,1,99999)                             ¦30         ¦1 ¦16  ¦0   ¦0        ¦Output Reg,even addr    ¦

    I found a note that MODNETIBM is a "Special cache Modnet".

    You should be able to request the old driver installer from Aveva support. They may even have the driver specification document which would explain the differences from MODNET. If they don't have it, it is possible to manually extract the files from your old installation of Citect (or Citect v7.00 if that is the latest release of MODNETIBM). I don't know if it is compatible with newer releases, though. Let me know if you need help to do that.

    You could try making a test project to communicate with one of your devices using MODNET and just read a single tag. If it works, you could try changing all the devices in your project to MODNET (or one of the numbered variants like MODNET11. The E and O addresses may correspond with the G addresses in the standard MODNET driver.

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.