Firmware Update of the CVS16

See release notes at bottom of page!
Flashing the CVS16
Required accessories:
  • USB cable plug type Micro B (CVS-side as a plug for any smartphone) to type A (PC-side)
  • A PC or Mac or .. The operating system does not matter, it just needs to support USB mass storage devices. CVS is a storage device such as a USB stick. *)
  • Download firmware file located in DownloadCVS16v4.1.bin
  • CVS16
*) .. MacOS generates hidden files on a volume. If this appears as a file AFTER the actual firmware file has been copied on the “stick” CVS will flash once again and so with “garbage”. The result would be that CVS does not work afterwards. If you have no host on a different operating system eg Windows which does not do such things then please read here on remedies against such a life of its own from MacOS.
Also Linux is not necessarily the appropriate OS for that: It generally thinks better not to touch the first block of each storage device (boot block).
Perform update:
  1. Disconnect battery (balancer plugs etc) and JLog from CVS. 
  2. Connect CVS to the PC (USB).
  3. It takes about 20 seconds to CVS appears as a drive.
  4. The file system of the drive will show up with a single file “firmware.bin”. Delete this file!
  5. Copy the downloaded file containing the firmware to be flashed onto the drive, represented by CVS.
  6. As precaution wait 2..3 seconds (CVS gets its operating voltage via USB) then disconnect USB, remove the cable from CVS.
  7. Connect CVS16 back to JLog, possibly for testing also a battery to the pins (balancer connectors) – but with the completion of step 6 that was it. 
————————————————– ——————————-
As this always leads to questions:
Please just follow the instructions above.
The flashed firmware version can NOT be determined.
The file name does not matter. That the firmware is afterwards always shown as “firmware.bin” is normal.
firmware.bin is the virtual file representation of the Flash ROM (program memory) in an equally virtual file system.
The first series is shipped with firmware version CVS16v1.00. This firmware has a bug that crept in when a change has been made ​​up at the last second – which locks the auto calibration after it was carried out by the manufacturer.
Oct 12, 2014
The next version was CVS16v1.01 followed by CVS16v2.02, now is CVS16v3.00!
The versions 2.02 and 3.00 improve accuracy, repeatability of measurement results and also the temperature compensation. v3.00 also includes mechanisms to improve the security of calibration data. Previous occurrences of a sudden deleted data memory suggest that this could happen by crazy gambling supply voltage. If possible JLog (and so CVS) should currently not be supplied from the JIVE Pro option port instead via JLog’s “JIVE Port” with the BEC voltage, and best, if possible, from a different power source. Unfortunately, the “BEC Bug” of the JIVE Pro is apparently still on the loose – and also the BEC startup behavior of the KOSMIK not just brings a reliable supply voltage.
CVS16v2.02 and 3.00 is compatible with the calibration data of CVS16v1.01!
Most improvements in v2.02 and 3.00 only come into effect when CVS was recalibrated. Should described above bug have struck in v1.01 must be recalibrated anyway.
The calibration is performed at the manufacturer R²prototyping in Switzerland.
Who wants to calibrate by itself and has the ability:  The calibration voltage is 65.000V (65 volts). You must not only be able to display the calibration voltage on 5 1/2 decimals than also the accuracy of the measurement must be that high! If you can not ensure this you should NOT calibrate itself! Any damage caused by electrical abuse in self-calibration actions will not be compensated by the manufacturer.
Attention! If you do not have correspondingly accurate measuring equipment as well as some electronic knowledge you should not try at the calibration! You will certainly also know that 60 volts DC represent a safety limit.
– flash firmware CVS16_Clear_Calibration.bin
– Disconnect USB!
– supply CVS with voltage (connect to JLog). After completion of the Clear routine the red LED lights up permanently, possibly flashing the blue.
– flash firmware CVS16v3.00.bin
– Disconnect USB!
– Calibration voltage 65.000V ready. – Connect pins 1..16 all to each other, this gives us virtually two pins, GND and input as 16 inter-connected pins.
– Connect input (1..16) to GND (ground the input). – Connect CVS to JLog. CVS starts. – Now the red LED flashes for exactly 2 minutes, all other LEDs are off. – After 2 minutes the green LED goes additionally on for 2 seconds. This means that the offset is determined.
– Now the blue light is on, the red continues to flash. With the blue LED CVS requires the calibration voltage. Now remove input-GND connection and connect the calibration voltage 65.000V (65 volts) between input and GND.
– The blue LED goes out, instead the orange flashes in addition to the red LED. – The state continues 3 minutes. This is followed by the actual calibration process, indicated by flashing 5 times with all 4 LEDs.
– The calibration is completed as it burns only the green LED, statically.
– To enter the operational mode CVS needs to be repowered, disconnect/connect JLog. The green LED will as usual flashing (1x for 10 complete cycles), the blue LED flashes as bus activity indicator (CVS – JLog). Red and orange LED burn only when an OOB or UC-alarm is active.
I apologize for the inconvenience caused thereby!

Die Kommentarfunktion ist geschlossen.