On Sun, Aug 7, 2022 at 06:21 PM, Skip Hansen wrote:
Yea, but then you have to conform to the SB9600 protocol, yuck! For
computer control you'd also need a SB9600 "gateway" or a rib and a
serial port, again yuck.
@ Skip,
True. Hand assembling a few basic commands like volume and mode select inc/dec, scan on/off etc might not be a major undertaking. I'd like to see a macro of commands that get you control of the squelch parameters too.
Although forcing a mode increment cmd to the uC might be needed to force an EEPROM read to create a scan function that can be controlled in a PH II design.
Doesnt the Xcat do something similar on one of the CH lines to X's uC to implement scan?
Since the X9000 OEM head is intelligent too, mode information is a function of the radio commanding the head to "display the data you have stored for mode nn. Building that array could get complex.
Likely OTF edits could get cumbersome too.
Using/hijacking the SB9600 protocol to program the EEPROM via the host uC is unlikely. I doubt Motorola supports single byte writes in the FW, which is necessary for the goal.
?
That's when we will need that wedge into the FW loop and a single byte write subroutine written......got 'er done yet?
With a lot of research and dedication, some form of SB9600 based UI isnt unrealistic, but is probably Ph III or beyond.
