开云体育

Hello Skip and all - my 1st post - I see 3 recent requests and there my be 4 boards available - so perhaps one is available - please put me on the list. Thanks. George. KB0CE

I would prefer seeing the discussion. Joe M.

I will have to look at the data again but if I recall correctly it's part of the 4 but data word I believe. I recall doing a (if frequency is between.... Then bit high or low) type thing. It was then

What did you do about the VCO V-bits? De

I just found this: https://wiki.w9cr.net/images/6/61/SB9600_Serial_Bus_Protocol_Manual_by_Motorola.pdf are you guy's aware of it?? I remember searching and searching for SB9600 "back in the day" and

Let's see... 2K x 8 requires 19 GPIO lines (11 address + 8 data). 8K x 8 requires 21. The ESP32-S3 (latest chip) has 45. That's the raw chip, the modules use some of the GPIO internally and don't

Emulation. It's the only viable option. Otherwise, you have to forego all the CTCSS/DCS, and whatever I/O and options the radio is capable of and reproduce them with other devices since the radio's uP

Casey, are you on the "emulate the exisiting EEPROM" path or the "hijack the synth registers and latches" path?

As a die hard analog dinosaur I concur. These beasts were built to survive, and have, I see you've found the RSS that allowed 32 MPL. I think that was the 255 mode version. As the fuzzy clears a bit

Thanks. Good to know I was on the right track. As for my synthesizer driver project I used an arduino to drive what I recall was a 256x64 OLED display via SPI and used the keypad matrix from a Micom

Yup been there done that, the data field sort of bleeds down the screen: *"Also, the PC's screen goes wonky* ( that's a technical term ) when you enter MPL data > than about 20. Keep up with where

I meant the addy buss line in the radio. If I understand what you did you were "serving" specific EEPROM data as requested the uC via the PIC's GPIO lines? Still had to know what addy the uC wanted

BTW the EEPROM is connected to the F8's GPIO ports, not its memory bus. Skip <skip@...> wrote:

You have it right Casey. The Xcat emulates the 2K x 8 EEPROM. The same concept could be used for the X9000, but of course the EEPROM contents should have to be fully understood or at least the

I remember asking Skip about that, way back when..... he will be back and fill us in I sure. As I recall he saqid that the timing was? a challenge. I think he uses the EEPROM in the 16F877? ( I dont

My thought is to take out the EEPROM entirely and present a dynamically changing equivalent of it to the uP in sync with its EEPROM read requests. I believe this is what the XCAT does.

To emulate an RSS write, or read for that matter, one would have to "snoop" the SB9600 stream, between the RSS in numerous configurations and the radio (for differentail analysis) to decipher what it

IIRC the radio may write certain things like last phone number dialed into the EEPROM during operation. De

Well wasnt that special....lol Skip did we exceed our Io bandwidth break the io server? No wait! Let me check NTD news. It was probably the CCP stealing all this high tech IP we are discussing.

@ RFI-EMI-GUY 16 MPL limit....no, but I'll need to qualify that. First, as has been mentioned by others, I too have an acute case of CRS as in "Why did I walk in this room, or What did I have for