FAT32, insert a card into the computer and check if there is a valid GUI *.tft file in the root directory. If not,
format the card again (with FAT32) and then re-upload the tft file to the root directory of the card. Then try
to upload GUI to the Dash7 again. If update does not start or “update failed” message will appear, try
another SD card and repeat the whole process again. In rare cases, the SD card adapter may be faulty, but
usually the problem is faulty or incorrectly inserted SD card. A correctly inserted card means that the
microSD card is inserted in the adapter and the adapter is inserted into the display unit with the QR code
facing the user. A click is heard when the adapter is inserted and the adapter remains locked in the holder.
10.
GUI update failed (update failed message on the Update screen):
Probably faulty microSD card, try another
card. Even if card is working fine in PC, it can be faulty. If GUI update failed also on other SD cards, GUI file
can be corrupted (very rare). Ask our tech support for a new file.
11.
Datalogger is not logging any data, LED on main unit only blink one time:
If the LED on the main unit is not
flashing, it means that no data is being written to the SD card. LED blinks one time at startup during
initialization, what only means that the data logger is powered up.
Possible causes are:
o
No SD card inserted or inserted incorrectly. SD card must be inserted upside down and pushed until
a click is heard and card remains locked in holder
o
SD card is write-protected. On the side of the SD card is a little switch which can lock the SD card
against writing. Slide this switch to the unlocked position.
o
SD card is faulty or not formatted correctly to FAT32. Format the SD card to FAT32 or try another
card.
o
Data logger is turned OFF or conditions for starting logging have not been reached. Go to menu
“DATA LOG” and check if item “Start of SD card log” is set to “NEVER”. If so, change this setting
according to when you want logging to start. You can set it to: “After power ON”, which start logging
immediately after Dash7 is powered ON. Or you can set it to: “After engine start”, which start
logging when engine RPM are higher than 0. Or you can set it to: “After Wheelspeed1 (or2) > 0“,
which start logging when car speed is higher than zero.
o
No connection between the Dash7 and the ECU, or ECU is turned OFF. If no data is available from
the ECU, the data logger does not log. Connect the ECU and turn it on. When data starts flowing
from the ECU and logging conditions are reached, logging should start. If you have followed all the
steps described above and the problem persists, please contact our tech support.
12.
Alarms occurs even if the sensor for the given measurand is not used:
This can especially happen when the
sensor for a particular channel is not connected (channel is not in use), because a disconnected sensor
usually means that the input reading will reach its upper or lowest level (eg. -40°C or +155°C). This value is
usually outside safe thresholds and should normally trigger an alarm (because this feature is commonly used
to warn the driver that a connected sensor is faulty or has been accidentally disconnected). A false alarm can
also occur if ECU was disconnected and reconnected or if data from ECU are corrupted (eg. very low voltage
during cranking, etc). If you want to avoid unwanted alarms from not used channel, solution is to set the
thresholds for that measurand to the values which cannot be reached even with disconnected sensor. If this
is not possible for some reason, you can recalibrate the input channel (change upper and lower values to any
safe values, eg. 5V = 30°C and 0V = 40°C). Last way (usually not necessary) is connectiong some resistor (eg.
2.7kOhm) between the input and GND (or +5V) what set the measurand to a fix value.
13.
When I connect a laptop to the ECU and disconnect a Dash7, it stops to display data. Can I have connected
both, PC and Dash7 to the ECU at the same time? :
Yes, you can have connected your laptop to the Vems
ECU, and at the same time you can watch all data (from ECU and also from Dash7 inputs) on the Dash7, but
you must to use an adapter “Tuning cable” which is available in our shop. This adapter allows you
simultaneously tune your ECU (or log data to the PC or whatever) and display all data and alarms (or also log
data to the SD card) on the Dash7. Without this adapter you can have connected only one device to your
ECU RS232 port (laptop or Dash7).
14.
When I was burning data to the ECU via Vemstune, I got OnScreen Waning message on the Dash7:
This is
normal and it can’t be completely eliminated. Usually it is a trigger error warning message. It happens
because on a short moment when Vemstune is burning data into the Vems ECU, the data sent from the ECU
to the Dash7 is corrupted.