Common VCI-100 Firmware Questions

[Thenavigator]

What version of traktor are you using?

[EMMan]

Hi,

Can I update my old second hand VCi-100 1.1 straight to 1.4?

[Thenavigator]

yes you can

[EMMan]

Thanks.

Anyone know when the Update Kit will be back online in the store?

[djgnyce]

Hi, today i had becomme the Firmware Kit.

But im become the Error No 15024: Boot failed

Im reading all the posts, but im already become this Error.

-Im usning a USB - Serial Calble....

Pls help me =P

[djgnyce]

I GOT IT - I GOT IT

@All - pls make sure, that u have installed your USB -> Serial Driver!

1. Connect your VCI to Pc - do not take it on.
2. Install the Driver USB -> Serial (The Name is on the Cable, or the Serial itself)
3. Run the FDT and choose the COM Nr. for your Serial -> USB
4. Look the Video =P
5. Flash it and it will work!

-SORRY FOR MY BAD ENGLISH, IM FROM GERMANY

[djfbus]

Hi,
Either I'm very confused or something is not working, can anyone give me some pointers please?
I'm updating from 1.2 straight to 1.4 via serial to serial straight through cable using Win XP and FDT 4.05. I follow the steps in the how to video and after running the software get the message below, which indicates to me that it was successful? Yet in use and with the various tests (RHS SYNC button does not toggle) the VCI seems to be 1.2 still? Anyone with a similar problem / what was the solution?

thanks

Fletch

What FDT reports:

OS: Windows XP [Admin]
FCF Settings Applied: H8/3052F, (C:\Program Files\Renesas\FDT4.05\kernels\ProtB\3052\Renesas\1 _2_00\)
FDT API initialised: version 4, 05, 00, 008
FCF Settings Applied: H8/3052F, (C:\Program Files\Renesas\FDT4.05\kernels\ProtB\3052\Renesas\1 _2_00\)
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
Received immediate response from device: 0xAA
Using micro-Kernel : 'C:\Program Files\Renesas\FDT4.05\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.05\kernels\ProtB\3052\Renesas\1 _2_00\Genm3052.cde'
Main kernel download complete...
Connection complete
Processing file :"C:\Documents and Settings\rupert\Desktop\VCI100-DaveX-1.4.mot"
Operation on User Flash
Downloaded the operation module
Writing image to device... [0x00000000 - 0x0000907F]
Writing image to device... [0x00009080 - 0x0000917F]
Writing image to device... [0x00009180 - 0x00009AFF]
Data programmed at the following positions:
0x00000000 - 0x0000907F Length : 0x00009080
0x00009080 - 0x0000917F Length : 0x00000100
0x00009180 - 0x00009AFF Length : 0x00000980
38.75 K programmed in 16 seconds
Image written to device
Disconnecting
Disconnected

[djfbus]

Ok - this is driving me nuts now. I understand that getting a connection problem will not allow the firmware to write - but I'm getting a write success message! I've done all the following:

connecting serial and then usb in the correct order
lower the baud rate to 9600
complete reinstall of FDT and start again
suspending the VCI so no buttons pressed during boot mode
ensure PCB is properly seated
changed serial port name from COM1 to COM3 - really clutching at straws now.

pFoKuS seems to have had a very similar problem - but I could not understand how this was solved.

I've seen some posts where there are 5 or 6 lines of image written to the device (going 1.2 to 1.4) - does the fact that I've just got 3 indicate a problem? Also similar posts show that the write took way longer than my 16 seconds - is this a possible problem? (I doubt this as lower baud to 9600 caused 56s write).

Anyone out there had similar problems and more importantly have the solution?!

Believing the write to have worked I applied the v.3 overlay and now am stuck with a fw1.2 VCI with a v.3 overlay - utter pants!

HELP!

[photojojo]

I think my upgrade was applied but it would be great to know if there is any way to 100% tell.
Maybe this is telling enough?

DaveX posted this related to the light test:
Bonus #1
========

Did you know that there's a factory test mode hidden in every VCI ? It's used in the factory to test all the buttons, faders, knobs and LEDs.

With 1.4 firmware: While your VCI is off, hold RIGHT ECHO+PLAY buttons (VCI-100SE mapping) and turn it on.

With previous firmwares: While your VCI is off, hold LEFT ECHO+PLAY buttons (VCI-100SE mapping) and turn it on.
============

For me I am able to get to the light test by holding the Right Deck's echo + play buttons while powering.

Maybe that is conclusive?

Thanks in advance.

Paul

Sounds conclusive to me, Are you able to use Fader FX mode?

Hi, I completed a button mod and a 1.4 firmware update two months ago, all seamed fine but on the odd occasion when hitting fader fx mode traktor would crap itself. Now it appears the whole controller crashes and losses all connectivity to the pc, i have tried it on two other laptops and used different usb cables but still fails. please help!

Try setting the out port to NA. If that works you may be able to use Drew's fix. PC only though.

http://www.djtechtools.com/forum/showthread.php?t=17497

Hi,
Yet in use and with the various tests (RHS SYNC button does not toggle) the VCI seems to be 1.2 still?

You should be testing the LEFT sync button.

http://www.youtube.com/watch?v=Frehvs6aJjA

[djfbus]

thanks Chris,

I did test with that one - I get my LHS / RHS muddled on times (dyslexia)...

...still no joy. I'll press on or take an alternative route.

Paul