There is an option to test dice communication in vida....After getting the "service machine", provided by roxanascham, installed to a virtual windows 7 pro 32 bit system, I ordered a VIDA/DICE unit and plugged it to virtual machine and to the running vehicle, confirmed that it read the vehicle information, displaying VIN and other information. Under Diagnostics I can see the Module tree with ECM,TCM, etc. All I can get is information about the vehicle, but no where in TCM where I can reset the Fluid Counter, for example. Are there any DICE units out that only read information, but will not send communication to the vehicle? Or, if anyone has the specific steps, after Vida loads and reads the vehicle, to get to the TCM Fluid Counter reset?
There is an option to test dice communication in vida....
Cant recall on top of my mind...but it is in the firts steps...
I think its under vehicle information
Envoyé de mon SM-N920W8 en utilisant Tapatalk
Thank you. Yes, I understand how it is supposed to work. But, I believe my DICE is defective, even though DICE communication tests OK generally, through the Windows Start/Dice/DICE Diagnostics. The bottom <Vehicle Interface status> light blinks orange constantly. I believe it is supposed to be ON constantly when Interface has been established. This results in the infamous [CEM] error indication when the vehicle is being Read. [Also, my Scangauge works perfectly with this vehicle, and it connects to the OBD port and reads many parameters of vehicle performance.]The fluid counter supposed to be reset with the engine off and key in posII, have not paid attention to the LEDs (edit- see this was already tried).
If the DICE is connected and communicating to the point you're able to see the reset (in Vehicle Communications/Activations I think), it's likely that the unit is functioning. Could do a re-read of the modules, see if that clears anything up. Any errors on TCM (might prevent more menus being shown) when you look at diagnostics?
Which VIDA version are you running out of curiousity? Access scenario sounds like a pre-2013.I get "The system cannot find the patch specified" when I run filldb.cmd. Any help? I've extracted the files to C:/VIDA and I'm running it as admin. Also tried running it both with and without the vida monitor application running. If I try to login to VIDA it just loads for a second and returns to the login screen, no info.
No problem. Actually my DICE can no longer read my vehicle. See above post.I kinda jumped on the last post without seeing your earlier post on what you had already attempted. Just seems odd that you're able to connect to the car but not complete the reset action. Can you pull parameters from the individual modules and see them on the screen? I probably won't be much help but wanted to ask a few basic questions first. Apologies for any inconvenience caused....
The downloads in the above post will only work for 2014D. The license file is different for each release.
Before finding this thread, I fixed my 2014A installation by using WinRar to extract 3 files out of the original patch executable.
A windows batch file called filldb.cmd
An SQL command file called filldb.sql
the VIDA license file called license
These need to be copied into a new directory called 'patch' in the VIDA home directory (normally C:\VIDA\).
You then edit the license file in Notepad and search for 'subscriptionExpireDate', you will find a date after it ("2017-12-31 23:59:59").
Change the year to whatever you want (within reason) and save the file.
Stop the VIDA service from the task bar by right clicking on the icon and selecting Stop,
and run the filldb.cmd command file (preferably from a command line window while in the C:|VIDA\patch directory).
This then creates an SQL command file to write the data from the license file into VIDA's SQL database and runs it using the MS SQL command line.
Restart the VIDA service by right-clicking on the task bar icon, and once it's status shows as 'Running' try starting and logging in to VIDA All In One.
The expiry warning should have gone.
I was lucky that I still had the original patch executable I had run when I installed 2014A. To do any of the above you need the patch executable that matches your version.