binary data communication through SerialPort

mrdebug

QSerialPort is what you need. Have you got the dongle protocol?

mrjj

hi besides what @mrdebug ask, have you tested wtih
http://doc.qt.io/qt-5/qtserialport-terminal-example.html
Its available directly in Creator and good for testing.

Sen Li

Hi @mrdebug @mrjj ,

That Terminal example is exactly what I have tried, and then I got the conclusion that QSerialPort Class cannot talk to it; I assume that is because of the failure of binary communication, however not sure about it.

All I know is, serialRead() was never activated even though serialWrite() has been gone through again and again.

Here is cited by Cypress Forum about CY5670 dongle communication:
"Since the communication uses binary codes Putty is propably not the right tool. Maybe use RealTerm, IIRC it has a mode the send and receive binary data. And I think you need to send the correct data to the dongle to answer. Maybe there is some command sequence to get a version number?"

It is sure that Putty could not talk to the dongle, while QSerialPort is similar to Putty.

Could anyone help me find a solution to talk to the CY5670 dongle?

Thank you!

koahnig

Every comms in serial is basically binary. It will not know a difference.
In most cases it is a baud rate respectively other settings issue. I guess that is also the issue with Putty.
Do you have the correct baud rate, data and stop bits and otzher flags?

mrjj

Hi
Im not sure what you mean by binary communication.
But QSerialPort can handle all that a com port can send.

When data comes in Terminal Example
Its read into a byte array which can handle binary just fine.
But the PutData calls
insertPlainText(QString(data));

And if its not printable as text, it might become nothing. (shows nothing)

So first check is to see if readData() is called.

If dongle has protocol, it might expect you to send something to it before it
sends anything.

void MainWindow::readData()
{
QByteArray data = serial->readAll();
console->putData(data);
qDebug() << "Its alive"; /// to test its called
}

Sen Li

@koahnig said:

Do you have the correct baud rate, data and stop bits and otzher flags?

Yes, I am sure those are correct.

The dongle is controlled by command packets. And any wrong command packets should active a error response, which I never received; the serialRead() was never called.

mrjj

well I would try with
http://realterm.sourceforge.net/ then and see if it even works at all.

mrdebug

Have you tried the QThread approach instead of events?
Please, download this
http://kde-apps.org/content/show.php/QtComPort?content=142378
and have a look at the file qthcomport.cpp
I know everybody don't like the QThread approach instead of events but in a difficoult situation I think the QThread approach is better. You can manage timemouts an polling.
Have you got the dongle serial protocol?
Every serial device has a protocol. For example if you send at a modem at&v you will have the current modem configuration.
Often the serial devices have a command to know the firmware version. This is the first command to implement. Normally there are a byte to begin, end and control.
Have you found the serial protocol in the sdk?

SGaist

Hi,

Maybe a silly question but are you sure this dongle can be used like a serial port ? The description says BLE to USB bridge.

mrdebug

I think the same thing. I normally use ble with bluez ( the Debian bluetooth stack) and not the usb dongle directly. Maybe his usb dongle has the bluetooth stack embedded.

Sen Li

Hi @mrjj @mrdebug ,

Thank you guys for helping me.

I finally got a response after sending a command packet to the dongle through a serial port.

So happy about it!

mrjj

@Sen-Li
congratulation!

SGaist

Nice, what was the problem ?

On a side note, you don't need to modify your thread title anymore, just use the "Topic Tool" button to mark the thread as solved :)

Sen Li

That CY5670 BLE dongle discards any commands without a header, which means I need to add a header to my command packet to talk to the dongle, otherwise nothing will happen.

SGaist

Thanks for sharing your findings :)