- This topic has 16 replies, 4 voices, and was last updated 6 years, 10 months ago by
.
-
Posts
-
I am trying to setup Modbus to a Logo! 0BA0 device
I have the Communication line setup in communicator, Rapid SCADA will connect to the PLC as a (shows server connected on the PLC) however I cannot read from any network inputs or write to a network output to the PLC.
Does anyone have a template made for the LOGO! series?
You have a table of registers from the manufacturer Logo! ?
Status of inputs and outputs.
Plus, the other registers you create yourself in the program Logo! and there should be a register card after its programming.I will clarify the manufacture of the device is Siemens the product series is called LOGO!
As per the PLC guide the Modbus addressing is as follows
I am able to get RapidSCADA connected (showing connected as server on the PLC) I am able to read inputs/outputs (I&Q) from the PLC
Please see the following capture form the PLC programming application.
The trouble starts if I try and send command 1 which is to enable 8193 (Q1) nothing happens, if I send command 2 it will enable Q2 not problem.
The next issue I also cannot enable the network input NI1, send command 3 and nothing happens
Here are the screenshots from the modbus line configuration from RapidSCADA
Comm_Line_Param
Any assistance would be great! I’ve been spending a lot of hours trying to solve this and would really like to use RapidSCADA.
c Q2 you have no problem because it is not yet tied to the program. Q1 may not be enabled due to overwriting in the program. Now there is no Logo at hand! Soft Comfort to understand.
As for the lack of response to the NI1 input, a possible problem is that the Communicator sends to the double device,and the input user variables you have are word. The formula for rearranging the bytes before sending the command.
In response, the device says that it has included the network variable NI1, so most likely at the program level it is not included.
Hi,
According to the communication line log, the device understands your command. Nothing happens because of a device logic. You should check that you specify the correct address and value of the commands.
Does the manufacturer provide an utility application that can send the required commands to compare data packages?I am not aware of any utilities, I did find another manual that goes into more detail about network connections using modbus. I will check through it and see what I can find/test.
You may contact the Logo support, provide them communication log and ask for explanation about the device behaviour.
Mkieffer,
I am working on the same PLC at the moment.
Did you manage to get your system working?
Would you mind collaborating with me via email so i can learn how you configured your software please?
Hennie Kotze
hennie _aty_ kwenamining.co.za
+27794914321 (south africa)Regards,
Mkieffer,
Can you please share some screenshots of your PLC setup (Network project) and settings, as well as your rapid scada settings?
I’m still struggling to get connection between the two…
Hi Hennie,
I ended up abandoning Rapid SCADA, I was unable to get it to properly communicate with the PLC.
MK
MK,
Sorry to hear that….
Did you find an alternative?? I would also like to explore different options…
I managed to get my communication working, but now i’m struggling with the graphics in the web station…
HK
Hennie,
I ended up going to — haven’t had a chance to get back to working on my project with it yet though. It’s far more complex than Rapid SCADA.
Would you mind sharing how you got the communication working with Rapid SCADA? It would be much appreciated!
Mike
Mikhail,
What recommendations are you referring to?
MK,
I will send a compilation of screenshots of all my settings, on the scada and on the PLC. I’m in South Africa (GMT +2) so we are going to bed now. Will send them in the morning.
From what i can see in your initial question, you are trying to send a command from the scada to the PLC via network input. Now i have used these network inputs and outputs successfully between two PLC’S, but i think you should maybe send your command via memory address (M) in the PLC. In your modbus address screen shot you’ll see they are mapped as coil 8257. They are read / write (RW). So instead of using the NI1, just use coil 8257 and in the PLC that will be M1.
I will try that tomorrow and let you know.
From where are you?
- You must be logged in to reply to this topic.