Vci-100 1.4 (hd) firmware upgrade

[pARtybOy]

hello there!I just sent my unit VCI-100 to Vestax to change 4 LEDs,that went off, & I asked them to upgrade my firmware to DJTT 1.4, but I'm afraid how the jogwheels will work with the new FW,I checked the .tsi & I see that it will have 1%sens/19%acel; in my 1.2FW I use 3%sens/0%acel, will it get so diferent from that?here is a video of me scratching in FW 1.2
http://www.youtube.com/watch?v=dmvvXCE4Dro
so anyone who scratches that can give a review about the new jogs resolution?
what about the LEDs,it is the 2nd time I send the unit to vestax to change LEDs (8 leds total burned) is this normal?
thank you, looking forward.

[fullenglishpint]

8 LEDs is unusual, but unfortunately they do sometimes burn out. Was it the same LEDs? I just replaced mine myself, to teach myself soldering

Will they actually put 1.4FW in for you? If so that's awesome.

The jogs are higher resolution so more accurate, you can still change the acceleration etc to suit your needs if you want to.

[photojojo]

I don't think they'll flash it with teh DJTT firmware, but if they do that's awesome. You'll probably need to make adjustments to the 1.4 tsi to suit your style just like you did with the 1.2 firmware.

[pARtybOy]

yes, they will do the FW update,they've picked up the unit yesterday...looking forward...
the LEDs didn't burn all at once,it's like one LED every 2/3months,last year 4 LEDs(sent to repair) and 4 LEDs the last 5 months...& my warranty exp date it's approaching...
My fear about the jogs is that it'll get too fast (.tsi is set on 1%sens) & I can't bring it down....

[ricoot]

They upgraded your firmware to 1.4?!

That is, this is... i'm speechless, really.

#$%^$%^*&^( awesome!!!

[EMMan]

Hi,

Recently updated an old second hand 1.1 firmware VCI-100 to 1.4. No problem. Works perfectly with last TSI file and of course DISCO MODE !

Thanks for help.

[sabastinematthews]

I am still using firmware 1.3 with my vci 100 arcade mod. I am using one of your custom mappings. I believe its 3.1. The last mapping before you replaced two of the buttons with slice and echo effect. Tried it and went back to the other version. I would like to know if I upgrade to firmware 1.4 will I still be able to use this mapping?

[psyfi]

hi your link says vci-100-v3_6-3.zip but when i download it its called vci-100SE-v3_6-3.zip .....is this the same file?

[djfbus]

Hi,

this is my first post and alas it is to ask for help with a problem.

I have a VCI 100 firmware 1.2 (confirm with the LHS sync button test).

I have performed the firmware upgrade via a serial to serial (straight through) cable on a Win XP PC running Renesas 4.05 basic and have uploaded VCi100-DaveX-1.4

The upload procedure all went well, with the software reporting that everything was written and completed successfully.

Yet when I again do the SYNC button test or both SCRATCH button test the unit performs as if it is still firmware 1.2 - I've read this thread and no one has specifically answered this (although someone had a similar issue).

All help and comments appreciated!

cheers

[djfbus]

further to my previous message, this is the 'success' message I get every time (must have tried 10x now!) I flash from 1.2 to 1.4 yet the vci remains as 1.2, what am I missing / doing wrong?

I've read all relevant stuff I can find in the forum, so have tried:

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
I must have tried this over 10x now - each and everytime I get 'Image written to device' - full details below.

I run out of options - can only now begini to wonder if my PCB is faulty or worse my VCI? HELP PLEASE!

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