J-Log.eu - Forum

S32 (JLog3) (EN) • Re: S32 Jlog burned up

2019-07-01T19:32:16+01:00

dl7uae hat geschrieben:

Hi!

Apologies for the huge delay! OMG..., Feb 15 ...

[...]

Hmm.. (again).. Drop me your postal address by PM. I will ask the distri MHM if they are willing to help.

Hi Tom - I just saw your response just now. I had long since given up on any support and have thrown my burned S32 in the trash. I'll send my postal address separately in case there's anything we can do. Would still like to get telemetry from the Mezon to my Spektrum DX9 radio.

Steve

Statistik: Verfasst von spennyS2B — 1. Jul 2019, 19:32

S32 (JLog3) (EN) • Re: S32 Jlog burned up

2019-04-27T17:33:53+01:00

Hi!

Apologies for the huge delay! OMG..., Feb 15 ...

Actually, quite impossible to burn it by the SRXL connection..

I even once tested for someone at Helifreak what the maximum supply voltage is in practice. Went up to 21 volts, stopped at this point , S32 still alive.
Of course, this voltage would a data pin not survive.

So, sorry, no idea how you could manage it...

Hmm.. Open the housing, let it heat up, find out which component getting hot.
This may give us an idea what is damaged, maybe also about the cause.
But.. makes not really sense for you. You just and only need a working S32.
Hmm.. (again).. Drop me your postal address by PM. I will ask the distri MHM if they are willing to help.

Statistik: Verfasst von dl7uae — 27. Apr 2019, 17:33

S32 (JLog3) (EN) • S32 Jlog burned up

2019-02-15T04:12:06+01:00

I seem to have burned up my JLog S32 before ever flying it and wondering how this could have happened.

I bought the S32 from someone on the web. I successfully used S32Terminal to configure it to receive telemetry from my Jeti Mezon ESC and send it to a Spektrum AR9030T receiver via SRXL. The lights lit up and S32Terminal could both write and read the configuration data.

Per S32Terminal's instructions, I connected S32 Port 3 (the top row of servo connector pins) to the receiver's SRXL port. I connected Port 2 (the middle row of pins, between Port 3 and the JST ports) to the Mezon's red telemetry plug, with the power (middle/red) wire cut so the Jlog would not receive power from the ESC. All according to the diagram displayed in S32Terminal.

The Jlog lit up fine when I powered on the receiver. But it did not send any data to the transmitter so I disconnected it and brought it back to my PC to try reconfiguring it to use X-Bus instead of SRXL. Once connected to the PC, I reconfigured the Jlog in S32Terminal. When I came back to the Jlog a few minutes later, it was quite hot to the touch. Since then, the lights have not come on and it does not connect to S32Terminal. The electronics seem to have burned up.

Did I do something wrong that could lead to the S32 burning up?

Is there documentation that I might have missed, that could have prevented this if I had read it?

Or could there be a different cause?

Statistik: Verfasst von spennyS2B — 15. Feb 2019, 04:12

S32 (JLog3) (EN) • S32 + HeliJive 120+HV + Pyro 700-45

2018-12-03T14:00:22+01:00

Hello,

I have a question.

I am using the following setup:

ESC: HeliJive 120+HV
Motor: Pyro 700-45L

Motor Pinion: 13T
MainGear: 110T

Battery: 12S

Logger: S32_2

Further information:

TRX: Frsky Horus X10S with OpenTX 2.2.2

The HeliJive is programmed with mode 4.

The S32 Logger is programmed with
Motor: Pyro 700
ESC: Jive/HeliJive
Pinion: 13T
MainGear: 110T

With throttle at 85% the S32 logger logs RPM speeds of 2400-2500Rpm
I find that a bit high also the sound coming from the Heli doesnt sound like that kind of RPM's
I could be very wrong, but I have my thoughts about this.

Any Experience with this setup?

The Logger is connected to the SmartPort of my Frsky X8R receiver.
The plain RPM's are double that of the S32 logger itself.
I had to set the blade number to 2 in the Telemetry setup page of the RPM sensor to get the same RPM reading as the S32 logger.

Statistik: Verfasst von pd5dj — 3. Dez 2018, 14:00

S32 (JLog3) (EN) • Re: Pixhawk/ArduCopter and Jeti

2018-07-07T14:25:34+01:00

Hi!

Sorry for the huge delay!

Nope, currently HoTT only. Pixhawk was some time just and only a favor for Ralf from Graupner.
One day I will have time again for development for RC...

Statistik: Verfasst von dl7uae — 7. Jul 2018, 14:25

S32 (JLog3) (EN) • Pixhawk/ArduCopter and Jeti

2018-06-03T00:04:59+01:00

Does the S32 not support Pixhawk/Arducopter telemetry with a Jeti Rx? Thanks!

Statistik: Verfasst von davidbitton — 3. Jun 2018, 00:04

S32 (JLog3) (EN) • Re: Kontronik JIVE 100 LV

2017-02-13T22:59:04+01:00

OK, I believe you...

so let's try....

Statistik: Verfasst von cdric — 13. Feb 2017, 22:59

S32 (JLog3) (EN) • Re: Kontronik JIVE 100 LV

2017-02-13T20:35:31+01:00

Because it's you

S32 + JIVE 100LV

log file header:

Quote:

S/N R2F01208 hardware version 3.0.4
(device marked as QC and functional tests passed)
Monday 02/13/2017 20:25:31 (mmdd20yy-24h RTC) S32T language: English
S32 (JLog3) R2prototyping You think of it, we make it. http://r2prototyping.ch http://j-log.eu
Support: http://support.r2ag.ch http://www.helifreak.com/forumdisplay.php?f=257 http://j-log.eu/forum
devID:00416609 enabling:F firmware bootloader:1.9 app:1.33 | BOR3 wu|sb|pvd|brr|VOS Vs/3:0.31V (3=0.31V 4=5.54V 8=0.17V)
SETUP name:"Cedric" esc:<JIVE> tel:/box: poles:10 ratiotype:2 (ratio:1:10.0 pinion:0 maingear:0) l/s:1/1 shunt:0
Sensor Fusion HV2BEC:0/0 CVS16:0/0/0 BID:0 C200:0 Temp:0 Volt1:0 Volt2:0 Pulse1:0 Pulse2:0 RPM:0 Pspeed:0 Gspeed:0 Aline:0/0 Morse
Alarm Thresholds cap:0 capPl:0/capPh:0 capR:0 ubat:0 ubec:0 tfet:0 tbec:0 imot:0 t1M:0/0 t2M:0/0 t3M:0/0 erpmm:0 erpmM:0 spdm:0 spdM:0
Enjoy your Hobby!

$1;1;0.00;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0
$1;1;3.88;0;0;0;0;250;0;0;0;0;0;0;0;0;0;29;0;29;0;0;0;0;0;0;0;0;0;0;0;0;0;0;-999;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0 JIVE fw version: 09
$2;1;3.88;30;30;555;16;0;0;0;0;0;29;0;0;0

Statistik: Verfasst von dl7uae — 13. Feb 2017, 20:35

S32 (JLog3) (EN) • Re: Kontronik JIVE 100 LV

2017-02-13T19:57:21+01:00

Shop, Kontronik... Ask your hairdresser.

This is the manual page for the JIVE, old as the coal, for JLog2.0, 2.5, 2.6. JLog2.0 came 2011: http://j-log.eu/jlog-in-funktion/sensoren/esc/jive
What do you think why speaking about ImotShunt, mAh etc..?

This is the archive for JLog1, 2010, older as the coal: http://j-log.eu/archive/past/old-jlog1/datenauswertung
What do you think where "I-Motor" comes from?

The sensor for measuring of Imot in the JIVE is a well-known topic for 7 yrs..
- because it is only a trace on the PCB, uncalibrated, not temperature-compensated (JLog does it afterwards)
- because it is measured in a motor phase line: PWM duty and frequency interfere with the ADC conversion time. Result is: It delivers house numbers. (Jlog converts the house numbers to real current values) Look: http://j-log.eu/jlog2-en/faq/imot-shunt-with-jive-and-overall-mah-accumulation

You probably noticed already: Made with a JIVE 100LV

- Ibec (BEC output current) is measured as RDSon in a JIVE. There is a FET switch behind the BEC. The drain-source resistance of the FET is the current sensor.
Btw: The JIVE Pro does not have this switch anymore but an ideal diode. Same in a KOSMIK. The diode is instantly on after powerup whereas the switch in a JIVE is later activated by a 2nd MCU, ATMEL ATmega168. So there is the reason for the "BEC design flaw" in Jpro and KOSMIK. The actual cause is already existing in the old JIVE. Only, it couldn't come to that negative effect because of the delayed switching, the BEC starts load-free.

JIVE Pro has no sensor for Ibec (BEC output current) but the KOSMIK has: a 1 milliOhm resistor plus op amp.

Statistik: Verfasst von dl7uae — 13. Feb 2017, 19:57

S32 (JLog3) (EN) • Re: Kontronik JIVE 100 LV

2017-02-13T19:14:28+01:00

Hi,

Oui c'est clair....

The documentation is really clear for me.

But I ask the question to a german shop, and he answered me: The JIVE 100 LV do not have any sensors, only the HV PRO version and the KOSMIK have sensors.

Have you tried the S32 with a JIVE 100 LV? is there a video available somewhere?

I also asked directly to Kontronik, waiting for the answer. It will definetely close the topics

Sorry to insist, but I want to be sure before use my budget

Statistik: Verfasst von cdric — 13. Feb 2017, 19:14

S32 (JLog3) (EN) • Re: Kontronik JIVE 100 LV

2017-02-12T22:46:01+01:00

D'accord?

Statistik: Verfasst von dl7uae — 12. Feb 2017, 22:46

S32 (JLog3) (EN) • Re: Kontronik JIVE 100 LV

2017-02-12T22:15:10+01:00

Oui, oui, oui, nous obtenons des données pour l'électricité à partir de JIVE 100LV. Moteur et BEC.

Statistik: Verfasst von dl7uae — 12. Feb 2017, 22:15

S32 (JLog3) (EN) • Re: Kontronik JIVE 100 LV

2017-02-12T22:00:18+01:00

No current sensor? Where is that claimed? It w'd in any case be BS. Current sensing for motor and BEC output.

See the table.

Quote:

If you have, do not hesitate to share

I have and I shared it. That's it.

You're confusing me a bit.. Are you confused by the symbols in the table?

"X" == YES, have it
"-" == NO, don't have

Statistik: Verfasst von dl7uae — 12. Feb 2017, 22:00

S32 (JLog3) (EN) • Re: Kontronik JIVE 100 LV

2017-02-12T21:42:44+01:00

Hi,

Yes I saw the table for each ESC.... I was just asking because I've seen that the JIVE LV 100 (http://www.kontronik.com/en/products/sp ... 00-lv.html) do not have current sensor...

I was unable to find information about sensor for this ESC...

If you have, do not hesitate to share

Statistik: Verfasst von cdric — 12. Feb 2017, 21:42

S32 (JLog3) (EN) • Re: Kontronik JIVE 100 LV

2017-02-12T20:51:40+01:00

Cedric,

Yes, this JIVE is supported as well. (no wonder, 7 yrs ago JLog1 started with that ESC ) All "JIVE"s before the "JIVE Pro" are supported as well, no matter if an addon like "power" or "heli" appears in the name.

Generally, check this http://j-log.eu/s32/s32-en

Here http://j-log.eu/s32/s32-en/s32terminal/ (as well as in the terminal in "step by step" --> "ESC/FC info: data items") you'll find amongst other things this table:

Statistik: Verfasst von dl7uae — 12. Feb 2017, 20:51