Posted 21 May hi there, how can i config RTU-DNET ( rs485 port ) with my pc? Share this post Link to post Share on other sites
Posted 22 May Configure to do what? It is a DeviceNet Slave (so needs a DeviceNet Master to control it) and, through that, is a Modbus Master for Modbus RTU slaves. You probably need to start here: https://downloadcenter.deltaww.com/downloadCenterCounter.aspx?DID=200&DocPath=1&hl=en-US (Or other translations.) 1 person likes this Share this post Link to post Share on other sites
Posted 22 May (edited) This module is intended to be used as a DeviceNet slave gate to DVP-Slim series DI/DO or special (AI/AO, temperature, loadcell) right-side extension modules. It could be coupled with DVPDNET-SL DeviceNet module. DVPDNET-SL is a left-side module for DVP-Slim series PLCs. Unlike RTU_DNET it could be used as both master and slave. This way users could built a high speed network. Configuration software used is called DeviceNet Builder and could be downloaded freely from Delta's Download center. RS-485 configuration is set by the path Setup-> Communication setting-> System communication port and then <serial port setup> window from the configuration software menu. Both modules could be setup using the same software. The RTU-DNET application manual posted above should be used. DVPDNET-SL operation manual is located here: https://filecenter.deltaww.com/Products/download/06/060305/Manual/DELTA_IA-PLC_DVPDNET-SL_OM_EN_20230906.pdf Edited 22 May by IvanBratanov 1 person likes this Share this post Link to post Share on other sites
Posted 22 May thanks IvanBratanov & pturmel I have a master module on the Kuka robot and I want to communicate with RTU-DNET and also exchange data with the main CPU (PLC) through port RS485. Share this post Link to post Share on other sites
Posted 23 May With the resources I linked, you now know as much as I about this combination. The documentation obviously is oriented towards scanning this DeviceNet slave from a Delta PLC--you'll have to re-interpret that yourself to conform to Kuka's requirements as the master. I don't know anything about that. You will certainly need a PC to DeviceNet hardware interface compatible with the software for that RTU in order to configure it. I assumed you understood that, but maybe not. 1 person likes this Share this post Link to post Share on other sites
Posted 9 June (edited) On 22.05.2024 г. at 9:44 PM, mehrandinio@gmail.com said: I have a master module on the Kuka robot… As I mentioned above DVPDNET-SL module can not work remotely or separately, i.e. it must be coupled with a DVP-S series PLC. I deeply doubt that KUKAs are controlled by such PLCs so you have to couple the DVPDNET-SL to a DVP-SA2 PLC for example first. Then you have to configure both devices to work together. Then you have to connect the KUKA’s automation to the SA2 PLC in order to send and receive data to/from the DEVICENET network. The SA2 has built-in one RS-232 and two RS-485 ports supporting MODBUS ASCII and RTU protocols. If the robot’s automation doesn’t support such interfaces you have to add a coresponding left-side module to the SA-2 PLC. In this case the PLC should interact as s gateway between both interfaces. For example if the robot supports PROFIBUS, you should attach and configure a DVPPF02-SL left-side module to the SA2 PLC. I don’t believe that using third-party automation together with such devices as KUKAs is a good idea because of the complications and difficulties you have to go thru first. Edited 9 June by IvanBratanov Share this post Link to post Share on other sites