Need help with Jlog2.5/Futaba14SG telemetry

[cmdkeen]

Hi There

I'm having problems getting the telemetry working on my new JLog2.5 to my Futaba 14SG

What I have done so far:

1) Update JLog2.5 with "25-J_Fc-163.115.bin" firmware and configure CONFIG.txt with JLC to match the gearing of my heli
2) Connect to my Heli Jive and verify that data logging works on SD card - Works OK

3) Connect SBUS2 to my Futaba 7008SG receiver.
4) Configure CONFIG.txt with JLC to SBUS2 and activate the "R" register function
9600,0,128,10,0,9,7,14,127,0,3,0,0,0,0,0,0,0,0,0,0 ,0,0,0,0,0,6,0,0,5,16,16,16,16,16,16,16,16,16,16,1 6,16,16,16,16,16,20,163,0,0

5) Power on the heli and rebind 7008SG to my 14SG in FASSTest-14CH SINGLE G mode
6) After a power cycle the telemetry still only shows internal and external voltage from the 7008SG. All other parameters does not register.

I tried changing ID's in the "SENSOR" menu but no change
Did I miss something ?

[dl7uae]

Please read the manual of your Futaba equipment.

Registering a sensor is done by connecting the sensor to the transmitter. JLog forms 8 sensors, so you have to register 8 times in one session!

Set the R flag, then register, then reconnect to the receiver and reboot JLog.

JLog needs power during registration!

That all is already explained in the forum here, please look for it.

[Magneto]

Originally Posted by cmdkeen

Hi There

I'm having problems getting the telemetry working on my new JLog2.5 to my Futaba 14SG

What I have done so far:

1) Update JLog2.5 with "25-J_Fc-163.115.bin" firmware and configure CONFIG.txt with JLC to match the gearing of my heli
2) Connect to my Heli Jive and verify that data logging works on SD card - Works OK

3) Connect SBUS2 to my Futaba 7008SG receiver.
4) Configure CONFIG.txt with JLC to SBUS2 and activate the "R" register function
9600,0,128,10,0,9,7,14,127,0,3,0,0,0,0,0,0,0,0,0,0 ,0,0,0,0,0,6,0,0,5,16,16,16,16,16,16,16,16,16,16,1 6,16,16,16,16,16,20,163,0,0

5) Power on the heli and rebind 7008SG to my 14SG in FASSTest-14CH SINGLE G mode
6) After a power cycle the telemetry still only shows internal and external voltage from the 7008SG. All other parameters does not register.

I tried changing ID's in the "SENSOR" menu but no change
Did I miss something ?

As Thomas said you haven't registered yet! But if you messed up the Telemetry or forgot the slot locations by changing Ids or slots you can always reset theTelemetry in the radio before Registering by going to Data Reset in the linkage menu and selecting Telemetry only reset! My first attempt was failure as I used the wrong Bin file and when I went to reregister I couldn't because of the exsiting sensors so I reset and Bingo !

[wblombard]

Steps 1 to 2 is perfect....from there do the following:

Make sure your TX has the latest software update...go to futaba web site and see update procedure... I know they just released version 2.0...Tom justs needs to confirm if this software works with J.log 2.5

Ok once that is done do the following.

On JLC start over....as you did in step 1 with the R button...you need to set up your TX....there is a plug in the back of your transmitter....

Now i dont know this off the back of my mind, but refer to the futaba manual..think its page 133...where once you plugged in the reciever cable that was connected to the R7008SB to the back of your TX...(NB NB....disconnect the red wire from your receiver plug...you dont want power on this cable into your TX, you dont need to replace it after wards) So switch of TX plug in cable...power on TX

Once the above has been done, go to the setup menu in your TX...and register...the registration you have to do 8 times...on the ninth time it will give you an error....and boom done! easy!!

If you made a mistake do the whole process again...config file R button everything

PM me if you get stuck..I'll gladly talk you through it. Easier than writing this stuff down.

[cmdkeen]

Hi Thomas/Magneto/wblombard

Yep, I did read some posts of registering sensors to the 18MZ,
but somehow I totally missed the concept of physically attaching the sensor to the 14SG.
After reading and following the "SENSOR : REGISTER" chapter in the manual everything works like a charm

One additional question.
I am running a HV system so I did cut the power (red) wire between the JLog2.5 and the 7008SB to avoid having the Jive and my BEC fight over the voltage supply.
Is this necessary or is the SBUS2 power pin physically not connected in the JLog2.5 ?

Thanks

[wblombard]

As long as there is no power therefore red wire has been cut then all is fine...no need for anything else. No power must go from jlog to the RX....power to be supplied by BEC to RX and BEC to Jlog...connection from jlog to RX does not require power.

[Magneto]

Originally Posted by cmdkeen

Hi Thomas/Magneto/wblombard

Yep, I did read some posts of registering sensors to the 18MZ,
but somehow I totally missed the concept of physically attaching the sensor to the 14SG.
After reading and following the "SENSOR : REGISTER" chapter in the manual everything works like a charm

One additional question.
I am running a HV system so I did cut the power (red) wire between the JLog2.5 and the 7008SB to avoid having the Jive and my BEC fight over the voltage supply.
Is this necessary or is the SBUS2 power pin physically not connected in the JLog2.5 ?

Thanks

Thomas told me there is a diode there anyway so I left the red wire in the servo connector but maybe I should remove it incase of a diode failure ? Any thoughts Tom or Linus!

[dl7uae]

Our diodes never fail.

So, no worries, let the red wire in place.

The only reason why I said "remove the red wire" was: There're ~3.2 volts coming out of that pin (JLog2.5 S.BUS2 port). This is for voltage supply of an Unidisplay or in case of more than one JLog-own sensor connected, sensors who need supply voltage.

Only, I thought: Hey, if a user connects his Futaba Rx to the S.BUS2 port of JLog2.5 only - he will experience a working Rx on base of that (3.2 volts only!). What now if that user is crazy enough to connect servos to the receiver and trying to use that all without connecting a real voltage supply to the Rx?!

So.. I said that only to provide for the worst case.

[knightofcarnage]

can you get current consumption?

[dl7uae]

Of course, calculated by JLog.

[Raptorapture]

Followed all steps; however, unable to get more than receiver voltage which is showing as 7.9v. Kosmik set to 8.0v. Have upgraded T14SG to 3.0. Have gold dot version of R7003SB. Have used JLC v5 for JLog2.5. Have used latest S.BUS2 driver 25KFc93.109. Config file contains: 9600,0,128,10,2,9,39,10,10,0,2,0,30,7,5,80,1,27,0, 0,0,0,0,0,0,0,6,0,0,5,16,16,16,16,16,16,16,16,16,1 6,16,16,16,16,16,16,4,93,0,0.

Hope you can help. Thanks.

[dl7uae]

Could you register the 8 s.bus2 (Futaba) sensors formed by JLog? I mean, does the registering (JLog's s.bus2 cable in the back of the transmitter) work for you? Do you see the displays of these 8 sensors now under "sensors" in the T14SG? Also under "telemetry"?

[Raptorapture]

Yes, just no values coming out.

[Raptorapture]

Can only upload one pic at a time. Here's the live display:

[dl7uae]

OK.., concerning telemetry everything seems to be ok. No displays show "-----"?

Let's look for the other connection, - to ESC (KOSMIK).

Does the green LED of JLog blink very fast? KOSMIK has initialized? (seen throttle zero pulse)

Do you have a log file for me? (last lognnnnn.txt)

KOSMIK's firmware is at least 4.0?!

Did KOSMIK start with JLog connected to one of its option ports? That's necessary! KOSMIK scans for devices on option ports immediately after its startup. JLog has to be connected that time to answer as a TelMe.

[Raptorapture]

Originally Posted by dl7uae

OK.., concerning telemetry everything seems to be ok. No displays show "-----"?

Let's look for the other connection, - to ESC (KOSMIK).

Does the green LED of JLog blink very fast? KOSMIK has initialized? (seen throttle zero pulse)

Do you have a log file for me? (last lognnnnn.txt)

KOSMIK's firmware is at least 4.0?!

Did KOSMIK start with JLog connected to one of its option ports? That's necessary! KOSMIK scans for devices on option ports immediately after its startup. JLog has to be connected that time to answer as a TelMe.

Was thinking similarly re upstream but thought that might show through live telemetry. The log files are adding up. Numbered something like 7 to 15. Each one contains the same single line full of zeroes separated by commas with the first two elements proceeded by dollar signs. Was wondering if some logging activation is required. Kosmik connected to JLog2.5 however no quick flashing green. Only quick red then green then none. Earlier was a symphony of lights between red and green alternated with amber. Connection has been moved from one port to another to see if that was the problem. Kosmik upgraded to >= 4.0. Kosmik partially initialized, ie started range scan for gov by going to zero but did not go to peak to minimize impact to bearings on bench. Cheers.

[dl7uae]

Hmm.. If the green LED does not flicker then no wonder.. JLog does not receive the KOSMIK.

After the LED light show (it's just a "movie" during 5 seconds of wait loop against "crazy supply voltage") the red LED show never light up! red==error

Please follow this!

..and reformat your SD card with the formatter from sdcard.org!

[Raptorapture]

Originally Posted by dl7uae

Hmm.. If the green LED does not flicker then no wonder.. JLog does not receive the KOSMIK.

After the LED light show (it's just a "movie" during 5 seconds of wait loop against "crazy supply voltage") the red LED show never light up! red==error

Please follow this!

..and reformat your SD card with the formatter from sdcard.org!

The light show happened earlier when I was setting up, just not recently. Edit: correction - The red comes on for 2 seconds then goes out, amber then green plus red alternate a few times then green for one second then a quick amber flash. Will check the connection. Very difficult access in Banshee unless I remove Kosmik which I don't want to do again. I followed everything exactly as per your link, doing the post install setup many times. I will rerun from scratch again. I really dont believe it is format issue. Do you need to do anything on the transmitter when starting again or will it just happily overwrite/ignore successfully the attempt to recreate the sensors?

Cheers.

Edit: Started from scratch. Same result including after formatting as well.

[dl7uae]

then a quick amber flash

Huh?! W'd mean: No data from KOSMIK (no green flashing) but anyway log recording (amber flashing) because a JLog-own sensor is configured.

Please attach your CONFIG.txt again.

Hmm.., but you said that you have only one line per log file..

Do you need to do anything on the transmitter when starting again or will it just happily overwrite/ignore successfully the attempt to recreate the sensors?

Before re-registering delete ALL sensors from its registry!

Otherwise: Telemetry RX->Tx seems to work because you get data from the Rx as sensor (two voltages).

--------------
Oops! I forgot to ask: Which receiver do you use? Hopefully no R7003 w/o pulldown. Then it could be that the Rx can not read JLog's data from s.bus2.

Another "stupid" question: Are you sure to have JLog's s.bus2 cable in the right port of the Rx and also in the right orientation?
You can not imagine what I've experienced already in this respect..

... and of course: After registering JLog needs to be restarted (re-powered) to get data from him on its s.bus2 port. After registration JLog remains in register mode. With the next start he comes up in operational s.bus2 mode. (registering protocol and operational (s.bus2) are quite different from each other, - besides the baud rates, 9k6 vs. 100k)

[Raptorapture]

Receiver is 7003 but golden version with pulldown. Restarted logfile number as well as registering again. Logfiles attached:
CONFIG: 9600,0,128,10,2,9,39,10,10,0,2,0,30,7,5,80,1,27,0, 0,0,0,0,0,0,0,6,0,0,5,16,16,16,16,16,16,16,16,16,1 6,16,16,16,16,16,16,4,93,0,0
JIVEinfo: ? N.A.
version: 25-K_Fc-93.109
log00000: $1;1;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
log00001: $1;1;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

double checking cable now, edit: cable good.

Cheers.