06 driver for Lookout

[maxofmillions]

Just loaded Lookout V6 on computer with directlogic plus latest version and don't have driver of 06 cpu....any help

[Controls Guy]

It probably doesn't need a CPU-specific driver.  The protocol is the protocol and "V2000" appears in all the CPU's.  If they appear to have different drivers per CPU, it might be because the driver pre-screens the requests to make sure the target PLC supports the registers you want to talk to.  Just go ahead and set it for the next closest thing that's in the list and give it a try.

I'm sure the protocol doesn't carry the CPU ID.  First of all, why would it? and secondly, I've run MMI's that only listed other CPU's like say 250 and up (though in that case, you didn't have to specify which one you had), and I just ran it anyway and it worked fine.  They just hadn't kept their supported CPU list up to date.  Now it's possible to FIND OUT which CPU is on the other end of the wire, so the driver could enforce CPU-specificity on the PC-end if they wanted to, but why?

The other alternative is that Lookout surely supports Modbus RTU, and the 06 will act as a Modbus slave on port 2 (the 15-pin 'VGA' port).

[franji1]

Just loaded Lookout V6 on computer with directlogic plus latest version and don't have driver of 06 cpu....any help

What is the version number of DL Plus?

[ddubs2248]

You do not need Direct Logic Plus at all.  You can utilize the modbus conversion for the V-Memory location and X, Y, and C's.   Follow http://forum.automationdirect.com/showthread.php?t=10073 and then click the phrase "with this handy Excel spreadsheet".

[ddubs2248]

You will need to load the modbus driver in Lookout under object, create, driver, and then select modbus.  Use the conversion information provide in the above post.  Let me know if you need further assistance.  I just upgraded a client's HMI to NI's Lookout by using this interface, it works well.