Firejo
Member
There has been a few posts recently where the 5069-SERIAL module was the topic or at least part of the topic and in those conversations some questions were asked about DF1 compatibility. Well shortly before Automation Fair I received one but my 5069 was tied up in my AB Fair display so I wasn't able to do anything with it.
Well now I have, and the first thing I did was update the firmware released in January which gives it DF1 Full Duplex, Half Duplex (master and slave), Radio modem and DH485 capabilities. The firmware upgrade was a little tricky as the firmware doesn't use a DMK file. So after several hours of fussing around I called Rockwell and found out that you need ControlFLASH 15.03.00 or higher and wound up discovering on my own that it actually requires ControlFLASH PLUS. Once I ran that, I was able to tree down to the module and upgrade its firmware.
But wait, there's more! After the upgrade, RSLinx would identify it with the correct firmware (2.011) but Studio 5000 would not. That required an AOP to be installed. Once I got through all of that it showed up with the correct firmware version and I could configure it with port 2 as a DF1 port (port 1 is Modbus only).
But wait, there's even more! Yes it's a DF1 port BUT... it's a DF1 PCCC port, not CIP. That one surprised me! So when connecting the 5069-SERIAL modules port 2, to a Gateway device, you have to setup the SLC Mapping table and use "N" register nomenclature (I'm guessing "B" and "F" files would work as well but I've not tested that yet) on the Gateway side to communicate with it. What I need to test (when I find more time) is will I have to use a SLC Mapping table on both sides of a DF1 Full Duplex connection if I use another Logix processor? I don't know why anyone would want to do that but the OCD in me has to find out if and how it works.
Well now I have, and the first thing I did was update the firmware released in January which gives it DF1 Full Duplex, Half Duplex (master and slave), Radio modem and DH485 capabilities. The firmware upgrade was a little tricky as the firmware doesn't use a DMK file. So after several hours of fussing around I called Rockwell and found out that you need ControlFLASH 15.03.00 or higher and wound up discovering on my own that it actually requires ControlFLASH PLUS. Once I ran that, I was able to tree down to the module and upgrade its firmware.
But wait, there's more! After the upgrade, RSLinx would identify it with the correct firmware (2.011) but Studio 5000 would not. That required an AOP to be installed. Once I got through all of that it showed up with the correct firmware version and I could configure it with port 2 as a DF1 port (port 1 is Modbus only).
But wait, there's even more! Yes it's a DF1 port BUT... it's a DF1 PCCC port, not CIP. That one surprised me! So when connecting the 5069-SERIAL modules port 2, to a Gateway device, you have to setup the SLC Mapping table and use "N" register nomenclature (I'm guessing "B" and "F" files would work as well but I've not tested that yet) on the Gateway side to communicate with it. What I need to test (when I find more time) is will I have to use a SLC Mapping table on both sides of a DF1 Full Duplex connection if I use another Logix processor? I don't know why anyone would want to do that but the OCD in me has to find out if and how it works.