FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
07-24-2024 11:37 AM - edited 07-24-2024 11:38 AM
Hello
I have been asked to find out what Input/output byte size limitations the various Ethernet based commuications possibilities are with a CtrlX Core in Drive:
1. CtrlX OS Profinet Device - Max number of Input/ output bytes that can be declared?
2. CtrlX OS OPC UA Pub/Sub and Client - Any restriction on number of read/write data bytes in one packet?
3. CtrlX OS OPC UA Server - Any restriction on data table size?
4. CODESYS Ethernet IP Adapter - Max number of Input/ output bytes that can be declared?
5. CODESYS Profinet Device - Max number of Input/ output bytes that can be declared?
6. CODESYS TCP/UDP Function blocks - Max packet size?
7. CODESYS MQTT - Max packet size? ( I have seen Solved: adjust Maximun packet size in the parameter list (boschrexroth.com) but it wasn't clear if there was any restriction)
I have done various offline tests (e.g. 4 and 5 above did not seem to generate any errors with huge IO size) and searched documentation but struggling to find definitive answers....maybe it is just a limit of network and hardware performance?
Many Thanks
Solved! Go to Solution.
07-31-2024 02:02 PM
I start with some answers – links into the documentations:
For all CODESYS fieldbus communications see the link below and the linked sites by CODESYS directly:
CODESYS - Fieldbus Communication (boschrexroth.com)
08-02-2024 08:24 AM
Hi,
point 6, I tried it and got a max number of 65507 Bytes for UDP.