Hi everybody! (Introduction to this board)

[dl7uae]

Aha...

[dl7uae]

@beans07

Unfortunately they are out of stock but I will wait until they come in.

Hmm..., sure? Just did an order there (except of the last click ), no "out of stock".

Well, the light is yellow but - who knows... Never saw a green light there.

Tom

[dl7uae]

Hi Tom.
Okay, i might have use for voltage sensor in 2-3 months. (i will have 8.4V BEC for electronics).

Petr, would be the following okay?

max. 12.8V, 12.5mV measurement resolution, 100mV log/display resolution, logged/displayed as "extTemp0" (°C)

voltage devider: -----|--4R--|--x-----------------> to JLog 4-1
..............................................|
.............................................---
..............................................i
.............................................R
..............................................i
.............................................---
..............................................|
...........................................----- GND

Resistors of the devider: For example 40k/10k, metal film resistors.

Tom

[jointer]

I think it would.
When i will have external BEC (Western Robotics Super BEC), will i need to connect ground with Jive?
I think the Jive is not opto isolated?

[dl7uae]

will i need to connect ground with Jive?

Yes.

No OC.

Attention, OT: Why WR? Because of a higher output voltage?
(If I look at the tiny cooling of the WR's and then read the specs... Even with an outstanding good Eta... - there're limits with buck regulators at higher input voltages - ... The physics does not twist. Well, it will work, but not if understood as continuous current.)

[jointer]

Yes, voltage for HV servos, 8.4V regulated.
As side effect, it should transfer some of the heat out of the Jive to WR. Maybe.
The Jive have different type of regulator?
I know one issue, when the WR shut down because of overheating in very hot weather.
So it will be mounted on a spot where should be some airflow.
There is no airflow under the TDR canopy.
My logged max servo current spike was 8.5A and the HV servos will be these Hitecs:
http://hitecrcd.com/blog/
I plan connecting them first to Jive to log the current demands.

[dl7uae]

The Jive have different type of regulator?

No, switching type.

Two years ago I played with buck reg's for R/C application, 10A continuous (7x24) 12..14S. So I know about dissipation loss... Burned them regularly after a time in short circuit tests if the input voltage was above 12S. Gave up then, do not need that personally, was the time a bit too cost expensive for me to experiment with that only just for fun.

[jointer]

But if you do not trust them at 12S-14S, then only solution is separate battery.
Not much space for that in TDR.

[beans07]

Originally Posted by dl7uae

@beans07

Hmm..., sure? Just did an order there (except of the last click ), no "out of stock".

Well, the light is yellow but - who knows... Never saw a green light there.

Tom

Thanks Tom I went by the light. I will put an order.

[dl7uae]

But if you do not trust them at 12S-14S

Who is "them", WR?
I do not have any experience with WR, so I have no opinion.

@beans07
Meanwhile I asked Lindinger if the yellow light means "out of stock". Yes, it does.

But "Der-Schweighofer" seems to have in stock and speaks also English: http://www.der-schweighofer.at/artik...ve_datenlogger

Tom

[jointer]

Them...
If i understood right, the BEC in Jive and WR is the same type, switching regulator.
WR is most favorite and reliable brand, definitely better then Castle BEC.
WR Super BEC is about 1/3 size of Jive, so i think (and hope) it is built to the specs.

[dl7uae]

We have a new configurator JLC4 (version 4.0.0.4), One-for-All, JLog 1 2.4 ... 2.6[.n], JLog1 2.7[1], JLog2 3.1, the new 3.2 and 3.3 A/B ("JTX", homebrew JLog telemetry with XBees), as well as the Powercroco CMT JLog1 setup.

Although there is no version marker contained in CONFIG.txt and it wouldn't be possible to integrate that subsequently in the different firmware flashes, JLC4 is almost unerring in recognizing the version during the read-in of the config file. Only JLog2 3.2 can be misjudged as 3.1 if the type of alarm line #1 is "switched" (and not "interval" or "flash" or "Morse") and "telemetry" is not Unidisplay.

The challenge was a JLC for version 3.3 (D.I.Y. telemetry with XBee), but it was a wish of a user to have also one JLC for both, JLog1 and 2.

Voila.

Tom

[Heli G]

Originally Posted by dl7uae

We have a new configurator JLC4 (version 4.0.0.4), One-for-All, JLog 1 2.4 ... 2.6[.n], JLog1 2.7[1], JLog2 3.1, the new 3.2 and 3.3 A/B ("JTX", homebrew JLog telemetry with XBees), as well as the Powercroco CMT JLog1 setup.

Although there is no version marker contained in CONFIG.txt and it wouldn't be possible to integrate that subsequently in the different firmware flashes, JLC4 is almost unerring in recognizing the version during the read-in of the config file. Only JLog2 3.2 can be misjudged as 3.1 if the type of alarm line #1 is "switched" (and not "interval" or "flash" or "Morse") and "telemetry" is not Unidisplay.

The challenge was a JLC for version 3.3 (D.I.Y. telemetry with XBee), but it was a wish of a user to have also one JLC for both, JLog1 and 2.

Voila.

Tom

Thanks Tom, it’s great to see the progress you’re making. Now if only Futaba can release that new telemetry TX!!

[dl7uae]

Let's hope that the display, the appearance of sensor data and its setup, will be as flexible as the S-Bus itself is or will be...

[Heli G]

Originally Posted by dl7uae

Let's hope that the display, the appearance of sensor data and its setup, will be as flexible as the S-Bus itself is or will be...

+1

[jointer]

We have a issue, Tom.
Jeti telemetry.
Sometimes, when the system is powered up, the JetiBox mini will start in JLog2 configuration mode, showing incorrect settings. We can exit the config and after entering it again, everything is right.
Latest 3.2 firmware.
We will test tomorrow again, because we done only 2 flights due to high wind, but it happened in roughly 40% of power-ups.
Edit: capacity check against EagleTree also tomorrow, i hope.

[dl7uae]

The "issue" is well-known, Petr, we already tried damping it by some provision in the firmware - but the chances for the logger are marginal. JLog cannot differentiate who it was sending acknowledge/keycode over the terminal bus.

It seems to be a bug in the firmware of the JETI Tx module. Keys, never depressed for the JLog, go through if connecting to Mx.

In most cases of that "issue" the logger landed in jbJLC - but sometimes in a strange manner that all values displayed are wrong.

The easiest way to avoid this is to have throttle a little above zero, at 1% for example.

Tom

[dl7uae]

mAh...

Petr, a bit too late for your today tests, sorry.

Look here under mAhrs....

Tom

[Vinger]

Hi Tom, I am a little confused about the firmware versions. Currently running v3.2_3.29 and this works fine. I do not have any telemetry connected to it and purely use it as a logger. Should I follow the two step procedure to upgrade to 3.30?

[jointer]

Thanks for help Tom, we will try that throttle thing next weekend.
From this weekend we have this mAh tests with the previous firmware:
2055mAh from JLog2 discharged
2260mAh EagleTree discharged
2380mAh Tema SCD 300 charged back (no balancing).
Type of flying was easy flying with some soft 3D.

I can confirm the JLog captures higher current spikes, Eagle logged around 93A and JLog spike was 107A.
BTW what is difference between I-motor and I-motor/Int?