<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Modbus RTU (serial port) does not work with new kernel version</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/50d7b5b1cd/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Runtime/thread/50d7b5b1cd/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Runtime/thread/50d7b5b1cd/</id><updated>2020-02-27T17:04:26.009000Z</updated><subtitle>Recent posts to Modbus RTU (serial port) does not work with new kernel version</subtitle><entry><title>Modbus RTU (serial port) does not work with new kernel version</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/50d7b5b1cd/?limit=25#e226" rel="alternate"/><published>2020-02-27T17:04:26.009000Z</published><updated>2020-02-27T17:04:26.009000Z</updated><author><name>suibaf</name><uri>https://forge.codesys.com/u/suibaf/</uri></author><id>https://forge.codesys.combc1cf6b92f3c614376fcc09e48c917ddc128863a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi Edwin,&lt;/p&gt;
&lt;p&gt;I solved:   &lt;/p&gt;
&lt;p&gt;&lt;a class="" href="http://raspberrypi.stackexchange.com/questions/47379/uart-problems-on-my-pi3" rel="nofollow"&gt;http://raspberrypi.stackexchange.com/qu ... -on-my-pi3&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;in particolar:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Zitat:&lt;/strong&gt;&lt;br/&gt;
You may also need to disable the serial console. The easiest way to do this is via raspi-config under Advanced Options -&amp;gt; Enable/Disable shell and kernel messages on the serial connection.&lt;br/&gt;
If you don't have raspi-config, it doesn't work, and/or you want to double check, first look in /boot/cmdline.txt. If you see:&lt;br/&gt;
 console=/dev/ttyS0,115200 &lt;br/&gt;
Or:&lt;br/&gt;
 console=/dev/serial0,115200 &lt;br/&gt;
Or anything involving console= that isn't console=tty1, remove it. Make sure not to accidentally add a line break to that file, it should remain all one line with spaces between the options, but no spaces around any =.&lt;br/&gt;
The other aspect is the login started by the init system. On Raspbian jessie, check:&lt;br/&gt;
ls /etc/systemd/system/getty.target.wants&lt;br/&gt;
If you see that serial device node (ttyS0) mentioned, disable this service:&lt;br/&gt;
systemctl disable  e &lt;a class="" href="mailto:serial-getty@ttyS0.service"&gt;serial-getty@ttyS0.service&lt;/a&gt; e &lt;br/&gt;
You will have to reboot for these things to take effect.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I don't know what I done, but it work!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Modbus RTU (serial port) does not work with new kernel version</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/50d7b5b1cd/?limit=25#ae2d" rel="alternate"/><published>2020-02-27T17:04:23.364000Z</published><updated>2020-02-27T17:04:23.364000Z</updated><author><name>eschwellinger</name><uri>https://forge.codesys.com/u/eschwellinger/</uri></author><id>https://forge.codesys.com792703a799a25d7f0e923b6384de0794fa6fc1fb</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
yes sounds like this is your problem&lt;/p&gt;
&lt;p&gt;could you check how the OS register your device Login by ssh and type:&lt;/p&gt;
&lt;p&gt;dmesg | grep -i tty&lt;/p&gt;
&lt;p&gt;and as i understand you could give /dev/serial0 a try&lt;/p&gt;
&lt;p&gt;BR&lt;br/&gt;
Edwin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Modbus RTU (serial port) does not work with new kernel version</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/50d7b5b1cd/?limit=25#75d2" rel="alternate"/><published>2020-02-27T17:04:22.426000Z</published><updated>2020-02-27T17:04:22.426000Z</updated><author><name>suibaf</name><uri>https://forge.codesys.com/u/suibaf/</uri></author><id>https://forge.codesys.com3010f5c99a3635f9e3511f22c7da6c8a16f4bccc</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I don't understand very well, but I think that the problem is this:&lt;/p&gt;
&lt;p&gt;&lt;a class="" href="http://raspberrypi.stackexchange.com/questions/49395/raspbian-jessie-4-4-ttyama0-pymodbus-not-working?noredirect=1&amp;amp;lq=1" rel="nofollow"&gt;http://raspberrypi.stackexchange.com/qu ... ect=1&amp;amp;lq=1&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;But I don't understand what I need to do!&lt;/p&gt;
&lt;p&gt;BR&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Modbus RTU (serial port) does not work with new kernel version</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/50d7b5b1cd/?limit=25#566e" rel="alternate"/><published>2020-02-27T17:04:19.611000Z</published><updated>2020-02-27T17:04:19.611000Z</updated><author><name>eschwellinger</name><uri>https://forge.codesys.com/u/eschwellinger/</uri></author><id>https://forge.codesys.com13e6de0a62dd6eaf79b011cdaaaf73b2f89a1f1a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
you need to check if the devices are available under /dev/ttyAMA0&lt;br/&gt;
if you see them there, I could not really imagine what elso should fail then.&lt;br/&gt;
Are you using udev ?&lt;br/&gt;
If yes you Need to check: /etc/udev/rules.d/serial-symlinks.rules&lt;/p&gt;
&lt;p&gt;BR&lt;br/&gt;
Edwin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Modbus RTU (serial port) does not work with new kernel version</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/50d7b5b1cd/?limit=25#bb0a" rel="alternate"/><published>2020-02-27T17:04:18.631000Z</published><updated>2020-02-27T17:04:18.631000Z</updated><author><name>suibaf</name><uri>https://forge.codesys.com/u/suibaf/</uri></author><id>https://forge.codesys.com4fc1a6c9cf9e01d2d2407b6680c9ccb4fcd25a30</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I have 2 raspberry Pi 2. On the first there si raspbian 4.1.19 - V7 + #858 and the last Codesis runtime 3.5.9.10. All work fine also communication with Modbus RTU with ttyAMA0.&lt;/p&gt;
&lt;p&gt;The second Raspberry Pi 2 has 4.4.13 -V7+ #888 kernel, last Codesys runtime 3.5.9.10. Same CODESYSControl.cfg file, same app. The Modbus RTU communication start, the slave answer and then stop to work. For test I tryed also a python library: minimalmodbus: same behavior. The communication start and then stop.&lt;/p&gt;
&lt;p&gt;Second your opinion, what is the problem with seriali port in the last Raspbian kernel? Is there addition configuration for serial port?&lt;br/&gt;
BR&lt;br/&gt;
Fabio&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>