Geospark said:...The node number was 1 for "MICRO1500" in PB32, yes?...
nicer said:1) Yap, it's MICRO1500
I'm sorry, and maybe it's just a language issue, but I was not asking you to confirm the node name. I was actually asking you to confirm that the node number for the node name "MICRO1500", in PanelBuilder32, was node number 1. I am asking this because on the Runtime (Target) tab you have the MicroLogix 1500, under the Serial DH-485 driver, set to node number 1. I'm just double checking you have this set correctly before moving on. Also, is the Station Number for the Serial DH-485 driver set to 2? This, again will set the PanelView to node number 2 at Runtime.
If we put the Test Application aside for the moment, as you don't yet have the necessary cable, and concentrate on the Runtime (Target) path to the controller. If you are happy that the Runtime path is correct (it looks good if those node numbers are correct); When you load and run the application on the terminal, did you, or do you get a message asking whether you wish to use the existing communications setup from the terminal menu or from the application? If so, you should select your application's setup. I think it is doing so already as you've mentioned that you can see the Serial DH-485 driver in the communications menu on the terminal.
With the MicroLogix in Run Mode, and the straight through cable connected to the PanelView, and the application running, what messages are you getting? Does it appear as though some communications are working or is everything throwing up error messages of the failed type? I would try to establish this so you know you have good comms but just have some cleaning up to do in the converted application.
Don't sweat it over the double post and no one here is finding you or your posts annoying, I'm sure.
Regards,
George
Last edited: