ETA on the Cell Voltage Sensor CVS16

[mkovalcson]

Tom,

I recently pointed someone at this sensor only to be asked where it could be purchased.

Do you still intend to release this sensor and do you have an expected ship date?

[dl7uae]

Now the answer can be: Very soon.

We've been waiting an eternity to the availability of a component. A few days ago finally got the delivery confirmation from Texas Instruments.

[mkovalcson]

Thanks! I relayed this to the Jeti forum where someone was trying get a clean per cell voltage solution.

[dl7uae]

OK, but we do not bring each single cell voltage into a telemetry except of HoTT GAM (and EAM) because the displays are fix existent (and very imprecise). We send a voltage alarm mapped on more other alarms sent by CVS to JLog (imbalance, undervoltage, weak cell etc) and value and number of the cell w/ the lowest voltage. Everything else is jewelry on the nightgown respectively there is no technical way to display it by a telemetry system. The full data set from CVS is subject of forensics (in JLog's log).

http://j-log.eu/jlog-in-funktion/sen...e-sensor-cvs16

[dl7uae]

production running

[swalko]

Hi Tom

IISI v2 is able to visualise up to 14 cell voltages including voltage drift. Do you think that it will be possible to send voltages from CVS16 to IISI V2 over MPX EXP-Gateway? Look on to 6th second of this video.

Cockpit V2 preview by IISI-RC.COM (2 min 12 sec)

If you want i can help you with testing on IISI V2.

[dl7uae]

Yes and no..
MSB knows 16 data addresses at max. We could use all 16 because there is no receiver occupying addr 0 (and 1 perhaps). Each could be of type "voltage".

If Matthias commits itself to support it I could implement it - to send all 16 voltages on the MSB.

[swalko]

So ... if it will be implemented ... and if i already use Kosmik + Jlog + EXP-GW i will need another EXP-GW and JLog to get data from CVS16 into cockpit?

[dl7uae]

No, the same JLog, w'd connect w/ its port COM to the EXP-GW.

[taosgraveyard]

Pumped about this, whether or not displayed on my jeti transmitter

Having an alarm means I would know to pull a log. That's good enough for me

[dl7uae]

- Ubat from ESC is automatically replaced by TPV (Total Pack Voltage) if a cell pack have been recognized by CVS.

If possible in the telemetry system in use - displayed on top:
- LCV (Lowest Cell Voltage)
- LCN (Number of the cell of LCV)
(Alarm on LCV by JLog, configured in JLC.)

Alarms mapped on Ubat voltage alarm:
- UC (Under Charge Alarm) at startup (before Imot is drawn)
- OOB (Out Of Balance)
- OOIRD (Out Of the average Inner Resistance of all cells of a pack -> weak cell)
(Alarms sent by CVS to JLog, mapped by JLog and given into telemetry/log/alarm lines. CVS parameterized by JLog, JLC->JLog->CVS.)

All other data in two log records for forensics - including four cell numbers regarding OOB and OOIRD.

Displaying:
We depend on the capabilities of each of the 8+1 telemetry systems.
In HoTTv4 GAM we have a 6S cell voltage display but do not use it. These displays are modulo 20mV. We use them for other purposes including LCV and LCN.
No good idea to send more than 15 data items into JETI EX telemetry although it w'd be possible (if the programmer knows about the trick behind ).

The difference of CVS compared to other cell voltage sensors: CVS does monitoring, is an intelligent sensor so to speak. Important is the result in practical use: Configurable alarms. All other is forensics in case of suspected/detected problems - by log inspection. So a JLog2.6GW could be no longer sufficient together with CVS because it does not log. (feature enhancement by enabler key needed)

-----
Of course we get more data items from CVS but some of them in log only:
LCN
LCV
TPV
MPV (max pin voltage - CVS in no-pack mode, 16-voltage sensor)
UC alarm
OOB alarm
OOB cell #1..4 (four single items)
OOIRD alarm
OOIRD cell #1..4 (four single items)
temperature (CVS16 onboard) Can be used to monitor the pack temperature, CVS mounted on a pack.
pin/cell voltage #1..16 resolution: 10mV in no-pack mode, 5mV in pack mode
(accuracy: 2.234mV -> rounding. 2-level temperature compensation for a 120-degrees range in application, at min (Celsius). Here is another difference to sensors from other manufacturers some of which only have 100mV analog accuracy, so have only 200mV practical (digital) accuracy. High resolution and reliability of measurements are required base for monitoring and statistical evaluation on cells that makes CVS.)

[Groucho_]

Originally Posted by dl7uae

If possible in the telemetry system in use - displayed on top:
- LCV (Lowest Cell Voltage)

That alone would be enough for me.

Everything else is an added bonus

[dl7uae]

Soon..

50 x 30 x 5mm, 6.4g

This is long past for me (for software development, finished in January). We apologize for the huge and pretty "artificial" delay. Our plans will be more accurate if we might be able in the future to spend our time exclusively with such things.
The front where I'm fighting currently: JLog as logger and telemetry gateway for DJI NAZA via an interface (bus/application router) used for that (C2T).

[Raptorapture]

Looks good Tom. Definitely want to try one out if nothing else but to see the impact to individual voltages during different flight and power conditions.

[dl7uae]

The first CVS were delivered. I'm curious...

(Oops.., big picture. Am too lazy for resizing.)

[Groucho_]

Is the user manual download active already somewhere?

[dl7uae]

Yes, for a long time, but only in German. It's an online manual as everything.

You do not need to know much to use CVS. Setup by JLC is self-explanatory. All alarms are mapped on the Ubat voltage alarm. It requires a different LogView device description as JLog26CVS or JLog26CC-CVS to view JLog's log files.