Hello,
I have poroblem with define input in function block modbusFB.serverTCP 'dataModel',
in my aplication I need starting Input Registers from 3000, and I must define this in 'data Model' but I dont now how exacly to do it.
Anybody now somethin about this?
ditto
I'm just getting my codesys wheels on and the modbus stuff is confusing.
I am re-platforming an existing PLC application
On that platform one could simply tag variables to register numbers and the whole shooting match could be accessed via modbus and typically holding registers and input registers were treated the same way...
On codesys I see there is a modbus TCP server Device I/O mapping tab and a Modbus TCP server IEC objects tab
I get the sense that one can configure the serving of variables both/either way but am unclear about the optimum/necessary path.
Apparently in the IEC Objects tab one can "ADD" something or other - presumeably channels. I have created a preliminary function block but the Select Function Block window shows nothing to select WTH ?
I exported the Device mapping and was surprised to see the entire Device IO map - complete with all the bit-mapped holding/input registers!! WTH!!?? Bit-mapped words are strictly a nichey special purpose application.
I am targetting making a couple hundred variables available which would turn into hundreds of pages of IO/mapping
Is the FUnction Block IEC objects thingy an alternative to that ?
I notice that CODESYS shows the tags which the PLC used to specify the register address... are tags used in CODESYS for any specific hard-core purpose ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I have poroblem with define input in function block modbusFB.serverTCP 'dataModel',
in my aplication I need starting Input Registers from 3000, and I must define this in 'data Model' but I dont now how exacly to do it.
Anybody now somethin about this?
ditto
I'm just getting my codesys wheels on and the modbus stuff is confusing.
I am re-platforming an existing PLC application
On that platform one could simply tag variables to register numbers and the whole shooting match could be accessed via modbus and typically holding registers and input registers were treated the same way...
On codesys I see there is a modbus TCP server Device I/O mapping tab and a Modbus TCP server IEC objects tab
I get the sense that one can configure the serving of variables both/either way but am unclear about the optimum/necessary path.
Apparently in the IEC Objects tab one can "ADD" something or other - presumeably channels. I have created a preliminary function block but the Select Function Block window shows nothing to select WTH ?
I exported the Device mapping and was surprised to see the entire Device IO map - complete with all the bit-mapped holding/input registers!! WTH!!?? Bit-mapped words are strictly a nichey special purpose application.
I am targetting making a couple hundred variables available which would turn into hundreds of pages of IO/mapping
Is the FUnction Block IEC objects thingy an alternative to that ?
I notice that CODESYS shows the tags which the PLC used to specify the register address... are tags used in CODESYS for any specific hard-core purpose ?
more posts ...
I created Modbus Server TCP, but when I try started i have a error "TCP socet error" "Error on open/close/read/write TCP socket."