Thank you for the example. I forgot to mention, that I use the SerialWrite function. I have succeeded to use the serial port commands for a USB connected Arduino board.
Thank you for letting me know you have made some progress and are using the SerialWrite function.
I get back with the question if it is possible to send via SerialWrite function information formatted as bytes? I have the information in HN as numbers that represent bytes (0-255). At the moment I have formated each number in the array to have 3 digits.
The strings in HN are intended to be useable with different languages and character sets like Cyrillic - therefore each character in a string actually uses 2 bytes.
Note, there are byte specific functions such as ChrBFN, LenBFN etc - perhaps you should be using these when building your byte-strings so as not to send extra information to the Arduino.
There is the possibility to convert the message with Arduino, but there is a mis-match between the sent message and the return message. I noticed there is a delay of 3 messages (I get the answer from the Arduino board for the message sent 3 times earlier). I can't tell if the delay is from the HN software or from the Arduino, but with the Arduino serila monitor software it works well.
Here is the code for the communication:
SerialWrite(1,info)
SerialTXWait(1)
Append SerialReadAllFN(1) onto field 14
Its been perhaps 10 years since I played around with this but do recall having similar problems with the serial NMEA messages coming from a GPS system. Once I understood the format then the thing worked. Not sure, but perhaps instead of using the SerialReadAllFN function I actually used the SerialReadBytesFN to read an expected number of bytes - perhaps the NMEA sentences are much simpler than an Arduino.
Have you had any luck getting the Arduino to slowly and repeatedly send out a simple string of bytes so HN can echo them to a field - it might help show up the mismatch.
