- Posts: 15
- Thank you received: 0
Classicladder TCP setup ?
- grzesiekzxr
- Topic Author
- Offline
- New Member
-
Less
More
4 years 1 month ago #251684
by grzesiekzxr
Classicladder TCP setup ? was created by grzesiekzxr
Hello Colleagues, at the beginning I want to thank you for creating a forum.
My problem is configuring the classicladder TCP
Can someone post a file .clp with settings for TCP.IP
My problem is configuring the classicladder TCP
Can someone post a file .clp with settings for TCP.IP
Please Log in to join the conversation.
4 years 1 month ago #252078
by HansU
Replied by HansU on topic Classicladder TCP setup ?
Do you want to run Modbus-TCP with Classicladder?
Please Log in to join the conversation.
- grzesiekzxr
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 15
- Thank you received: 0
4 years 1 month ago #252082
by grzesiekzxr
Replied by grzesiekzxr on topic Classicladder TCP setup ?
Yes, I'M able to run classicladder serial,
But I would like to know how to setup tcp, IP, IP port, in config file. Clp.
Thanks
But I would like to know how to setup tcp, IP, IP port, in config file. Clp.
Thanks
Please Log in to join the conversation.
4 years 1 month ago #252094
by Aciera
Replied by Aciera on topic Classicladder TCP setup ?
Have you found the ClassicLadder documentation?
TCP/IP setup is mentioned in Section 9.2:
linuxcnc.org/docs/devel/html/ladder/classic-ladder.html#_modbus
TCP/IP setup is mentioned in Section 9.2:
linuxcnc.org/docs/devel/html/ladder/classic-ladder.html#_modbus
Code:
[list]
[*]If no port name for serial is set, TCP/IP mode will be used…
[*]The slave address is the slave address (Modbus/RTU) or the IP address.
[*]The IP address can be followed per the port number to use (xx.xx.xx.xx:pppp) else the port 9502 will be used per default.
[/list]
Please Log in to join the conversation.
- grzesiekzxr
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 15
- Thank you received: 0
4 years 1 month ago #252259
by grzesiekzxr
Replied by grzesiekzxr on topic Classicladder TCP setup ?
Thank you, I read the documentation and browsed the forum before I posted my request.
Communication with the servomotor works using: mb2hal, qmodbus or by checking ping.
However, I cannot communicate using classicladder TCP.
My attempts:
in the config.hal :
loadrt classicladder_rt numPhysInputs=15 numPhysOutputs=15 numS32in=10 numS32out=10 numFloatIn=10 numFloatOut=10
addf classicladder.0.refresh servo-thread
loadusr -W classicladder --modmaster --modbus_port = 192.168.33.1: 502 custom.clp
#loadusr -W classicladder --modmaster custom.clp
#loadusr -W classicladder --modmaster custom.clp
#loadusr -W classicladder --modbus_port = 192.168.33.1: 502 custom.clp
or trying to configure a connection in file.clp:
MODBUS_MASTER_SERIAL_PORT=192.168.33.1:502
#MODBUS_MASTER_TCP_PORT = 192.168.33.1: 502
I used wireshark and debug to see changes.
Despite many attempts, so far without success
Works on the latest version of LCNC 2.83
Thank you for your interest in the topic.
Communication with the servomotor works using: mb2hal, qmodbus or by checking ping.
However, I cannot communicate using classicladder TCP.
My attempts:
in the config.hal :
loadrt classicladder_rt numPhysInputs=15 numPhysOutputs=15 numS32in=10 numS32out=10 numFloatIn=10 numFloatOut=10
addf classicladder.0.refresh servo-thread
loadusr -W classicladder --modmaster --modbus_port = 192.168.33.1: 502 custom.clp
#loadusr -W classicladder --modmaster custom.clp
#loadusr -W classicladder --modmaster custom.clp
#loadusr -W classicladder --modbus_port = 192.168.33.1: 502 custom.clp
or trying to configure a connection in file.clp:
MODBUS_MASTER_SERIAL_PORT=192.168.33.1:502
#MODBUS_MASTER_TCP_PORT = 192.168.33.1: 502
I used wireshark and debug to see changes.
Despite many attempts, so far without success
Works on the latest version of LCNC 2.83
Thank you for your interest in the topic.
Please Log in to join the conversation.
- grzesiekzxr
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 15
- Thank you received: 0
4 years 1 month ago #252290
by grzesiekzxr
Replied by grzesiekzxr on topic Classicladder TCP setup ?
... "Classic Ladder has a Modbus/TCP server integrated. Default port is 9502. (the previous standard 502 requires that the application must be launched with root privileges)."
Wireshark detect nothing.
IS it posible that need more privileges chmod 777 ?
Wireshark detect nothing.
IS it posible that need more privileges chmod 777 ?
Please Log in to join the conversation.
4 years 1 month ago #252324
by Aciera
Replied by Aciera on topic Classicladder TCP setup ?
I don't really know. Are you getting any information (errors) in the terminal?
Also if you use the default port 9502 do you see anything on wireshark at all?
edit:
Can you post your clp file?
Also if you use the default port 9502 do you see anything on wireshark at all?
edit:
Can you post your clp file?
Please Log in to join the conversation.
4 years 1 month ago #252327
by HansU
Replied by HansU on topic Classicladder TCP setup ?
Just to throw it in here, only in case you haven't heard of it before.
There is a component called MB2HAL, which also allows you to connect to Modbus-TCP devices.
linuxcnc.org/docs/2.9/html/drivers/mb2hal.html
If you are using Classicladder only for Modbus you can consider using this. Or to test the connection to ensure the hardware is connected properly.
There is a component called MB2HAL, which also allows you to connect to Modbus-TCP devices.
linuxcnc.org/docs/2.9/html/drivers/mb2hal.html
If you are using Classicladder only for Modbus you can consider using this. Or to test the connection to ensure the hardware is connected properly.
Please Log in to join the conversation.
- grzesiekzxr
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 15
- Thank you received: 0
4 years 1 month ago #252633
by grzesiekzxr
Replied by grzesiekzxr on topic Classicladder TCP setup ?
Thank you, I know and use Mb2hal is a great soft.
If I find time for further tests, I will let you know what has worked.
If I find time for further tests, I will let you know what has worked.
Please Log in to join the conversation.
Time to create page: 0.115 seconds
