Logview Program

[jcflyer]

In the logview program which parameter would represent the collective stick movements???

[dl7uae]

Huh?!

In the log from which device?

If you speak about JLog: The only very indirect reference is the motor current.

[jcflyer]

Hi Tom,
Yes from Jlog 2.5, so the motor current would most represent the stick movements?

[dl7uae]

Quite inaccurate.

Many other things come into play: Cyclic, reverse downwash (up to Vortex), wind, airstream, boost effects, FBL if between sticks and model, governor, ... Chocolate Santa Claus...

[jcflyer]

Ok Tom i get it chocolat santa claus, is there any way to tell stick position from the logs when using gov. mode?

[dl7uae]

is there any way to tell stick position from the logs when using gov. mode?

How is this to work?
We have a FLAT throttle curve.

Well.., in the past there were many special firmware for JLog2. One was logging two servo signals.

But:
a) It makes not much sense if we have a FBL system between sticks and swashplate servos. Also the mixing may be in between.

b) "Sum" signals: Alternatively PPM wouldn't be the problem. But all the other (newer) protocols have never been implemented by me: s.bus, JR's sum prot, JETI's, SJ's SUMD, Mikado's sum prot, ... and again the Santa

c) Too many firmwares --> confused users. It makes JLC, which is an "expert system", more complex. It requires more different device description files for LogView. etc.pp.

[jcflyer]

Well Tom,
I don't know that is why I asked you are the expert here!!! If it isn't possible ok fine I just didn't know never wanted to know before yesterday...

[mdu6]

How about having a sensor that would be connected in-line with the servo and would report back it's position to J-Log ?

I would want something like this so I would know how much the governor is pushing on the Nitro engine for speed. So I could read the engine RPM from telemetry and at the same time see that the governor is currently throttling the engine at 84% (for example).

[aziz76]

J-Log will report on any sensor that it supports and is attached. Stick positions is not supported. There are other systems that support this such as the Jeti transmitter which can log stick positions which can subsequently be viewed on logview. There may also be other transmitters that can do this, but to log stick positions from a device on the model is really not possible, closest thing would be logging receiver output signals (strictly speaking not the same thing, but close)

[mdu6]

That's what I want - receiver or more precisely governor output to the throttle servo - I have not seen this - hence the idea of having a dedicated sensor that would be inline between the governor and throttle servo

[aziz76]

That would be the equivalent of logging PWM % off an ESC on electrics. I definitely see the utility in that when tuning governor and head speed. I don't know of a device that would do that though. The most logical would be for that telemetry to come from the governor itself. I don't fly nitro but perhaps there is a governor out there that would do this.

[aziz76]

Originally Posted by mdu6

That's what I want - receiver or more precisely governor output to the throttle servo - I have not seen this - hence the idea of having a dedicated sensor that would be inline between the governor and throttle servo

I believe this will do what you need:

http://shop.rc-electronic.com/EAGLE-...=A22000&p=2337

[mdu6]

thanks for the find - too bad it's not integrated with some 3rd party radio telemetry system (at least now) ...

Well.., in the past there were many special firmware for JLog2. One was logging two servo signals.

Is this firmware version still available or can you bring it back because this is what I need ! ?

[dl7uae]

Which ESC, which telemetry do you use?

[mdu6]

Not ESC - but nitro engine

I just want to have the servo throttle position (which is driven by the vbar or spartan governor) feed back to my TX so I can view RPM and servo position (how much the governor is pushing on the engine). I would use a Y-cable between FBL unit throttle output and throttle servo to feed Jlog.

I do not currently have a telemetry capable TX - but will be choosing a new one soon (JR XG14, Jeti DS16 or DX18)

[dl7uae]

Jeti! JR is too poor for that (displays).

Ok, will make you a special firmware with two pulse inputs. Two or one?

[aziz76]

Now that is personalised service

You are awesome Tom!

[mdu6]

I can only think of one such use for the throttle - so one is enough !

Can you comment more on why the Jeti would provide better capability for this telemetry ?

Lastly - thank you !

[dl7uae]

JR: there're still only these 6 items for displaying:



At least: neither throttle nor pwm.

JETI: almost everything to display and very flexible.

OK.. because I have no desire for a special JLC: will fix use the "signal" pin on JLog's "OPT port" as pulse input, so the central pin will remain for JLog-own sensors, digital/analog temperature sensors, speed sensor, eventually rpm sensors also.

Do you have any intention to use one/some of them?

Now the last question is: which unit to use for display of the pulse length? We measure microseconds, something between 0 and 3000 (center pulse width is 1520us). If you want to have a normalized representation, e.g. 0..100%, then the question is: what pulse length is zero?

[mdu6]

Yes I was thinking to use the RPM sensor (hall effect) from my Spartan Vortex (Y cable also) to feed RPM to the JLOG - so both throttle position and RPM would be provided by the JLOG. But I could also use the TX own capability for that purpose - what do you think ?


The Spartan specification is for 1520us centre pulse - so go with that and a normalized display (-100-0-100) or (0-100).

Thanks for the details on the telemetry (JR-Jeti) - what about the DX18/TM1000 capability ?