https://forge.codesys.com/forge/talk/Engineering/thread/a52d50ed7f/2020-02-27T14:10:18.024000ZRecent posts to Modbus Serial as easy as...2020-02-27T14:10:18.024000Z2020-02-27T14:10:18.024000ZDanybbahttps://forge.codesys.com/u/danybba/https://forge.codesys.com94f590201eb3b55c81d59f55bb7b7b1781947379

<div class="markdown_content"><p>Hy, I have the same Problem: </p> <p>First question is ist possible to use teh Raspberry with Codesys as a Modbus RTU Slave Device? </p> <p>If yes I implemented the Modbus Com Port and added the Modbus Serial Device. I also added the .cfg code to COMPORT1. But Codesys always says "no driver found" in the State of the comport and the serial device.</p> <p>Can you please help me? </p> <p>Regards Daniel</p></div>

2020-02-27T14:10:17.013000Z2020-02-27T14:10:17.013000Zwilliamchttps://forge.codesys.com/u/williamc/https://forge.codesys.com4c6551e206c02342b81a057955e12970326377e6

<div class="markdown_content"><p>OK - I'll give that a go and see what happens. Thanks.</p></div>

2020-02-27T14:10:16.658000Z2020-02-27T14:10:16.658000ZAndreyShttps://forge.codesys.com/u/andreys/https://forge.codesys.com343016e5893af71871737f760734130605b89654

<div class="markdown_content"><blockquote> <p><strong>williamc hat geschrieben:</strong><br/> I think it's vxworks based.<br/> What is meant by PCI-Bus anyway?</p> </blockquote> <p>I am not sure, what PCI actually means. Maybe something like peripheral communication (component) interface. But it does not have nothing common with the PCI bus from desktop computers. =). This is just a virtual bus for connecting components. This connector is be placed to an error state by the driver, that handels it. This driver use SysCom library. </p> <p>Try to use SysCom functions directly and to look at CODESYS messages on the debug console.</p></div>

2020-02-27T14:10:16.301000Z2020-02-27T14:10:16.301000Zwilliamchttps://forge.codesys.com/u/williamc/https://forge.codesys.com5b028b2b5a6687aaf14005824b55564ac3c555eb

<div class="markdown_content"><p>I think it's vxworks based.</p> <p>What is meant by PCI-Bus anyway?</p></div>

2020-02-27T14:10:15.271000Z2020-02-27T14:10:15.271000ZAndreyShttps://forge.codesys.com/u/andreys/https://forge.codesys.com76706888b7b9174acce24bde4e53937117521fe8

<div class="markdown_content"><blockquote> <p><strong>williamc hat geschrieben:</strong><br/> The driver state stays the same when running or stopped.<br/> The only way I've managed to configure that doesn't show this error is to add a master then a slave but this isn't the physical attributes of the device.<br/> I can't really speak about the device as it is something that is under development however, I have been assured that the Modbus comms should just work. I've been told there are two physical ports on the unit one for debug and one for field bus. But I have tried setting com port to both 1 and 2 and they show same error.</p> </blockquote> <p>Do you use Linux as a base platform for your device? Can you look at CODESYS startup log on your device? SysCom could print some debug message to stdout.</p></div>

2020-02-27T14:10:14.908000Z2020-02-27T14:10:14.908000Zwilliamchttps://forge.codesys.com/u/williamc/https://forge.codesys.com2a488c4586572909ed613f72534057f575291dda

<div class="markdown_content"><p>The driver state stays the same when running or stopped.</p> <p>The only way I've managed to configure that doesn't show this error is to add a master then a slave but this isn't the physical attributes of the device.<br/> I can't really speak about the device as it is something that is under development however, I have been assured that the Modbus comms should just work. I've been told there are two physical ports on the unit one for debug and one for field bus. But I have tried setting com port to both 1 and 2 and they show same error.</p></div>

2020-02-27T14:10:14.496000Z2020-02-27T14:10:14.496000ZAndreyShttps://forge.codesys.com/u/andreys/https://forge.codesys.comcf43beedf685f0f3203326d2ba4e52cb20e3be39

<div class="markdown_content"><p>Is "No driver found" displayed in STOP state of program? <br/> Is it changed to "Bus failure" when you start the program? <br/> The one possible reason can be that you have wrong settings in "Modbus serial port configuration". Usually this causes wrong COM port number.<br/> The other possible reason can be that the PLC vendor does not support SysCom library in the runtime. But this is pretty unlikely. What PLC do you use?</p></div>

2020-02-27T14:10:13.446000Z2020-02-27T14:10:13.446000Zwilliamchttps://forge.codesys.com/u/williamc/https://forge.codesys.combf05e864293fe84d554a7cf2d88ee0764a35362b

<div class="markdown_content"><p>Hi,</p> <p>I'm a bit stuck. </p> <p>I've got a device which runs CoDeSys and has a serial port present. </p> <p>In my application I've added a Modbus Com device and then under this a Modbus serial standalone slave device.</p> <p>I've set my coms port to the physical port of the device and the device to ID 1 and then mapped my input parameter to a variable in my program. </p> <p>Then I use an application to send a modbus message to device id 1, code 6, address 0 and value 1.</p> <p>But I don't receive the value in my program. </p> <p>Where am I going wrong?</p> <p>Any help greatfully received.</p> <p>One additional note...this isn't probably helping.</p> <p>When I run program and look at my Modbus_Com Status I have PCI-Bus : No driver found error. What does this mean?</p></div>