CodePudding user response:
Were not RS485 serial port more than one serial portCodePudding user response:
A 485 corresponds to a QSerialPort object it is better to read and write multithreaded wayCodePudding user response:

CodePudding user response:
If directly set up more than one thread to create a more QSerialPort object, operate eg: SerialThread: : SerialThread1 (QString portName, BaudRateType baud, DataBitsType databits, ParityType parity, StopBitsType stopbits, FlowType flow, long timeout) {struct PortSettings ttySetting;//s3c2440 - {BAUD115200 DATA_8, PAR_NONE, STOP_1, FLOW_OFF, 500}; MyCom1=new Posix_QextSerialPort (portName, ttySetting QextSerialBase: : Polling); MyCom1 - & gt; Open (QIODevice: : ReadWrite);//serial myCom1 opened for both reading and writing - & gt; SetBaudRate (baud); MyCom1 - & gt; SetDataBits (databits); MyCom1 - & gt; SetParity (parity); MyCom1 - & gt; SetStopBits (stopbits); MyCom1 - & gt; SetFlowControl (flow); MyCom1 - & gt; SetTimeout (timeout); It is ok to}CodePudding user response:
Or make uncertain a serial port receives more data programming, we hope you give some ideasCodePudding user response:
The building Lord have done yet?CodePudding user response:
Object-oriented programming, make multiple objects don't have to do is bai