Frequently Asked Questions Digitech RP2000 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- The Digitech RP2000 is a very cool Guitar effects processor. I'm going to attempt to answer the most commonly asked questions I hear and that are asked on the RP mailing list. Contributions from: Tony Kennedy Ron Baker Carlos Becker Terry Bush Stan Borek Ivor Williams -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- And on with the show... Q. Is there a Mailing List? A. Yes. There's a general RP list. Here are some web addresses: Main Digitech Page - www.digitech.com RP Mailing List - http://www.digitech.com/users.htm RP2kEdit List - http://groups.yahoo.com/group/RP2kEdit Q. Is there a website with patches? A. Yes. www.makeascene.com/rp2000 Q. Is there a patch editor? A. Yes. There are two. Ripper2000 is at http://rushtabs.tripod.com RP2kEdit is at http://groups.yahoo.com/group/rp2kedit/files/ You can also use: MIDI-OX a general MIDI SysEx program at http://www.midiox.com/index.htm Q. Is it possible to turn the drums (rhythm) off and on from one of the foot switches. A. Yes. 1.) select a user preset, 1 thru 64. 2.)push assign button by data wheel. 3.)push rhythm button three times till CNTFS= is flashing. (CNTFS= is abbreviation for control foot switch) 4.)rotate data wheel till RHYTHM is flashing alternately with the CNTFS=. (this assigns the control foot switch to the rythm funcion.) 5.)push the store button three times to save your change to the patch. Note: you can now switch the rhythm on/off with the control foot switch but you are stuck with whatever rhythm pattern and tempo you have set ie:if you have this rhythm switch on two or more patches you can't have two different types of rhythm patterns, one for each patch Q. How do I tell what version my RP is? A. On powerup, you see Ver 1.[x] displayed on the LED readout. Where x is the incremental version number. So if you see Ver 1.[4] you have version 1.4. Simple eh? Q. How do I get an upgrade? A. Ask Digitech! :) Go to: www.digitech.com/contact.htm In the spaces provided fill in, Name: Email address: Regular address: Choose product: RP2000 Choose subject: Technical assistance Then write message like: Hello, how can I obtain the upgrade eprom chip, part # 72-3065-04v1.30 ? If possible would you please send it to the above address. Thank you. Q. What upgrades are available and how do I install them? A. There have been upgrade chips for versions: 1.3 (can be user installed) 1.4 (requires the unit be sent back to the factory for pedal upgrade.) (From Terry) If you are doing an upgrade to version 1.3 : Changing the chip was fairly painless provided you do the following: 1.) Write down the user patches you wish to put back on the RP2K. 2.) Power down. 3.)Pull off data wheel knob. 4.) Remove allen head screws on top of unit. 5.) Lift face plate straight up for about an inch then rotate top towards you, turning it upside down. Be careful not to lay top on small optic light circuit board on bottom. 6.) Remove the 10 or so black phillips head screws on the back of the larger circuit board. 7.) Leaving top upside down, turn over large circuit board to find a rectangular chip with the numbers RP2000 U18 on it. (The other one is for drum tracks) and take note which way the new one should go in. (don't put it in upside down.) The chips have a small indent on one end for marking. 8.) using a small flat bladed screwdriver insert and gently pry up right then left sides of the chip till you have worked it out of the socket. (Easier than you might think) don't lever against any chips beside it. 9.) Insert upgrade chip in socket and firmly press into socket till it seats fully. 10.) Reverse procedure to reassemble, taking care to put the clear plastic fin under expression pedal, into the slot of the small optic light circuit board. (take some time and be careful here, it doesn't look super sturdy) 11.) After reassembly, hold down Rhythm button while you power up. The display will show "XXXXXX" 12.) Release Rhythm button and push FX button. Then calibrate expression pedal. Toe down - push lighted foot switch, Toe up - push lighted foot switch. 13.) You're done! Now put your user patches back where they were. Enjoy! (From Stan) Here are some remedies to installation installation hassles I went through and observations I made (Legal and Common-Sense Disclaimer: This worked for me---proceed at your own risk and expense. If you don't know how to pull, install and ground chips, please take your upgrade and RP2000 to a qualified tech): (1) Trying to find a hex tool for the face-plate fasteners may be very difficult. I could not match Brittish (somewhat less than 1/8 inch) or metric (somewhere between 2.5mm and 3mm) hex tools. My solution was to use a TX15 insert bit (tapered "asterisk"-shaped tip, cost = $2-$3) with a 1/4 inch socket and nut driver. The TX bit works fine but there is a warning---the TX15 insert bit worked great but a Torx15 socket was slighly too large! Go figure!. (2) Don't forget to remove the data wheel before you try to swing open the face plate! You can pull straight up to remove the knob from its stem. (3) Swing the face plate open---don't just lift it up and open. There are ribbon connectors between the face plate and the base of the unit. You don't want to stress these cables. Also, there is a somewhat delicate piece that hangs down from the bottom of the face plate and drops into an opening on a small circuit board. Right to left motions should be avoided. Be careful! (4) Don't completely reassemble your RP2000 after you install the new chip. Put a couple of screws in the circuit board that holds the chip and put the center fastener in the faceplate, in case your chip is not seated properly or you have to remove the chip. Try out the RP2000 before you batten down the hatches! (5) Don't touch anything but the utility button once the RP2000 powers up with the VER 1 30 operating system. I learned this the hard way! Just spinning the data wheel can cause a bizzare lockup condition that will not go away by turning the RP on/off or by attempting a factory reset after the lockup! You may not be even able to get to the factory reset quick enough after the lockup. If you do get this bizzare lockup, shut of the RP2000 and turn it back on while holding down the utility button. The display will read "TECH". Press the left arrow (FX Mode) button a number of times (each time you press the button a different system test will be performed)until you get the VER 1 30 message, then a patch name. At this point---GO DIRECTLY TO THE UTILITY MENU AND PERFORM THE FACTORY RESET! The factory reset procedure is in the RP2000 manual, near the end. If the lockup persists, see (6), below. (6) If the lockup persists beyond the TECH procedure above, remove the VER 130 chip and (gently!) ground the pins. Reinsert the chip and try again. Or, you can remove the backup battery for a few minutes. I can't explain the lockup I encountered but I can say that removing the chip and grounding the pins allowed me to get to the utility menu and perform a factory reset. After that, I was able to quickly restore my personalized presets via MIDI SysEx. (7) Don't forget to reset your global settings, pedal calibrations, V-switch sensitivity, etc., before you save your new VER 1_30 bulk dump. (8) Cakewalk users---make sure that you go to: Setttings - Type Filter... and set a checkmark for System Exclusive in the Global Settings area of the "Record These Types of Events" dialog box. If you do not have System exclusive checked, you will not be able to receive bulk or patch dumps from the RP2000. After your bulk dump, save individual patches that you have modified. The individual patches may be the only ones that are portable from upgrade to upgrade! A bulk dump from VER 1 00 may not work with VER 130, and vice versa! (Note: According to Digitech, a full bulk dump is NOT compatible across version) Individual patch dumps definitely do survive the VER 100 to VER 130 upgrade. It's more time consuming but only during the saving process. Cakewalk can dump all the individual patches back into the RP2000 with one click. Don't forget to save a bulk dump of your new VER 1 30 settings as insurance. When restoring my RP2000 via MIDI sysex, I send the bulk dump, then all of the individual patches. It has worked fine for me. Q. How do I reinitialize the RP2000? A. The re-initialization procedure will return everything (including user presets) back to the original factory settings. Hold in the RHYTHM button while turning the power ON. Hold the button until the display shows all X's. Finally, press the FX Mode button. Your RP2000 will briefly read 'RESET' and will then prompt you to re-calibrate the expression pedal. When the display reads 'TOE UP' rock the pedal all the back and press the #3 footswitch. When the display reads 'TOE DN' rock the pedal all the way forward and press the #2 footswitch. Your RP2000 is now reinitialized. Q. How do I scroll DOWN through the banks or programs? The bank button only goes up. A. Press and HOLD the bank button to scroll down. Press and RELEASE the bank button to scroll up. Q. How can volume discrepancies between red and green channel be alleviated? A. Adjust volume level for each program channel individually. Q. What do I need to hook my computer to the RP? A. The RP connects to a computer via the MIDI ports. You need to use BOTH the In and Out connections. MIDI is NOT bidirectional. There are several options: 1. If your soundcard has a joystick port, you can get a gameport->MIDI adapter. They are around $25. Most major music stores have them. I've seen them online at http://www.cablesnmor.com/midi-cable.html 2. A USB MIDI connector. This is an adapter that hooks to the USB port of your PC. MIDISport is a fairly inexpensive one. (~$100) 3. Some soundcards come with a MIDI interface built in. The SoundBlaster Live LiveDrive is one example. Q. What amp sounds best with the RP2000? A. Many prefer a very clean amp like a JC120, or a keyboard amp, or PA. Try them out and see what you like? Q. How do I use MIDI-OX to save/load sysex info? A. (from Ivor Williams) In MIDI-OX: - from the "Options" menu, ensure that "Pass SysEx" is ticked - from the "View" menu, select "SysEx ..." - this brings up a "SysEx View and Scratchpad" window - from "Sysex" menu, select "Receive Manual Dump ..." From the RP2000: - use the "Utility" button, etc, to initiate the dump - wait 'til the RP2000 indicates that it's done ("DMPING" no longer shows) In MIDI-OX: - press "OK" to acknowledge the number of bytes received - it should show 208 bytes for an RP2000 patch - from the "Display Window" menu, select "Save As ...", etc To restore patches to the RP2000, in MIDI-OX: - from the "Command Window", select "load File ...", etc - from the "Command Window", select "Send/Receive Sysex" - press "OK" to acknowledge the number of bytes received - it should show 10 bytes for an RP2000 patch upload Note: - the patch number is stored in the 208 bytes of patch data. If you saved it as patch number 1, it will be restored as patch number 1. You'll have to edit the patch data to store it as any other patch. - it doesn't matter which patch the RP2000 is displaying at the time the patch is restored - you can use the same procedure to perform a bulk dump/restore. But, it looks like the bulk sysex format is different after the chip upgrade, so you can't use it to make a backup prior to the upgrade. Perhaps someone who has performed the upgrade has some details on this. Q. What does the upgrade to 1.4 do? A. According to DigiTech, the 1.4 upgrade does mainly 2 things: adds a bit more gain to the Matchless model and fixes a problem with the V-Switch turning itself on and off . Fixing the V-Switch problem requires a new treadle assembly. Q. What are the Continuous Controller values for the RP? A. That's a VERY long answer. E-mail Tony (bonkrz@yahoo.com) for the list. Q. What's the System Exclusive layout? A. Another LONG answer. See the appendix at the end of this FAQ. Q. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Appendix. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 1. System Exclusive Layout. Here are the current sysx messages that are available in the RP2000 HEADER= F0h,00h,00h,10h, 00h (channel is always 0), 52h (RP2000 device Id), After the header will be a single byte procedure number. All data after the HEADER and procedure number is in split bytes unless otherwise noted. A split byte is when a single 8 bit number is split into two bytes, the first byte is set to one if bit 7 is a one, the second byte is the original byte's bits 6-0, eg. a byte of C5h would be split into the following two bytes: 01h,45h EOX= F7h One and only one response is transmitted from the RP2000 per sysx message received. If the host unit requests data then that data is transmitted back to it, if the host is sending data or requesting a command then the RP2000 will respond with this standard message: HEADER, RESPOND_TO_MESSAGE, procedure number that this message is responding to (not split byte), error number (not split byte), EOX Note: 0= no error, see the error messages down below If requesting data and there is an error with the requesting sysx message then the RESPOND_TO_MESSAGE sysx message will be sent instead of the expected data message. // Valid Sysx messages #define REQUEST_ONE_PROGRAM 0x001 RECEIVED MESSAGE HEADER, REQUEST_ONE_PROGRAM, bank (0=factory,1=user), program number, EOX RESPONSE HEADER, RECEIVE_ONE_PROGRAM, bank (0=factory,1=user), program number, program size (lsb), program size (msb), program data, EOX #define RECEIVE_ONE_PROGRAM 0x002 RECEIVED MESSAGE HEADER, RECEIVE_ONE_PROGRAM, bank (0=factory,1=user), program number, program size (lsb), program size (msb), program data, EOX RESPONSE see RESPOND_TO_MESSAGE #define REQUEST_BULK_DUMP 0x004 RECEIVED MESSAGE HEADER, REQUEST_BULK_DUMP, EOX RESPONSE HEADER, START_BULK_DUMP, version (msb), version (lsb) transmit bulk dump version, receive bulk dump version, Utility bulk dump version, transmit program version, receive program version, EOX HEADER, RECEIVE_DATA, USER_PROG_TABLE (not split byte), data count (bits 6 -0, not split byte), data count (bits 13 -7, not split byte), data count (bits 15-14, not split byte), data (this is split byte), EOX HEADER, RECEIVE_DATA, BANK_NAME_TABLE (not split byte), data count (bits 6 -0, not split byte), data count (bits 13 -7, not split byte), data count (bits 15-14, not split byte), data (this is split byte), EOX HEADER, RECEIVE_DATA, UTIL_TABLE (not split byte), data count (bits 6 -0, not split byte), data count (bits 13 -7, not split byte), data count (bits 15-14, not split byte), data (this is split byte), EOX HEADER, END_BULK_DUMP, EOX #define START_BULK_DUMP 0x005 HEADER, START_BULK_DUMP, EOX RESPONSE see RESPOND_TO_MESSAGE #define END_BULK_DUMP 0x006 HEADER, END_BULK_DUMP, EOX RESPONSE see RESPOND_TO_MESSAGE #define REQUEST_DATA 0x007 HEADER, REQUEST_DATA, memory type (not split byte, see REQUEST_BULK_DUMP), data count (bits 6 -0, not split byte), data count (bits 13 -7, not split byte), data count (bits 15-14, not split byte), EOX RESPONSE HEADER, RECEIVE_DATA, memory type (not split byte, see REQUEST_BULK_DUMP), data count (bits 6 -0, not split byte), data count (bits 13 -7, not split byte), data count (bits 15-14, not split byte), data (this is split byte), EOX #define RECEIVE_DATA 0x008 HEADER, RECEIVE_DATA, memory type (not split byte, see REQUEST_BULK_DUMP), data count (bits 6 -0, not split byte), data count (bits 13 -7, not split byte), data count (bits 15-14, not split byte), data (this is split byte), EOX #define SET_MIDI_MERGE 0x009 HEADER, SET_MIDI_MERGE, merge on/off (0= off, 1= on), EOX RESPONSE see RESPOND_TO_MESSAGE #define RESET_PROGRAM 0x020 HEADER, RESET_PROGRAM (returns to main menu), EOX RESPONSE see RESPOND_TO_MESSAGE #define RECEIVE_KEY_SCAN_CODE 0x054 HEADER, RECEIVE_KEY_SCAN_CODE, key code, wheel direction (only useful for the encoder wheel), EOX RESPONSE HEADER, RESPOND_KEY_ACCEPTED (responds when the key is seen), key code, EOX #define RESPOND_KEY_ACCEPTED 0x056 HEADER, RESPOND_KEY_ACCEPTED, EOX RESPONSE HEADER, RESPOND_TO_MESSAGE, RESPOND_KEY_ACCEPTED (not split byte), MIDI_UNKNOWN_PROC_ERR (not split byte), EOX #define RECEIVE_OS_CMD 0x016 // Store prg HEADER, RECEIVE_OS_CMD, os command (like store prg, see MIDI OS cmd defines below) data for the command (prg number for store) EOX RESPONSE see RESPOND_TO_MESSAGE #define RECEIVE_PARAMETER_VALUE 0x018 HEADER, RECEIVE_PARAMETER_VALUE, parameter index (should follow the matrix), parameter value (msb), parameter value (lsb), EOX RESPONSE see RESPOND_TO_MESSAGE #define RESPOND_TO_MESSAGE 0x07f These messages will be added in the next version release. #define RECEIVE_PRG_NAME 0x015 #define REQUEST_PARAMETER_VALUE 0x017 // MIDI address table indexes, // used in bulk dumps #define USER_PROG_TABLE 0 #define USER_PROG_INDEX 1 #define FACT_PROG_TABLE 2 #define SDISC 4 #define BANK_NAME_TABLE 5 #define UTIL_TABLE 6 #define LED_BUFFER 7 #define ZREG_BUFFER 8 Here are the current sysx error codes. // MIDI error messages (in response to a sysx message) #define MIDI_PROC_NO_ERR 0 #define MIDI_UNKNOWN_PROC_ERR 1 #define MIDI_BAD_PRG_NUMBER 2 #define MIDI_WRONG_MODE 3 #define MIDI_UNKNOWN_OS_CMD 4 #define MIDI_BAD_USER_PRG_NUM 5 #define MIDI_REQ_PRG_ERRS 10 // 10= wrong size, 11= bad prg number #define MIDI_REC_PRG_ERRS 15 // 15= wrong size, 16= invalid bank // 17= invalid user program number #define MIDI_REC_SYSX_ERR 20 // 20= not enough buffer space // 21= ran out of buffer space while receiving #define MIDI_BULK_DMP_ERR 40 // 40= wrong size of request proc #define MIDI_UTIL_DMP_ERR 50 // 50= invalid version Here are the current sysx operating system (OS) command codes. // MIDI OS cmd defines #define MIDI_OS_CMD_STORE 1 // store the current program #define MIDI_OS_CMD_UPD_SDISC 2 // download the sdisc buffer #define MIDI_OS_CMD_INIT_ZREGS 3 // calls wr_zreg_xdata_buf() #define MIDI_OS_CMD_RD_ZREG 4 // reads one ZREG and returns it Here are the current key codes. #define KEY_PICKUP KEY_MATRIX1 #define KEY_COMP KEY_MATRIX2 #define KEY_WAH KEY_MATRIX3 #define KEY_MODEL KEY_MATRIX4 #define KEY_EQ KEY_MATRIX5 #define KEY_TALKER KEY_MATRIX6 #define KEY_EFFECTS KEY_MATRIX7 #define KEY_DELAY KEY_MATRIX8 #define KEY_REVERB KEY_MATRIX9 #define KEY_BANK KEY_FS6 #define KEY_CONTROL KEY_FS5 #define KEY_FS_AMP KEY_FS2 #define KEY_FS_EFFECTS KEY_FS3 #define KEY_FS_DELAY KEY_FS4 #define KEY_FS_COMP KEY_FS1 #define KEY_FXMODE KEY_MENU1 #define KEY_EDIT KEY_MENU2 #define KEY_RHYTHM KEY_MENU3 #define KEY_STORE KEY_MENU4 #define KEY_UTILITY KEY_MENU5 #define KEY_ASSIGN KEY_MENU6 #define KEY_FS_TUNER 22 #define KEY_FS_BYPASS 23 #define KEY_FS_LAL 25 #define KEY_WHL0 24 #define KEY_TIMEOUT 26 #define KEY_REPEAT 27 #define KEY_MENU1 18 #define KEY_MENU2 20 #define KEY_MENU3 21 #define KEY_MENU4 19 #define KEY_MENU5 16 #define KEY_MENU6 17 #define KEY_MATRIX1 9 #define KEY_MATRIX2 5 #define KEY_MATRIX3 8 #define KEY_MATRIX4 6 #define KEY_MATRIX5 15 #define KEY_MATRIX6 7 #define KEY_MATRIX7 11 #define KEY_MATRIX8 12 #define KEY_MATRIX9 10 #define KEY_FS1 1 #define KEY_FS2 2 #define KEY_FS3 3 #define KEY_FS4 4 #define KEY_FS5 13 #define KEY_FS6 14