Vintage Synth Repair

Hi Fran,

Thank you for your posting and help.

I have tried what you suggested and found the midi in/out handshake seems to be working alright. Could be I'm trying the wrong OS as I've heard these have to be loaded in order although I don't know the one in flash mem.

Here are the results:

Pressing "Test MIDI Loopback" on Updater program:

Unit showed: "Bad Sysx Msg"

Computer Updater window showed: "The selected MIDI ports are functioning properly"

Updater program window showed:

"Testing MIDI ports via external loop..."

MIDI Out SysEx:

F0 00 00 10 00 50 F7

"Testing MIDI ports via external loop..."

MIDI In:

F0 00 00 10 00 50 F7

Then I tried:

Message in Updater Program window after trying to transfer OS update:

Disabling MIDI Merge...
MIDI Out SysEx:
F0 00 00 10 00 4B 08 00 00 F7

Flushing target's input queue...
MIDI Out Realtime:
F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8 F8

Requesting software version from target...
MIDI Out SysEx:
F0 00 00 10 00 4B 28 F7

Requesting software version from target...
MIDI In:
F0 00 00 10 00 4B 28 F7

Requesting software version from target...
MIDI In:
F0 00 00 10 00 4B 06 11 F7

Waiting for Utility data...
MIDI Out SysEx:
F0 00 00 10 00 4B 11 F7

Waiting for Utility data...
MIDI In:
F0 00 00 10 00 4B 11 F7

Waiting for Utility data...
MIDI In:
F0 00 00 10 00 4B 06 11 F7

I will try your other suggestions/contacts later, probably next week.

In the mean time thanks again for your response & happy weekend!

eons

Hi Eons,

Did you try the diagnostics in Digitech's updater program? The diags will show all midi messages to and from the unit. You can activate the diags by double clicking anywhere there isn't a button in the updater program. There will be a midi loopback test and a window that opens showing the data sent and received. Make sure you are using 2 midi cables which it sounds like you already have done.

The unit is waiting for data so it seems that the flash program is still intact. I'm not sure about the leg lifting deal. Digitech support is usually very helpful. I know on some of these once the update is corrupted the unit is trashed unless the factory reloads it. I'm not sure about the Digitech units. I've encountered this with Korg and Novation units.

If the list is bothered by the OT you can email me at narfman96 at yahoo dot com for more help. Also there is a RP Yahoo group or several you can ask for more specific info. On google I also found a dude from Australia that mentions upgrading these.

Good luck, Fran

--- In vintagesynthrepair@yahoogroups.com, "eons" wrote:
>
> Hi,
>
> Ok.. sorry, I know this is synth group but I need help and unit it old anyway.
> I have this RP20 guitar processor client tried to update OS but got stuck in the way. I asked if power was turned off or there was a cut in the cabling during his update and he said no.
>
> It powered up with all buttons lighted and black square characters shown at top line on LCD; unit looked 'locked'.
> I removed the internal batt. and placed it back in and progressed slightly with display showing: "waiting for data".
>
> I tried to load OS ver 1.05 (I have 1.10 and 1.15 for later) (through Midi In & Out) with DigiTech's update program but got message: "unknown procedure" on unit's display and "An incorrect SysEx Procedure ID was received" on computer.
>
> Client contacted manufacturers he said and they quoted to "before taking off the eeprom, lift pin 2 of U48" and "you will have to re-solder the pin after the update is complete". I have done this with no good results as unit displayed "unknown procedure".
>
> Does anyone in the group possibly have service manual and/or other OS updates for this thing please?
> Unfortunately the eeprom looks surface-mounted with no socket and could be this has crashed/went faulty.
>
> Thank you for any possible help you might suggest.
>
> eons
>