Issue appears almost solved....
Thanks for the input!
Update: A couple issues solved- main one being that the order that power is applied to which device appears to have a significant effect on the conversion chip performance(I will buy some with a different breakout board). Now I am seeing +8/-8V on the RS-232 when the transmit pin is grounded.
This makes me believe that the final issue is that whatever is being transmitted, is not understood by the radio head. In other words,
I think the problem is with the line of code below (which may contain some rookie mistakes)
RS232serial.write("$PMMRC00G4N29\r\n");
I tried RS232serial.print, also adding ,DEC, HEX, BIN, OCT. Also tried declaring it as a byte, String, char, and placing the variable in the command instead.
<CR> in string is wrong, should be \r\n
Or could remove it and do this before your write delay:
serial.write(13);
serial.write(10);
chksum appears to be incorrect.
Thanks- I corrected <cr>
FWIW this code also sends *something* to the RS232 (according to the oscilloscope), but the expected frequency change is not occuring:
(RS232serial.write(uplink),13);delay(100);
Bob's right of course. I'd also do readcommnetwork() differently - with a while loop, since you might not get all the data in one read.
Thanks, I noted that rather than spitting out scrambled characters on Serial1 while transmitting on Serial2, the "status messages" seem to get buffered and as soon as I am done with the transmit, the missing messages show up without any scrambling almost every time now.