• Replies 11 replies
  • Subscribers 585 subscribers
  • Views 629 views
  • Users 0 members are here
Options
Related

DNP Driver

Michael

Using the serial DNP3 driver, but can't get it to commuicate.  Serial cable and port work fine on RTU, and PLC program is trusted.

I'm pretty sure that the issue is in the setup.  The Address is suspect - the help file talks of a device number and the section of the .ini file where the address is?  I must be missing something here.

I see a key name in the client, which seems not to have a place in Citect.  Is that correct?

Any other tips and tricks for this?  I haven't seen a white paper.  The driver help looks like it was for a  few versions ago.

Parents

  • I'm currently working on my first DNP project and have also had some trouble getting comms established - though I'm using ethernet rather than serial.   Setting [DNPR] SCADAAddress in citect.ini is important, so that your server has a DNP address.  But the main thing that tripped me up was data in my RTU not being assigned "Good Quality".  On Citect my tags all showed as Bad, which I assumed was the comms link, when in fact the comms link was fine and it was just the Quality flag in my RTU that was not being assigned. 

Reply

  • I'm currently working on my first DNP project and have also had some trouble getting comms established - though I'm using ethernet rather than serial.   Setting [DNPR] SCADAAddress in citect.ini is important, so that your server has a DNP address.  But the main thing that tripped me up was data in my RTU not being assigned "Good Quality".  On Citect my tags all showed as Bad, which I assumed was the comms link, when in fact the comms link was fine and it was just the Quality flag in my RTU that was not being assigned. 

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