Example for CODESYS with a PROFINET IO Controller and a PROFINET IRT Gateway.Example Configuring Temperature Measurements.Installing CODESYS Runtime System on the RevPi Device.Backing up and Restoring a CODESYS License.How to Configure RevPi DIO by Using PiCtory.How to Transfer IO Configuration to logi.CAD3 (Jessie).How to Create a RAP File Exemplified by RevPiTimer.How to Create a Configuration File with PiCtory.How to Run Azure IoT Edge Runtime on RevPi Devices.Enabling and Disabling Revolution Pi Services.How RevPi Core Works w/o Separate Monitor/Keyboard.Installing RevPi Modules on a Top-hat Rail.A total of 30 virtual devices can be configured. Should you need more, then you can simply configure several virtual Modbus devices. Application: RevPi Core makes data available that can be accessed by a masterĪ maximum of 32 registers per virtual device can be used for input and output data.Application: RevPi Core accesses data from another Modbus device.Application: RevPi Core makes data available that can be requested by a master.Application: RevPi Core requests data from another Modbus device.The following virtual devices are available in RevPi Core and can be configured via PiCtory: READ_INPUT_REGISTERĮxample of necessary information for Modbus TCP 9600 Baud, 8 data bits, 1 stop bit, no parity READ_HOLDING_REGISTERĮxample of necessary information for Modbus RTU The kind of register is specific to the device.The Unit ID 255 is recommended to address the gateway itself. But when this Slave is a gateway of ModbusTCP on ModbusRTU, it can address several ModbusRTU Slaves. Then either a ModbusTCP Slave will be clearly identified in the network by means of its IP address. In practice, it depends on the connected device which value has to be set.
0 Comments
Leave a Reply. |