I think \n (ASCII char 10 is new line feed and is different than \r (ASCII char 13) which is carriage return. It would be \r\n for both, or at least that was how I remember it from my days at staring at an HP serial protocol analyzer.
From:[email protected] <[email protected]> On Behalf Of Warren Merkel Sent: Thursday, August 12, 2021 8:38 PM To:[email protected] Subject: Re: [nodered-hamradio]Kenwood CAT to relay example.json..... PROGRESS
?
\n ( new line) means look for the carriage return and line feed characters, together. .? ?Char(13) Char(10)
?
If your string only has one or the other,.it won't match.
?
On Thu, Aug 12, 2021, 8:29 PM Dave / NR1DX <manuals@...> wrote:
A break through of sorts late this afternoon
In the port setup is a group of boxes under INPUT. The second row down is a line? SPLIT INPUT with two boxes which default to [On the character]and [\n]
Changing the [\n] to "A"? ( one of the characters in the serial string we are looking for) allowed information to start coming out of the serial port into the rest of the flow.
??I am sure that "A" is not likely correct it certainly screws up the serial message parsing for the later logic to act on But it points as to where to start looking further ....... Is "\n" supposed to be a number or \(number)? maybe?
Can anyone point me to a complete set of DOCUMENTATION? that defines what all the choices under INPUT are and how to choose appropriately?
Dave WO2X and Alan thanks again for all your suggestions earlier. Dave a video call tomorrow at this point is not necessary. Pointers to real documentation if it exists appreciated though. Until that surfaces I will likely play the "monkey at the typewriter" till I figure out what goes in all those boxes and why.
Tomorrow I will point the output of the Serial node to Msg-Payload in DEBUG mode and see what the data string really looks like
Dave NR1DX
On 8/12/2021 1:00 PM, Dave / NR1DX wrote: > Dave & Alan > > OK Dave's cleanup and reinstall routine was 98% accurate and I was > able to fill in the holes. I now have the all the other USB COM ports > cleaned out and the FTDI port listed and connected... That is the good > news ...the bad news is still no data coming out of the SERAIL-IN > node. I bypassed all the other stuff and routed the output of the > SERIAL-IN? directly MSG_payload to see what if anything we were > getting...nothing. > > My thinking is correct (verify) that if the SERIAL NODE is now > "connected", and my serial dongle RXD node is blinking when I change > FREQ we should see some kind of string coming out of that node ( ASCII > I suspect) > > I will continue to plug away at this but if I don't solve it today > tomorrow at your convenience is fine > > Dave > NR1DX > > On 8/12/2021 12:08 PM, David De Coons wo2x wrote: >> To delete all the old references to serial ports in the serial node, >> double click the serial node. Click the pencil to edit. Upper left of >> that window select delete. >> >> Use pull down to select next serial device. Use pencil to edit. >> Delete. Repeat for any remaining serial cables. >> >> Then it will prompt to create new. When you were in the /dev/serial >> folder, highlight the serial cable in the serial by ID folder. Right >> click and select copy path. >> >> Back in Node Red when you open the serial node and create new. Paste >> the path you copied for the usb to serial adapter. Set baud rate. Set >> timeout to something like 500 ms. It defaults to 10000 ms. This is >> important! >> >> Sorry if I am not 100% accurate with description. Doing it from >> memory while out having lunch. >> >> Again let me know and I can help tomorrow. >> >> Dave wo2x >> >> Sent from my waxed string and tin cans. >> >>> On Aug 12, 2021, at 11:44 AM, Alan Blind, WA9WUD >>> <a.alan.blind@...> wrote: >>> >> >> >> >> >