serial-port

问题 I have a FTDI connected to my PC and the FTDI is connected to an Intel Edison Arduino breakout board 0RX and 1TX pins. Serial pin hookup: Edison TX ------> FTDI RX Edison RX ------> FTDI TX To edit the Intel Edisons GPIO I followed the correct answer in the first post: https://communities.intel.com/message/265411#265411 To view my GPIO configurations I executed: cat /sys/kernel/debug/gpio Which then echoed out: Nodejs code: var SerialPort = require("serialport").SerialPort; var port = "/dev

问题 I'm having some issues with pyserial and windows (on linux it works fine with the same code); I seem to be writing erroneous bytes. The code even works fine on the same machine inside a debian VM, So Im pretty sure its a software thing. I'm using Python 2.7.6 32bit, pyserial 2.7 but have tried others (2.5 and 2.4) all exibit the same errors. Interestingly enough, the errors are much less frequent when the baudrate is increased to 115200. This is the relavant bit of my code: ser = serial

问题 I'm trying to set up a serial connection with a device which runs on a 1996 processor. This means that it can take several second for the data to be transmitted back to me. I know that the readyRead signal is generated every time new data is available, but my question is how long is generated for. Also is their a way that I can test for the ready read being low because if it stops being emitted when their is no longer any data left to read in, that would be really helpful. do{ ui->label_5-

问题 I am using two libraries to connect with a port, and two of them uses different styles in writing these commands. I want to understand the difference because I want to use the second one, but it results in port becoming unresponsive after some time, I wonder if it causes a kind of overloading. Here are the methods. Method 1: if self.port: self.port.flushOutput() self.port.flushInput() for c in cmd: self.port.write(c) self.port.write("\r\n") Method 2: if self.port: cmd += b"\r\n" self.port

问题 I've a sample pascal program, provided in a technical handbook of coin counter S350/360 machine, that enables communication between the machine and a computer using RS232C cable. I've came up with the following equivalent C# code and for some reason only the procedures that only need to write data to the serial port are executing and working successfully. I can only write data to the port but cannot read any data from it. I checked this using a Serial Sniffer and it turns out it only sniffs

问题 I have been trying to use serial communication with my Arduino Uno and have used the library jSSC-2.6.0. I am using a SeriaPortEvent listener to receive bytes from the Serial Port (Arduino) and store them in a linked list. public synchronized void serialEvent(SerialPortEvent serialPortEvent) { if (serialPortEvent.isRXCHAR()) { // if we receive data if (serialPortEvent.getEventValue() > 0) { // if there is some existent data try { byte[] bytes = this.serialPort.readBytes(); // reading the

问题 I am making a simple C program to get data serially from a serial device. The data is in hex format. Before writing the code I checked it in cutecom and I was receiving 25 54 00 1e which is the correct and exact value. But when I write the code then I receive this BFE50A14 which is wrong data. I dont know where I am making a mistake, please help. Thanks.! CODE: #include <stdio.h> #include <stdlib.h> #include <errno.h> #include <termios.h> #include <unistd.h> #include <fcntl.h> #include

问题 CustomSerialDeviceAccess is a sample on Microsoft's GitHub and it's for UWP to read/write SerialPort. The problem is that the sample can open devices on Win10 but get "DeniedByUser" on Windows Server 2019 & Windows Server 2016. I try to find some different things about Registry and Group Policy but get nothing. Can you give me some suggestions? Thx! 回答1: I got the way to fix the problem. Use MDM/GP to set the trusted devices policy to ForceAllow. For GP example, gpedit.msc -> Administrative

问题 I am performing an app with QT for communicate my PC with an 8 bits microcontroller through rs-232. I am using the QtSerialPort library and the communication is working fine, but each time I write something from the PC to the micro and I receive the response, I have to close and open the serial port or I can't continue communicating.. My configuration is: 10500 bps, 8 bits, 1 stop, no parity, no flow control. The code used for the configuration and the lecture/writting of the port is the next

问题 I'm now working on a project which uses libserial for serial port communication under Ubuntu. we modified the libserial source code to allow MARK/SPACE parity. but when doing data receiving test, sometimes (about 5% chance) the incoming data sequence is wrong. The first byte can jump to the middle of the incoming buffer or even to the end. The problem is inside the original SerialPort::SerialPortImpl::HandlePosixSignal( int singnalNumber) f unction, when the error happens it can not read some