https://forge.codesys.com/forge/talk/Runtime/thread/87506d2b8e/2024-01-06T19:46:20.282000ZRecent posts to How to connect serial devices ?2024-01-06T19:46:20.282000Z2024-01-06T19:46:20.282000Zusacodesysuserhttps://forge.codesys.com/u/usacodesysuser/https://forge.codesys.com5eb58396b1bddfb7c48a19cdb1083a6fb713ed3d

<div class="markdown_content"><p><a class="user-mention" href="/u/eschwellinger/">@eschwellinger</a> do you have any examples of using a USB barcode scanner? I have read through the forums here and I am unable to find how to get the barcode data to populate in a text field without having to first click into the text field to activate it. Is there a library that allows you to access the barcode data? I am really new to this in general any help is greatly appreciated, hopefully you have a pretty clear example</p></div>

2023-03-23T13:01:27.672000Z2023-03-23T13:01:27.672000Zr-kebhttps://forge.codesys.com/u/r-keb/https://forge.codesys.com0e59301e5e46bedf91a5e6c91cfbd54296386b63

<div class="markdown_content"><p>Hello,</p> <p>I'm facing a particularly odd issue, which is when I try to write the data to the rs485 interface, the start and end voltages of the packet are not sent through the A wire. I recorded this issue while comparing the sent data using an oscilloscope. When using the USB-to-rs485 interfaces and realterm terminal program, all is well and the data is then read by the slave and returns the requested information. But when using the rs485 on the PiXtend V2-L, there is no response.</p> <p>Does anybody have an idea of what could be the issue here? Is it the PiXtend, rpi, CAA SerialCom library (also tried with SysCom library and the result was the same) or perhaps something else? I've checked that the parameters match multiple times.</p> <p>Regards,<br/> Rok</p></div>

2023-03-23T13:01:25.363000Z2023-03-23T13:01:25.363000Zr-kebhttps://forge.codesys.com/u/r-keb/https://forge.codesys.comaac583f22fe60fb717f8f7b45c122fc305d04ea5

<div class="markdown_content"><p>Hello,</p> <p>I'm facing a particularly odd issue, which is when I try to write the data to the rs485 interface, the start and end voltages of the packet are not sent through the A wire. I recorded this issue while comparing the sent data using an oscilloscope. When using the USB-to-rs485 interfaces and realterm terminal program, all is well and the data is then read by the slave and returns the requested information. But when using the rs485 on the PiXtend V2-L, there is no response.</p> <p>Does anybody have an idea of what could be the issue here? Is it the PiXtend, rpi, CAA SerialCom library (also tried with SysCom library and the result was the same) or perhaps something else? I've checked that the parameters match multiple times.</p> <p>Regards,<br/> Rok</p></div>

2023-01-26T16:27:31.969000Z2023-01-26T16:27:31.969000Zoleanderkirohttps://forge.codesys.com/u/oleanderkiro/https://forge.codesys.com59ff47bb7c80537a7489e328430d84152f236403

<div class="markdown_content"><p>I receive:"<span>[ 0.000000]</span> Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835 .enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=800 bcm2708_f b.fbheight=600 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x 40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=eb299098-02 rootfstype =ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles<br/> <span>[ 0.000475]</span> printk: console <span>[tty1]</span> enabled<br/> <span>[ 2.931350]</span> 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2<br/> <span>[ 2.934089]</span> printk: console <span>[ttyS0]</span> disabled<br/> <span>[ 2.934217]</span> 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 86, base_baud = 50000000) is a 16550<br/> <span>[ 2.934482]</span> printk: console <span>[ttyS0]</span> enabled<br/> <span>[ 10.430930]</span> systemd<a class="alink" href="/forge/talk-ru/1/">[1]</a>: Created slice system-getty.slice.<br/> <span>[ 10.434094]</span> systemd<a class="alink" href="/forge/talk-ru/1/">[1]</a>: Created slice system-serial\x2dgetty.slice."</p> <p>but<br/> /dev $ ls tty*<br/> tty tty10 tty13 tty16 tty19 tty21 tty24 tty27 tty3 tty32 tty35 tty38 tty40 tty43 tty46 tty49 tty51 tty54 tty57 tty6 tty62 tty8 ttyprintk<br/> tty0 tty11 tty14 tty17 tty2 tty22 tty25 tty28 tty30 tty33 tty36 tty39 tty41 tty44 tty47 tty5 tty52 tty55 tty58 tty60 tty63 tty9 ttyS0<br/> tty1 tty12 tty15 tty18 tty20 tty23 tty26 tty29 tty31 tty34 tty37 tty4 tty42 tty45 tty48 tty50 tty53 tty56 tty59 tty61 tty7 ttyAMA0<br/> Is the interface ttyAMA0 ?</p></div>

2023-01-25T18:21:23.358000Z2023-01-25T18:21:23.358000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comcee5d0a8eab7552855e3c1be666c46b79b5c0b53

<div class="markdown_content"><p>dmesg | grep -i tty</p></div>

2023-01-24T16:13:08.572000Z2023-01-24T16:13:08.572000Zoleanderkirohttps://forge.codesys.com/u/oleanderkiro/https://forge.codesys.com6c15689f73d0806d7a145ad397673cb78dff6cd5

<div class="markdown_content"><p>I receive a long list, what shell I receive ?<br/> With "lsusb" I receive: "Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC"<br/> I want to acces on this port. With lsusb -vs I receive :<br/> "idVendor 0x0403 Future Technology Devices International, Ltd<br/> idProduct 0x6001 FT232 Serial (UART) IC<br/> bcdDevice 6.00<br/> iManufacturer 1 FTDI<br/> iProduct 2 FT232R USB UART<br/> iSerial 3 AB0JV1PJ"<br/> How can I reach a success ?</p></div>

2023-01-21T05:49:38.934000Z2023-01-21T05:49:38.934000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.coma784d4b7e40c861e1ce0bf84ba6e7405698ed9fc

<div class="markdown_content"><p>check with 'dmesg'</p></div>

2023-01-20T16:46:53.566000Z2023-01-20T16:46:53.566000Zoleanderkirohttps://forge.codesys.com/u/oleanderkiro/https://forge.codesys.comef5b7cb28aed00a805bfeb6dbe6b55cbd011e5cf

<div class="markdown_content"><p>I want to control a model railway via usb (NEM451).<br/> So I wanted to use your program. I can connect the interface directly to 1 of the 4 usb-ports.<br/> If I try to search the USB-Port I receive:<br/> Bus 001 Device 004: ID 28a0:1185 USB OPTICAL MOUSE<br/> Bus 001 Device 005: ID 1c4f:0016 SiGma Micro USB Keyboard<br/> Bus 001 Device 006: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)<br/> Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub<br/> Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub<br/> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br/> but not a tty-port ?</p></div>

2022-06-24T07:26:45.096000Z2022-06-24T07:26:45.096000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comed240c400c0823a62938e8dcedff4ae59e6aad89

<div class="markdown_content"><p>Is it a RS485 adapter - if so, keep in mind that CODESYS do not control the send direction -<br/> this must be supported by the hardware (your adapter).<br/> If you are using RS232 - no clue whats going wrong.</p></div>

2022-06-23T19:47:37.335000Z2022-06-23T19:47:37.335000Zman2002https://forge.codesys.com/u/man2002/https://forge.codesys.com30296d52f3a3c345d397c7c10345fad32e892cab

<div class="markdown_content"><p>Hi Edwin, </p> <p>I am having the same problem as Nosi described in an earlier post. I constantly get zeros in the read buffer when attempting to read from the COM port after making the changes below to the /etc/CODESYSControl_User.cfg file</p> <ul> <li><span>[SysCom]</span><br/> Linux.Devicefile.1=/dev/ttyACM0 - this is communication port for the motorcontroller (Octopus Pro controller).</li> </ul> <p>I am able to successfully write from Codesys (V3.5 SP17 Patch 3) to the motor controller, but reading from MC is proving to be a challenge. I can read data from the COM port in Linux when I apply the commands below but not in Codesys. </p> <ul> <li>stty -F /dev/ttyACM0 115200</li> <li>stty -F /dev/ttyACM0 raw </li> <li>cat /dev/ttyACM0</li> </ul> <p>Please help.</p> <p>Thanks.</p></div>