开云体育

There was a cheap Chinese dual band mobile on the market a couple years ago that used an Android phone and Bluetooth for the control head. I would post a link if my memory would serve me. The

Here it is, you can still get one! https://www.amazon.com/VR-N7500-Headless-Transceiver-Bluetooth-Programming/dp/B084D3V4MJ

Well, I'm the list owner and I have no objections. It's been a pretty quiet list for many years. If anyone else has any issues let us know. 73's Skip <kb9bpf@...> wrote:

I would have no problem doing the radio side of Bluetooth, but I'm not a phone app developer. If there's an app developer that's interested it might be doable. I even have a cheapish Chinese Android

LOL yea the Uniden guy is me. The housings are now PETG and have held up fine in 100+ temps in direct Kansas sun on a dash board.

Excellent. Thanks!

@ 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

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.

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

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

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.

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

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

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

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

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

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

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

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

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