A-B driver problem, still unsolved

[mjrx]

This problem got marked as solved, but is not. Any NI techs familar with this driver and/or A-B KF2?

I am having a problem with the Allen Bradley driver. The help file says it "enables serial comm via a KE, KF or KF2 module". I am using a KF2 device. I can verify everything with RSLinx, see my program, RS Who shows everything, but when I try lookout I always get the error "STS error 10 reading xxx illegal command or format". Any help would be appreciated, thanks.

Other details: DF1, half duplex, 19200 N81. It seems like it wants to momentarily read device data in Lookout before I get the above error message. 

[mjrx]

Anybody? I can communicate to the Allen Bradley using NI OPC client and KepServer, but I'd rather not spend $800 on the Kep, especially when the Lookout documentation specifically says "use AB driver to communicate with KF2 in full or half duplex".

[Ryan.S]

Could you log the serial communication from both Lookout and the kepware? We can compare the serial data and check the difference.

In Lookout, go to Options->Serial Port, configure the diagnostic file. The file name is like d:\log.txt. Read an address.

In Kepware, configure a tag on same address, and open Quick Client to read. Configure the "Channel" property, on "General" page, check "diagnostics".  Right click on channel, select Diagnostics, you will see the data. Right click on screen and save it as text file.

Maybe we can find something different from the log file.

By the way, what's your lookout version?

[mjrx]

Below is some pasted text from the serial log file. I am trying to communicate with a SLC 5/04 through a KF-2, half duplex. I get the same results when trying a DataLink DL3500 (which os supposed to be the equivalant to the KF-2). RS Linx works fine through both devices, Lookout does not. Notice the funky characters inserted in the lines between the "[   ]" data.

10:56:29.2 - AB1 ->
[10][01][04][10][02][04][00][0F][00][0B][00][A2][02][07][89][00][00][10][03][17][D4]
10:56:29.2 - AB1 <-
[10][06]
10:56:29.2 - AB1 ->
[10][05][04][FC]
10:56:29.3 - AB1 <-
[10][02][04][04]O[10][10][0B][00][10][03]$[89]
10:56:29.3 - AB1 ->
[10][06]
10:56:35.2 - AB1 ->
[10][01][04][10][02][04][00][0F][00][0C][00][A2][02][07][89][00][00][10][03]1[E4]
10:56:35.2 - AB1 <-
[10][06]
10:56:35.2 - AB1 ->
[10][05][04][FC]
10:56:35.3 - AB1 <-
[10][02][04][04]O[10][10][0C][00][10][03][95]H
10:56:35.3 - AB1 ->
[10][06]
10:56:41.2 - AB1 ->
[10][01][04][10][02][04][00][0F][00][0D][00][A2][02][07][89][00][00][10][03]<t

[Andy F.]

mjrx,

Were you able to get a diagnostic log from the Kepware driver so we can compare? You should be able to get this while using the evaluation mode. You are most likely correct that the odd characters between the brackets is the problem, but the compare will help the developers. Also, what version of Lookout are you using? Thanks!

Andy F. 

[mjrx]

Using Lookout 6.0.2

Error message is "STS error 10 reading I1:0 illegal command or format"

Settings 19200 N81 CRC half duplex station 4 SLC5/04 (standard Allen-Bradley SLC-500 driver)

The top part of the screenshot is the Lookout OPC client/KepServer, no problem

The bottom part is the Lookout AB driver.

Both are 4 polls of input I:1.0/0.

[mjrx]

Is there any way NI could help with this driver problem? I'm desperate - I have no choice but to talk to the SLC through a KF2 device in half duplex. Anyone?

[Ryan.S]

I looked into your log data and the DF1 protocol, and found some clue.

The command sent by lookout is almost the same as the one sent by kepserver. The only difference is the address. When you use kepserver, what's the "station number" and "device id" you set for the driver? I'm afraid Lookout doesn't handle it correctly.

The current driver in Lookout has a long history, it is not easy to troubleshoot and debug. we will keep working on this problem.

Just for your information, Lookout 6.2 has the new NI OPC Servers which meets your requirements much better, although the upgrade is not free.

[mjrx]

Thanks Ryan - the station number is 4 and the device ID is 1. I don't know if the new OPC server would work - my system is a serial radio network with 4 nodes - 2 are A-B half duplex, 2 are Modbus RTU (this is why I can't use the Kepware, it needs the serial port and so does Lookout, and also there is no way you can run 2 channels in Kepware using the same serial port, the A-B would need 1 serial port, the Modbus would need another).

[Ryan.S]

What if you set the "PLC address" as 1 in Lookout? I guess you set it as 4.

If it doesn't work, then can you configure the KF2 module as address 0?

I think the driver doesn't work correctly when you use a KF2 module. I even think it doesn't support it... but not sure.

The NI OPC Server works in almost the same way as the kepserver, so I'm sure it works if you have already tested the kepserver.