Kosmik+Jlog 2.6+ Jeti

[Puttputt maru]

I am in with my first Kontronik Kosmik, my first Jlog but not my first Jeti as I usually fly with a Mezon ESC.

I have looked around the forum most info is dated but not necessarily out of date. Just in case any particular advice or new things I should be looking for in my set up?

Thanks.

[dl7uae]

Hi!

No, nothing special. Only, it could be that you have to pull the plus wire in the harness JLog--KOSMIK, use an Optipower BEC Guard and supply JLog together with all other electronics from the output of the Guard. Use JLog's "JIVE port" to supply em alternative way. See the online manual on the JLog home page, chapter sensors-->ESC-->KOSMIK/JIVEpro.
This is due to a powerup design flaw of the BEC of these ESC's.

Everything else is straightforward. Don't forget to pull the plus wire in the servo cable connection JLog--receiver.



Note a new firmware bug in KOSMIK firmware 4.6 and use the JLog firmware with a workaround for that, marked "kwa46". See the 2.6 firmware downloader.

Unfortunately KOSMIK and JIVEpro still do not send Ubec(V), throttle(%), effective throttle(%, incl bailout offset), timing(°).

Btw, did you know that JLog is also supporting your MEZON as ESC acting as virtual sensor device?

[Puttputt maru]

Thanks for the heads up on the work around I will keep it in mind.

Looking forward to learning a new device and set up. I will probably have more questions as I go along.

[orthobird]

i just got mine! I let you know if it works. I am using Kontronic 200, Jeti DS 16, and BD 3SX, seems like i have to undo the red wire from the plug from "COM" to the EXT port on the r3 Rx?

[dl7uae]

seems like i have to undo the red wire from the plug from "COM" to the EXT port on the r3 Rx?

Yes, you have.
Reason: for other applications we have serial Tx on the "signal pin" but serial Rx is not fix connected to Tx to form a 1-wire bus than it is connected to the center pin which normally is plus supply voltage in. Software-controlled we short-circuit Rx with Tx if we need a 1-wire bus.
So.., if you'd connect plus from receiver to the center pin of JLog's COM port - it w'd land on serial Rx==Tx, disturb the bus an worst case destroy the processor if the voltage exceeds 6 volts.

You have a KOSMIK, the one with the BEC design flaw which may lead to "crazy voltage" at powerup..

Do the following: pull the plus wire in the harness JLog--KOSMIK.
Pull the red wire in the servo cable receiver--JLog(COM) on JLog's end and put em on the inner ("signal") pin of JLog's "JIVE Port", which in plus supply voltage input.

Best w'd be to use an Optipower BEC Guard between the BEC (master+slave!) and all supplied electronics -- including JLog by the above described mod.

[orthobird]

got mine to work!

Jlog 2.6 to Jeti R3 to Jeti DS 16 to Kontronic Kosmic 200 ESC
The instructions are not the best.

1. using the male to male JR type extension, connect the com from Jlog to the "ext" on the jeti R3 Rx. Must cut red wire.

2. connect the blue from Jlog to the Kontronic data port

3. go to your computer and download these two:

http://j-log.eu/wp-content/plugins/JLog26/dl26.php

&

http://j-log.eu/wp-content/uploads/common/JLC7.exe


then insert SD card or USB extension with micro sd card, open it up, then transfer those two files onto it, then eject,

insert the programmed micro SD card into the Jlog 2.6

turn on your system


go to Jeti Tx, and configure sensors

then go to display telemetry and pick what you want to display


that was it!!

[dl7uae]

Well.., I admit: the description got cryptically because of the above mentioned mods.

... I do not invent the bugs and flaws of others..

These additional mods are just a precaution.
That thing is based on a racing condition, so entirely unpredictable how and if it happens. May be nothing bad happens w/o the mods w/ your copy of a KOSMIK, in your setup.
Just try it.

The originally only necessary measure, clearly described in the manual, is to pull the red wire in the connection COM--receiver (telemetry).

[Puttputt maru]

Thanks guys for all the info..I am still waiting for my Triabolo so this is just gathering info for now and this is most valuable.

[john2kx]

[QUOTE=orthobird;6645820]got mine to work!

Jlog 2.6 to Jeti R3 to Jeti DS 16 to Kontronic Kosmic 200 ESC
The instructions are not the best.

1. using the male to male JR type extension, connect the com from Jlog to the "ext" on the jeti R3 Rx. Must cut red wire.

2. connect the blue from Jlog to the Kontronic data port

3. go to your computer and download these two:

http://j-log.eu/wp-content/plugins/JLog26/dl26.php

&

http://j-log.eu/wp-content/uploads/common/JLC7.exe


then insert SD card or USB extension with micro sd card, open it up, then transfer those two files onto it, then eject,

insert the programmed micro SD card into the Jlog 2.6

turn on your system


go to Jeti Tx, and configure sensors

then go to display telemetry and pick what you want to display


that was it!!

Ortho,

After spending two days trying to get my 2.6 jlog, kosmik 200, DS16 and R9 rx working using the instructions provided by Tom, I thought I would try your method. It sounded easy enough but no joy for me.

What I found different in your method (the way I understand it) is that you down loaded the kosmik/jeti file "as well" as the JLC7 onto the SD card, inserted the SD card into the jlog and you were up and running.

Did you have to wait some period of time before your Tx picked up the telemetry, as I have seen this in the past when changing ESCs, adding temperature probes, GPS etc.

I cut the red comm wire and the flashing lights on jlog appear to go through their stages, followed by the green light flashing by itself after several seconds. SD card was reformatted prior to start. Comm line is plugged into bottom right set of pins on jlog.

Would my R9 vs your R3 make a difference?

At this stage, if I did not have so much $$$ invested in the kosmik I'd slip my mezon 130 in and call it a day.

John

[TeroS]

JLC is a windows-program. that is not needed on JLog SD-card.

It kinda looks like one or more of three things:

- You did not configure JLog, only updated firmware
- Issue with cable from JLog to R3?
- Issue with R3 port?

Edit: Yes, it takes some time for telemetry-sensors to appear, you did press the update in transmitter, right?

[john2kx]

CP,

To be clear, I am using a R9 rx. Perhaps in my many efforts to verify the jlog was working, I did not allow adequate time for Tx to pick up new telemetry info. Each time I tried a different method of files installed or removed from the jlog SD card, I checked Tx screen within a few seconds and did not see any telemetry data...and then would try a different method.

I'm powered up now and will give it 15 minutes or so and see what happens. Just ordered a progunit as it looks like this is a piece I'll need now or in the future for the kosmik.

I asked for help on another post and received a prompt reply Tom. Evidently, I did not make it clear that I was not a computer guru. I have read many of his posts in the past and several of yours recently and can tell both of you guys are way out of my league when it comes to using computers.

Some of the things that have stumped me right out of the gate:
-the transfer of the two bin files from jlog to the SD card. I believe I loaded the correct files but am not clear on how to properly alter them prior to removing them from SD card.


These are the instructions provided:

"Firmware on JLog flash:
Copy the downloaded file (firmware) on the MicroSD, namely "top", ie in's root directory, not in a subdirectory. Insert the SD in JLog and enter this operating voltage. The red LED lights JLog, then starts flashing for about 15 seconds. Then JLog starts the application is ready for use.

Verify JLog has flashed the correct firmware by selecting "version.txt" read the file on the SD.

Never leave you more than a firmware file on the SD, JLog would otherwise reflashen each time with a different firmware! It is best to delete the firmware file after flashing again.

Start all firmwares and also operate when no SD is inserted, can be just logged then not, of course."

End of instructions.

I believe the translation is killing my efforts while trying to interpret the above, combined with my lack of understanding file transfers, root directory and sub directory.

I did manage to get JLC7 downloaded and inserted my gear ratio, kosmik/jeti info and clicked "load". I assume this went to the SD card.

At this point, I do not even know which version kosmik I have, although it was just purchased 3 weeks ago. I was instructed to read the kosmik SD card after the first spool up (to obtain version #) without success and just found there is a file that needs to be downloaded (available from kontronik) to read the card. I will do that later today.

I have spent 3 days now trying to get jlog to work and believe I'll spend the rest of the day moving on to test hovering my new heli without any telemetry. I know the kosmik is a fine esc and the jlog is needed to make the telemetry work. Just wish there was a youtube video made for computer dummies like myself. I think the video would only last about 3-5 minutes as there are not very many steps to perform...they just ALL have to be correctly, in the right order.

John

[Puttputt maru]

Altough I am not sure what you are doing wrong, have a look at:

https://markkovalcson.wordpress.com/...smik-and-jeti/

It might help you it is pretty much step by step (it is for 2.5 but 2.6 is pretty much the same)

[john2kx]

Hey Eric,

I book marked Marks thread when he posted it and tried to use it during my process without luck. Being a software developer, I believe Mark did not run into the down loading of bin files in the exact location, then editing some text before transferring that I believe is my biggest problem.

[dl7uae]

Ummm...

the transfer of the two bin files from jlog to the SD card

Not two, ONE! Depending on your firmware version of the KOSMIK, if <4.5 or >4.5 (bug), you select the JLog firmware without or with the workaround.

End of instructions.
I believe the translation is killing my efforts while trying to interpret the above, combined with my lack of understanding file transfers, root directory and sub directory.

Uhh.. this Google translation is from START. Why don't you read the English part?

I provided you already with both exclusively ALTERNATIVE firmwares for JLog. How flashing works, you've already figured out. How to check the result (check version.txt), also.

Ok, so you just need to install JLC (should be easy, is a self-extracting/installing .exe), start it (runs already after initial install) and load the CONFIG.txt JLog has created at 1st run. JLC is a Windows program!

So modify the setup according to your needs (telemetry on, pole #, ratio, alarm thresholds) and save back to the SD. JLog will learn the settings at his next startup.

So what..

A JETI Tx needs some time to learn all displays of a sensor, especially because of a long-term bug in transmitter firmware: it needs several attempts until the Tx learns also the first data item from JLog, "Ubat".

Anyway.. what is the current status your end?

(Red wire has been removed from the servo cable JLog/COM--receiver?!)

[TeroS]

Give me your gear ratio and I'll make the config.file for you.

So, you should have only the one correct .bin file on your SD, also the config-file is done with JLC.

There's a bug in Kosmik's current firmware (4.6 and 4.8), in order to get the correct rpm reported to Jeti you need to set it as follows:

Kosmik setup
- Motorpoles to what your motor have
- Gear ratio to 1:1

JLog setup
- Motorpoles = 2
- Gear ratio to what you have, for example in my Logo 800 it's 1:9.72

Let me know if You need any help?

I need obviously do a step-by-step write-up about this someday, the same questions are asked quite a lot with kosmik these days.

[TeroS]

Originally Posted by dl7uae

...So modify the setup according to your needs (telemetry on, pole #, ratio, alarm thresholds) and save back to the SD....

Usually no alarms are configured in JLog when used with Jeti TX since Jeti is more versatile whit programming possibilities regarding telemetry-alarms.

[dl7uae]

Usually no alarms are configured in JLog when used with Jeti TX since Jeti is more versatile whit programming possibilities regarding telemetry-alarms.

Okay but depends..

Sometimes it is better if the alarm source is a state machine, for example:
- mAh alarm stops or comes less frequent if pwm or throttle is below 10% (motor off)
- no Ubat alarm in case the main battery is disconnected for replacement - on base of stopped data stream from ESC

Text mode users, usually multicopter not helicopter pilots, benefit from a popup page if the alarm situation has changed. That needs alarm thresholds defined in JLog.

JETI has the most flexible telemetry. In other systems, it is of much more dramatic, JLog MUST generate alarms themselves, even when the telemetry system does not accept alarms from sensors.

[john2kx]

Originally Posted by CP-Geek

Give me your gear ratio and I'll make the config.file for you.

So, you should have only the one correct .bin file on your SD, also the config-file is done with JLC.

There's a bug in Kosmik's current firmware (4.6 and 4.8), in order to get the correct rpm reported to Jeti you need to set it as follows:

Kosmik setup
- Motorpoles to what your motor have
- Gear ratio to 1:1

JLog setup
- Motorpoles = 2
- Gear ratio to what you have, for example in my Logo 800 it's 1:9.72

Let me know if You need any help?

I need obviously do a step-by-step write-up about this someday, the same questions are asked quite a lot with kosmik these days.

I'm still pounding away, feel I'm getting closer but not there yet. Pic might show where I am...kind of.

My gear ratio is 7.44:1
Motor pole: 10

[john2kx]

And this is how my equipment is looking powered up with a 6S pack. Green light is flashing on jlog.

[TeroS]

Do you have a ProgUnit for Kosmik to set polecount? (This is for rpm)