Help Please with AutomationDirect Driver

[mjrx]

I am trying to connect to the bottom port of an Automation Direct (Koyo) DL05 w/ DL250-1 CPU. Upper port is used for a local HMI, so I have to use the bottom port for Lookout. In DirectSoft I select DirectNet in Port 2 config and appropriate baud, stop bit, address, etc. I am getting comm alarm "invalid request frame" in Lookout. I can comm with upper port in K-Seq OK, and bottom port Modbus protocol seems to work OK too, but I don't want to go through the V mem to Modbus conversions so I want to use DirectNet  (which is N-Seq). Anyone know of any tricks or tips in this area? Thanks very much. 

[Khalid]

This should help you communicate with the bottom port:

http://digital.ni.com/public.nsf/allkb/5e95de0ef78603c986256570000557ae

Regards,

-Khalid

[mjrx]

Thanks, I already saw that. All that does is tell you how to change from K to N and back. Once I set to N, I can't talk anymore (comm fail).

[Khalid]

I believe -- it's been a while since I did this -- with the above approach, you can talk K-Sequence on the lower port. Is that an option for you?

Thanks,

-Khalid

[mjrx]

Thanks Khalid. K-Sequence may be an option on the bottom port. Would I just setup the driver in Lookout as "Upper Port(k)" even though I'm connected in the bottom port? And can I address the PLC as something other than 1? (I have several slaves on my network, need addressing)

[Khalid]

You're right -- you would just setup the driver in Lookout as "Upper Port(k)" even though you are physically connected to the bottom port.

As for the address, I am not sure.. since we are really using K-Sequence which, normally, expects address of 1. But we are connected to the lower port which can have multiple devices.. so, am not sure. Sorry!

-Khalid

[mjrx]

Thanks Khalid. What about the fact that you cannot use K-Seq on both ports at the same time?

[Ryan.S]

when using "lower port(n)" in lookout, try to make a connection to X0 first.

Someone before seemed to have a communication problem like this, and a connection to X0 acted as a trigger to initialize the object.

[rfoote]

Actually, what it takes for Lookout to start polling the DL05 is a connection being made between an object (pushbutton, switch etc) and any output on the PLC, such as Y0, Y1 etc.

This was back in Lookout 5.1 using the generic Modbus driver, but it might be worth a shot.

I ended up making a "dummy" switch on any screens that needed to interrogate the DL05 for analog input, since that was all I was doing with them.

Message Edited by rfoote on 07-07-2006 10:57 AM

[mjrx]

Thanks for the help - I think I am going to try and use the Modbus driver due to the K and N sequence shortcomings.