UART example acting weird

RE: UART example acting weird

molviken — Tue, 21 Apr 2020 16:32:29 GMT

Okay, good to know! Thank you very much for the help! Now remains to merge with mqtt, wish me luck.

RE: UART example acting weird

Didrik Rokhaug — Tue, 21 Apr 2020 13:12:23 GMT

A quick chat with one of our developers revealed the issue.

The Link Monitor was made to communicate with the modem, so it expects the communication to follow a certain protocol. I.e. it expects any input to be answered with a properly formatted "OK" or "ERROR" line.

The application can output whatever it wants, and that output will appear as blue text in the Link Monitor.

However, it can only send "AT commands"*, which will appear as yellow text.

The properly formatted responses will be colored white.

As a quick test, I changed the output in the callback to "OK\r\n", at which point the Link Monitor worked as expected**.

* Technically, you can send whatever you want, as long as you get a response similar to what an AT command would get.

** The application will print one "OK\r\n" per character. The first one will be taken as the response (white), while the rest will be takes as generic output from the application.

RE: UART example acting weird

molviken — Tue, 21 Apr 2020 12:40:51 GMT

That worked like a charm. Guess ill continue to use RealTerm/Termite instead of link monitor from now on.

RE: UART example acting weird

Didrik Rokhaug — Tue, 21 Apr 2020 12:07:29 GMT

Hi.

Could you try to use a different serial terminal than the Link Monitor?

When I use Termite, everything works as expected, but when I use the Link Monitor, it varies how much is printed out. Sometimes, I only get "UART loopback star1", other times I get all expected output, though I am not able to send any input.

I'll look into why the Link Monitor is not working as expected.

Best regards,

Didrik