Reply to Firmware FAQ and Upgrade Solutions

FAQ

How do I update my firmware?

Please visit this post to learn how to update your firmware:
http://www.djranking s.com/2008/08/1...-100-firmware/

If you have problems please visit this thread:
http://www.djranking s.com/community /sho...=7732#post7732


Which firmware version does your VCi-100 have?
Version 1.1
the firmware with the "ramp up problem"
http://www.youtube.com/watch?v=b2Y509VQVEQ

the jog wheel touch sensor turns off when the wheel stops turning, not when you release your finger.

Version 1.2
-VCI-100's with a green sticker on the back are firmware version 1.2
- this version solved the ramp up problem but still has several bugs including
* the fourth FX buttons send out the same midi message as the right headphone cue button.


Version 1.3
The firmware found in all VCi-100SE controllers that was designed by Ean Golden.

You can tell if you have 1.3 by following these steps.

1) connect your vci-100 to a computer but dont start traktor.

2) Click the button that is at the top right hand corner of the left jog wheel (its next to the filter knob for deck A).

3) If this button's light toggles on and off then you have 1.3 (the same button on the right deck will not toggle on and off.

Here are a few of the changes made in 1.3

general improvements:

* Eliminated the problem where the 4th FX buttons trigger other buttons (cue)
* added midi in functionality to the loop buttons
* added a note on to the jog wheel in scroll mode

performance:

* turned the filter knobs into double knobs (0-127 on the left and right side)
* added a "freeze function" to the bottom of each fader and top of the fx knobs. this sends out a 127 message only at the end of the movement
* added inverted messages to the faders (this allows an effect to be turned on by turning the fader down- not possible otherwise)
* added unique values to the FX buttons (these were used for direct FX selection- now added in Traktor Pro)


Problems updating your firmware?

first some basic rules:

• serial to serial cables work perfectly and have reliable results (use one if you can!)
• You must use a standard serial cable- not a null modem cable
• serial to usb cables have very erratic results and cause problems (see bellow)
• the com port your device is on needs to be between 2-8 (when using a USB)
• follow the order of plugs and power very carefully

Everything works but at the end you get the following message:
Opening port 'COM3' ...
Loading Comms DLL
Loaded Comms DLL
Error No 15060: Error while opening the port
Error No 15026: Unable to open comms
Error No 15061: Error while closing the port

You have the wrong COM port selected. Each USB port has different COM address, so make sure you have the right one selected. COM 3 is usually a serial while 2, 4, 5 are usually one of the USB ports.


Everything works but at the end you get the following message:
OS: Windows XP [Admin]
FDT API initialised: version 4, 02, 00, 008
Clock Frequency (External) = 24.0000MHz, Clock Mode = 0, CKM = 1, and CKP = N/A
Connecting to device 'H8/3052F' on 'COM3'
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM3' ...
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Attempting 4800
Attempting 2400
Attempting 1200
Error No 15024: Boot failed

this seems to only be happening to people with a usb to serial cable. if at all possible try a different cable or use good old serial port on someones computer. There was a also a report that this error was corrected when making sure the firmware kit is seated completely down on the board. This requires removal of the harness next to the header so it can sit down completely.

if you must use a USB to Serial, read this

If you are using a USB serial cable plug it in to a USB port

Now run device manager, if you don't know how to do this follow this link.

[ame="http://en.wikipedia.org/wiki/Device_Manager"]Device Manager - Wikipedia, the free encyclopedia@@AMEPARAM@@/wiki/File:Vista_Device_Manager.png" class="image"><img alt="" src="http://upload.wikimedia.org/wikipedia/en/thumb/d/d7/Vista_Device_Manager.png/220px-Vista_Device_Manager.png"@@AMEPARAM@@en/thumb/d/d7/Vista_Device_Manager.png/220px-Vista_Device_Manager.png[/ame]

Now expand the ports branch,
(See thumbnail 1)

If you are using a built in serial port its is most likely assigned to COM 1,
Check that there are no ports with the same number, if another device is assigned the same COM port number you will have to change it to use another number.

If you are using a USB serial cable then it will appear in the list called something like "Prolific USB-to-Serial Comm Port", if you are confused about which one it is remove your USB-serial cable from the USB port, then you should see that device disappear from the Ports tree.

Now right-click and open the properties of the Port you are using, and the click the port setting tab. (See thumbnail 2)

Check that your settings are the same as in thumbnail 2. If they are not change them.

Now if you need to change the serial port number click the advanced button. (See thumbnail 3)

You can now change the Com port number that is assigned to the serial port in the drop down menu. Select a number in the range of 2 - 8 that is not in use.

Click ok in the advanced settings window, then ok in the properties window.

If you are using a USB serial cable unplug it then plug it back in to the same USB port.

Now repeat the instructions in Ean's video.

You get a time out error

Clock Frequency (External) = 24.0000MHz, Clock Mode = 0, CKM = 1, and CKP = N/A
Connecting to device 'H8/3052F' on 'COM3'
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM3' ...
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Received immediate response from device: 0xAA
Using micro-Kernel : 'C:\Program Files\Renesas\FDT4.02\kernels\ProtB\3052\Renesas\1 _2_00\uGen3052.cde'
Downloading and verifying micro kernel...
Device is erasing...
Erase Timeout value set to 21 seconds
Error No 15068: Error while reading timed response
Error No 15047: The device has not confirmed its erasure
Error No 15019: Download() failed

In the directory which you installed FDT, there will be a file called "FDTAdvancedSetup.exe". You can use this file to adjust the delays sent by FDT.

Essentially, a USB connection is way quicker than a serial connection and as such, sometimes your connection will be too quick for the software. The connection gets ahead of the instructions and the instructions get lost resulting in time outs.

So, back to FTDAdvancedSetup... go into this, you will see two boxes you can click on: "connection settings" and "configure serial port...". Click the "configure serial port..." box. In here, you will see a box "enable serial port delay fix". You want to make sure that's checked. Then where it says delay value, enter 1000 or something (1000 worked for me, you may need to go higher depending on the cable). Disregard where it says the lower the value the better, that doesn't really apply to us as we're just downloading the file, not doing live programming.

This should fix all those time outs and connection errors when using a USB to serial adapter.


After performing the set up steps and connecting the firmware header, the jog wheels still light up blue. When I touch them they turn red.

this is the only thing that would indicate there is something physically wrong with the firmware kit.

• Check to make sure the kit is seated properly on the board in the right place(including removing the cable as shown in the video)
• make sure its connected to the computer serial port or usb port.

If your unit will still not start up in boot mode (the unit is on but the wheels dont light up) then there is something wrong with the kit. Email us (service at djranking s.com) and we will send you a new one promptly.