Kurzweil 1000 Series Upgrade Process #2

Before you begin read the Static Handling information.  Then read the Basics information and Chip Data. Then read this page and understand how to download the chip data you will need.  If your upgrade requires a jumper change, look at the Jumper Pictures.

Several members have upgraded one or more Kurzweil 1000 series keyboards or modules. Each person may use different chip burners and/or take a slightly different approach. Before you attempt to upgrade your unit, read each approach. The more you know the better success you will probably have. 

This is Process Documentation #2:  For and alternate process go to upgradeprocess1

You will need to find a source for the PROM/EPROM chips required for your upgrade. Specifications sheets for the various types can be found in the Manuals page. The 'speed' of the chips you purchase may be important so review all the notes regarding the upgrade before you purchase chips. You can find a beginner's discussion about chips, eproms, roms etc at http://www.ustr.net/memory.htm (this will open a new window).

The raw data (zip files) required to burn the chips is in the Chip Data page. Choose the file for your desired upgrade. Note that the 8 (Eight) button boxes have two possible OS chip sets.  Details in the Chip Data page.

Process Documentation #2:

How to upgrade the Kurzweil K1000 and K1200 modules.

You can upgrade / expand the modules a bit (from SX > SXA) or "all the way". These are the PRO 1-3 modules. Upgrading a bit is wasting time and money, because for the same you can have it all. And on this site only the OS for the PRO's are available.

This is what you are dealing with:

We have 8 button modules (AX, PX, SXA, etc) and 23 button modules (PRO 1-3).
Some modules have socketed eproms and some have soldered eproms and some a mixture of this.
Each module has 4 OS (operating system) eproms and up to 12 sound eproms.
Only the PRO's are fully loaded.
If you upgrade the sound eproms, you also have to upgrade the OS eproms. They are related.
Only the eproms with a window on top (under a sticker), can be erased. Others are OTP (one time programmable).
For JP03/JP04 jumper change, see upgrade process #1.
Socketed eproms can be removed very easy (with a chip puller). Soldered eproms can also be removed, but this is a lot work.

What can become what:

Each (8 or 23 button) module can become any PRO. BUT if eproms are soldered and you don't want to unsolder them, you can only upgrade in the same line. For instance a PX (piano) has to become a PRO 1. The PRO 1 is the piano and more module. If you change all eproms (soldered or socketed) and OS, you can make any PRO. But I think an 8 button module cannot become a PRO 3 because the OS cannot handle this. There is also no OS upgrade available for this.
So if you want a PRO 3, you need a 23 button module.

What do you need:

Eproms. 27c801 or 27c080 for sound. (See information on the Chip Data page about alternative Sound Roms chips.) You need 27c512 (200 ms or faster) for OS. (Expanders only) Do not mix different speeds. Eproms can be found at eBay. Just search for the type (like 27c801). Data sheets for the eproms can be found on the manuals page of this web site.
Programmer
Chip puller
Data for programming can be found on the Chip Data page of this web site.

For soldering.
Small 15-30 Watt soldering device.
Desoldering pump.
Magnifier (with light).
Sockets 32 pins wide.
Guts.

You need to solder for the eproms (but you don't have to) and for some boards for the JP03/JP04 jumpers. Changing jumpers is needed. Details can be found the upgrade process #1 documentation. Follow the upgrades menu link.

I desoldered eproms because I wanted a PRO 2 and 3 and wasn't patient enough to wait for available modules. If you sure you also want to do this, do it the less difficult way. Because the soldered eproms can not be erased (OTP), don't spare them. Just cut the legs and desolder the legs one by one. Desoldering is the major job. You need a desoldering pump. I hooked it up to my vacuum cleaner. Be careful not to overheat the vacuum cleaner. After that buy sockets for soldering. Soldering with a magnifier and a small soldering device is easy and even fun.

How to program.

I have used a Batupo programmer from Batronix. This is the "basic" one, but enough for the Kurz. Can be found here.........
(http://www.progshop.com/shop/programmer/BX32/eprom-programmer.html )
I tried a Willem programmer and an unknown brand, but I couldn't program. If you are not familiar with electronics and programming, use the Batupo. This one so very easy. Read the online info at that site.

After installing and connecting the programmer (Only USB).
Start the software.
Insert the eprom
Click "Auto-Indentify" for the chip. Some cannot be recognised. Browse till you find the right one.
With "Open File" browse to the desired data. Download the data first from the Chip Data pate of this web site.
Click Start
If the eprom is not empty, you get an error. So you have to erase, using a UV eraser. The programmer cannot erase.
After burning, the software verifies the burned data with the original data.
Finished.
Remove the eprom, sticker (close) the UV window and mark it. (58 for instance).
Add it to the Kurzweil board. 58 has to be in socket U58. Do not mix them up.

The 4 OS eproms from the 8 button units can be re-used (remove the sticker and erase) if you don't want to save them. But 2 of them (U22 and U33) are too small (they are 32k x 8 bit) for the PRO OS, so you need 64k x 8 bit replacements.

Erasing a eprom / chip

The ones with a window (sometimes stickered) can be erased with an UV eraser. This is a small and cheap box with a UV lamp. The UV light erases the eprom. A programmer cannot erase our chips. Do not overdo the erasing. You can damage them. Start by a few minutes and then try to program. With error "chip is not empty" do some more erasing by the minute.
A chip can be broken. For these you always get "chip is not emty". Sound eproms are larger, so this takes longer to erase / program.

Process Documentation #1:  For a different upgrade documentation go to upgradeprocess1