Batboard

Anyone done this and had it worked? The normal HEX strings that work in XTS Astro CPS don't work in this version and don't appear in the .exe either... Can anyone shed some light? Would like to get my R split up a few Mhz.

Cheers,
AJ

I'm pretty sure you cant hack the band limits on a waris portable...

Something about the bandsplit info is stored in the radio and not the CPS.

exactly, this has been covered on here many many times, the band information is stored in the firmware of the radio, not the cps so you can't take them out of band.

Read through this thread:

http://batboard.batlabs.com/viewtopic.php?t=3747

Covers using the FPP capabilty of a HT1550XLS to nudge out of band.

Yes, in WARIS series radios the bansplit info is stored in radio, not in CPS - but not in the firmware (FlashROM) - it is a part of codeplug
(i.e stored in EEPROM) and therefore can be easily changed. The only problem is to find a position and format in which bandsplit data is presented - these things are absolutely different depending on radio family: Select V, MDC, MPT, SmartZone etc.

Bandsplit has nothing to do with firmware.. but HLA will never understand that... even after multiple attempts.

tpg

The Pager Geek wrote:Bandsplit has nothing to do with firmware.. but HLA will never understand that... even after multiple attempts.

tpg

Is it the Cowtheif syndrome?

Yup

Hello.

The FPP Spectra can not be taken out of band.
The bandsplits are stored in the SP firmware in the railroad clean cab chassis.
I believe the same is true for the FPP ASTRO HT1550.

Alright guys... back on topic.

Fellow experimenters,

Something new has surfaced on this topic.

Recall that at least one other person, while hex-editing 'ProRadio.exe,' found references to a 'Debug' mode, and to 'Blast Codeplug' options. There was, at the time, much speculation about how to get the CPS into this mode.

I tried the obvious today -- opening a command line, and running ProRadio.exe /debug -- and darned if it didn't bring up a window that I'd never seen before (and, to be honest, wasn't quite sure how to work with). This was in version R06.08.00.

I don't have the time to follow up on it at the moment, but I would be curious to know what others may learn. Perhaps other versions will exhibit the same behavior?

Happy tweaking.

kc7gr wrote:Fellow experimenters,

Something new has surfaced on this topic.

Recall that at least one other person, while hex-editing 'ProRadio.exe,' found references to a 'Debug' mode, and to 'Blast Codeplug' options. There was, at the time, much speculation about how to get the CPS into this mode.

I tried the obvious today -- opening a command line, and running ProRadio.exe /debug -- and darned if it didn't bring up a window that I'd never seen before (and, to be honest, wasn't quite sure how to work with). This was in version R06.08.00.

I don't have the time to follow up on it at the moment, but I would be curious to know what others may learn. Perhaps other versions will exhibit the same behavior?

Happy tweaking.

Any luck getting it to generate a codeplug. I haven't been able to get it to work, keep getting error.

Seems that by copying all the applicable DLL files from \Program Files\Common Files\Motorola\RDK\ into the Pro Series CPS directory, executing "ProRadio.exe /" or "ProRadio.exe -" brings up some funky window that just has ProRadio listed a bunch of times, double-clicking one of them brings up a window asking for a Version String and Model Number, and some funky registry type stuff.

This is on R06.10.02