Common VCI-100 Firmware Questions
Common VCI-100 Firmware Questions 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) | |
| Adolf Hit 06.01.2009 | Hi Derek, From what I can understand you are upset that your USB to serial cable did not do the job, if you had read through the community s you would see that infact most people have used some kind of usb to serial cable to flash the firmware. If you feel that we have misled you in some way can you please provide a reference then we can see if it needs to be re worded? also @SPITA you have the clock frequency set to 22 MHz. It should be 24 MHz |
| Harley Wrase 07.01.2009 | I had this error:
same messages:
Attempting 4800 Attempting 2400 Attempting 1200 Error No 15024: Boot failed I'm really mad on DJTT now because all the way in video/community you say that usb to serial cable is ok and works fine but as we can see it's not a 100% sure way to flash the vci. Personally i bought an a usb to serial cable (usb is working everywhere and not everybody have serial port) and was ready to flash it immediately, then i noticed that it doesnt work and i had to buy another one, this time serial to serial and it worked. I lost some money and time because you guys persuade us to buy wrong cable! Please update info on the main site. |
| Soraya Mikesell 14.12.2008 | please help i'm not able to upgrade I've try everything that in the community s said i put back my vestax but now i'm not able to use it any more the only thing it does a red light on right jogwheel sometimes turn on i 'm using a usb to serial i guess i'll try to get another cable or find someone who have an old computer with a serial connection Clock Frequency (External) = 22.0000MHz, Clock Mode = 0, CKM = 1, and CKP = N/A Connecting to device 'H8/3052F' on 'COM4' Configuration: 'BOOT Mode' connection - using emulated interface Opening port 'COM4' ... 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 Erase Successful micro-Kernel download successful Sending inquiry for getting line size Buffer size has been set to default (128 bytes) Sending selection of device command Selection of Device - Device selected, code 0302 Sending selection of clock mode Sending selection of clock mode Selection of Clock Mode - Clock selected, code 0 Changing baud rate to 9600 bps Error No 15005: 'COM4' read time out Error No 16148: Unable to set baud rate value = 9600 Error No 15016: Changing baud rate to 9600 bps |
| Trần Trung 13.11.2008 | Nevermind folks after trying over and over again on my pc, I grabbed my labtop I use for work, and since I have a docking station to it, I installed the software on it and used just my regular belkin Serial Cable, and BAM Success. I guess I have some issues going on with my PC that I need to look into. Now the fun can begin... |
| Trần Trung 12.11.2008 | Hello everybody, well I got my vci-100 a few weeks ago, but got my firmware upgrade kit back in late September, and today I had the time to finally upgrade and put everything I got for the upgrade which included, the firmware kit, overlay and the jog wheel covers, and I also went ahead and added the pro X fade. Well everything went to plan except the firmware upgrade, I've been trying to do it over 5 hours now and nothing has happened. I dunno I believe the firmware kit is bad, I have a serial cable and i thought that was bad so I went and bought another along with a serial to usb cable with a communicator light built in and it was transmitting to the vci but then I noticed, everytime I powered on the vci, the red leds came on, so I would start all over again, but unconnecting the usb to the vci and the serial cable from firmware upgrade kit, I also went into the Device manager and lowered the Data bits, and even tried adjusting the adjusting the recommended speed, nothing happened I kept on getting the Flash Development Toolkit and flash programming components are provided without support 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 So with me failing in that I went ahead and put everything else on and tested the unit, it works fine, but the trouble I am having now is with the Firmware upgrade and I believe I have a bad part, I am open to helpful tips, but so far everything you guys have suggested to do from this Thread I have tried and failed numerous times, but I am still open to more suggestions. If I don't reply today, I will tomorrow when I arrive home from work, to try again with the suggestions from you guys. |
| Jose Rodriguez 09.11.2008 | I tried, I failed...any help would be very much appreciated. I am using the serial to usb cable from Monoprice. I installed the drivers from the disk that comes with it. One question I have is, there is no option for COM1, only COM3. Is that how it is supposed to be? This is what my window says at the end. I also set the delay to 1000. Any help would be great, thanks 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 Received immediate response from device: 0x55 Attempting 4800 Received immediate response from device: 0x55 Attempting 2400 Received immediate response from device: 0x55 Attempting 1200 Received immediate response from device: 0x55 Error No 15024: Boot failed |
| 08.11.2008 | thats creative- thanks for sharing! |
| Mauro Giannotti 08.11.2008 | I just finished installing the SE firmware. HooRay!!!!!!!! I followed all instructions in the community , but i still couldn't get the installation to work. same messages: Attempting 4800 Attempting 2400 Attempting 1200 Error No 15024: Boot failed Someone else in the community stated you must use USB power, not the transformer, so I speculated there could be a power issue with my setup. In my case, I was using an older Windows machine to do the installation, but my Vestax always runs off USB power on my Mac. It appears my Windows machine doesn't possess enough juice to satisfy the Vestax. My problem was solved by unplugging the Vestax from the PC and plugging it into the Mac for power. So here is the setup that saved me: Simultaneously a USB from the Mac to the Vesax (power), and a "USB to Serial" from the Vestax to the PC (firmware upgrade). It was smooth sailing from that point on. POWER THE VESTAX WITH YOUR USUAL USB PORT ON YOUR USUAL COMPUTER TO INSURE YOU HAVE ENOUGH POWER!! Good Luck.......... |
| Mac Fly 04.11.2008 | I did all the steps in the video no problem and i hit program flash and this is the error i get: OS: Windows Vista/Server 2008 [Non-Admin] 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 Error No 15064: Failed to write the data byte(s) Attempting 4800 Received immediate response from device: 0x55 Attempting 2400 Received immediate response from device: 0x55 Attempting 1200 Received immediate response from device: 0x55 Error No 15024: Boot failed Im using dynex dx-ubd89 usb to serial cable, anyone have any reccomendations? |
| Eric Powa B 17.10.2008 | Success! Apparently while most usb to serial adapter users can get away with setting the "enable serial port delay fix" value to 1000, the 6 year old belkin adapter I was using needed the delay fix to be upped to 5000(even then it took 3 attempts). Cheers to HW designers who understand the need to separate boot firmware from user runtime areas, Ean Golden for understanding the need to get vci-100 v1's upgraded to stop that annoying ass wah issue and to the DJTT userbase who keep propelling controllerism and digital dj's to new heights. Thanks! sYn |
| alex tsikarishvili 17.10.2008 | hi, it seemed I couldnt join the club of the happy fellows either :-( This is what I got, using a serial cable not USB to serial. ================================================== =========== Clock Frequency (External) = 24.0000MHz, Clock Mode = 0, CKM = 1, and CKP = N/A Connecting to device 'H8/3052F' on 'COM1' Configuration: 'BOOT Mode' connection - using emulated interface Opening port 'COM1' ... Loading Comms DLL Loaded Comms DLL Initiating BOOT SCI sequence Attempting 9600 No immediate response from device. Assuming erase in progress... Erase Timeout value set to 21 seconds Error No 15068: Error while reading timed response Error No 15024: Boot failed ================================================== =========== It appears that the serial cable i was using was faulty, so with a different one upgrade went all smoothly... |
| Eric Powa B 16.10.2008 | Yeah, I am using usb to serial. But unfortunately I made all the described changes to the config of the firmware program before even trying the upgrade. I'm hoping someone here has some serious magic programming juju because I'm afraid I am the first one who has a "didn't go great" story. As of now my VCI is dead... will not update, will not operate normally. anyone have any suggestions? I'm on a MBP running winXP in bootcamp mode. I have a VCI-100 first revision. the USB to serial dongle I'm using is a belkin f5u409. any help would be great. sYn |
| Sean Sibanyoni 16.10.2008 | Hi sYn, Are you using a USB to Serial cable? The timeouts are a common problem with those. Look at the sticky thread in the community for a fix if so. |
| Eric Powa B 16.10.2008 | Anyone having erase timeout issues? I cannot complete the firmware upgrade because my device doesn't respond to the erase command within the 21 second timeout. here is the output. 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 thx sYn |
| jesus gomez 17.09.2008 |
Originally Posted by rcolbourne
|
| 16.09.2008 | Thats a great suggestion! I need to confirm that is a fix- thanks for contributing that indo colbourne |
| Sean Sibanyoni 11.09.2008 | How to adjust FDT to work with USB to Serial cables. 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. |
| 07.09.2008 |
Originally Posted by DaHesu
|
| Steeve Lauritano 03.09.2008 | I just wanted to say that you must power the VCI using a USB cable, as using a power adapter will not work (at least it did not work for me, despite the lights being lit up and everything). EDIT: I mean when you're powering the VCI during the flash. |
| Lucas Carlsen 31.08.2008 | Thanks Steel and everyone else. I was trying to upgrade using a null modem cable with a gender changer but i had all the problems described above. Went out yesterday and got a proper serial cable, and everything worked flawlessly. Now i just have to figure out how to use the new configs. Thank you everyone for your help - this thread really hepled. /D |
| Jo V 27.08.2008 | There are two types of a DB9 serial cable. The one that you should use is called modem cable and the other one is called null modem- or crossover-cable. A null modem cable use to be female to female and a modem cable use to be male to female. With a null modem connection the transmit and receive lines are crosslinked. If you try to use a null modem cable you will get an error when writing the firmware. Therefore use a regular DB9 serial modem cable and NOT a null modem cable. |
| Hannes Deburchgraeve 26.08.2008 |
Originally Posted by MicPhono
|
| Mohit Joshi 26.08.2008 | Alright I got my issues out of the way and was able to upgrade toevening
. In the end the issue was my serial cable. I had a female to female 9-pin serial cable and bought a gender changer so I could connect it to the upgrade board. The cable itself worked but I believe the gender changed is bad. I went to Fry's today and bought a $3.99 male to female 9 pin serial cable and everything worked without any issues. I'll post in the successful upgrade thread as well. THanks!!! |
| Hannes Deburchgraeve 24.08.2008 | So I'm embarrassed to say my jog wheel issue was caused by an ill adjusted jog wheel sensitivity knob. It was just up too high so that whenever I touched the jog wheel it wouldn't turn off again. I turned it down and everything works fine now. Thanks Midifidler! |
| Stephen O'Keeffe 24.08.2008 |
Originally Posted by MicPhono
|
| Adolf Hit 24.08.2008 | @Mycole Glad to hear you found a cable which worked. Ill check out the LEDs on my VCI when I get home, I'm pretty sure the header which you have to remove to fit the vci update is the cable which connects to the jog whell LEDs. |
| Hannes Deburchgraeve 24.08.2008 | Just an update: I was successful finally. I bought a Gigaware USB to Serial cable from RadioShack. The thing worked without having to use the CD. Windows XP had a driver for it already. I just checked which COM port it used in Device Manager and selected that port when I used the Renesas. I now have one remaining issue! My left jog wheel is always Red. The center plater tiggers when I touch it, but it never turns blue and doesn't allow me to pitch shift. The sensor LED above it is always red as well. Could I have missed a step when putting my unit back together? Any tips? |
| Adolf Hit 24.08.2008 | @SGB It might help you if you change the default Baud rate in the Renesas FDK to 9600. @Ean I will start some threads with the different errors as the title |
| Adolf Hit 24.08.2008 | Hi All, I have been experimenting with a USB serial cable and found that it will not program (failing on error 15024) when you either have the wrong serial port selected, or you have the number of the serial port is too high. I found that when I assigned a COM port number of 9 or greater the update would fail on error (15024). USB update cables are often automatically assigned high numbers so this could be an issue for some people. To check for either of these problems follow these steps. 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. http://en.wikipedia.org/wiki/Device_Manager 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. |
| 24.08.2008 |
Originally Posted by MicPhono
MIcPhone, were you able to then successfully upgrade your vci-100 when the right com port was selected? What cable did you use? |
| 24.08.2008 | A few quick notes: We are all entering new territory here so I appreciate your patience while everyone figures out any possible variations between systems. With that being said, Midifidler, do you believe its best if people start new threads for specific problems/questions? I can confirm that Vestax has reported that there have been random results with serial to USB cables and renesas. Can anyone that has had trouble with these cables try a desktop with a serial connection? |
| Elia Ajram 23.08.2008 |
Originally Posted by Fatlimey
|
| Mohit Joshi 23.08.2008 |
Originally Posted by caliborn_g
Hope this helps... |
| Stephen O'Keeffe 23.08.2008 | I got to the last step where you press "program flash," but I keep coming up with this error message. I've tried 4 different USB ports, made sure everything is secure, and have followed the instruction video word by word. My vci is just sitting there gutted open until I can solve this... Can anyone help? 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 Error No 15060: Error while opening the port Error No 15026: Unable to open comms Error No 15061: Error while closing the port |
| Mohit Joshi 23.08.2008 |
Originally Posted by midifidler
I have also tried power cycling the device using the switch as well as unplugging the USB from the PC and then plugging it in again. Unfortunately, I still have the same problem. |
| robert chanda 23.08.2008 |
Originally Posted by sgb
Control Panel/System/Ports(Com&LPT)/Com3 right click, select "Properties"/Port Settings/Flow Control What do you believe Midifidler? A com port issue? I'm handwaving here. |
| Elia Ajram 23.08.2008 |
Originally Posted by mycole
|
| Elia Ajram 23.08.2008 | Another issue trying to upgrade. Looks like I get into boot mode, then erases the firmware, and cannot upload some kernel for flashing. I gave the pcb a thorough inspection for open circuits, and everything was fine there. I checked for documentation as to what that error really meant, no luck on the Renesas site. I'm stuck right now, still trying to find more information on the error codes everybody is getting. log from flasher =================== 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 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 Erase Successful micro-Kernel download successful Sending inquiry for getting line size Buffer size has been set to default (128 bytes) Sending selection of device command Selection of Device - Device selected, code 0302 Sending selection of clock mode Sending selection of clock mode Selection of Clock Mode - Clock selected, code 0 Changing baud rate to 38400 bps Set baud rate value = 38400 Downloading main kernel 'C:\Program Files\Renesas\FDT4.02\kernels\ProtB\3052\Renesas\1 _2_00\Genm3052.cde' Error No 15005: 'COM3' read time out Unable to get acknowledgement after the download main kernel |
| Adolf Hit 23.08.2008 | @MicPhono If it is in boot mode (no LEDs on) then you are a step ahead of Mycole. After you get this error try power cycling the vci with everything connected by removing the USB from the PC then plugging it in again, then try to flash it again. Also confirm that COM 1 is the com port is definatley the serial port you have connected the uprgrade kit to. Though if you are using COM1 you probably only have 1... |
| Mohit Joshi 23.08.2008 | I'm able to get into boot mode, but I'm getting the same thing as mycole: Clock Frequency (External) = 24.0000MHz, Clock Mode = 0, CKM = 1, and CKP = N/A Connecting to device 'H8/3052F' on 'COM1' Configuration: 'BOOT Mode' connection - using emulated interface Opening port 'COM1' ... Loading Comms DLL Loaded Comms DLL Initiating BOOT SCI sequence Attempting 9600 Attempting 4800 Attempting 2400 Attempting 1200 Error No 15024: Boot failed I believe the black connector could be ok since the vci seems to detect the pcb and puts itself into boot mode and all the soldering points look ok. Could it be an issue with the soldering points with the serial connection? |
<< Back to DJ TechTools' VCI-100 FAQReply