START HERE |
|
Register | FAQ | PM | Events | Groups | Blogs | Calendar | Mark Forums Read |
Unregistered
|
JLog - The JIVE logging stamp JLog - The JIVE logging stamp - Official English Support Forum |
|
LinkBack | Thread Tools | Display Modes |
12-18-2016, 03:19 PM | #1 (permalink) | |
Registered Users
Join Date: Feb 2008
|
S32 (JLog3) and Futaba Telemetry
supplementary information - Futaba
Quote:
__________________
Tom (j-log.eu) |
|
Sponsored Links | |||
Advertisement |
|
12-19-2016, 04:16 AM | #2 (permalink) |
Registered Users
Thread Starter
Join Date: Feb 2008
|
This is a simple bug. They removed "ESC" from their list of sensors to replace it with "ROXXY ESC". Forgot the "ROXXY ESC" then.. Bingo, ...and if a switch-case construct does not use "default:" the machine may just crash. They (we) are in luck that it gets in sync with the program again, and rather fast (a second about).
Kontronik managed it for the 1st time that Futaba integrated the displays of a foreign sensor: "Kontronik ESC". Afterwards Castle came along. Robbe owned the brand "Roxxy", has fallen under chapter eleven, Multiplex owns the brand now. Guess they asked Futaba to have also a brand naming in the display. So Futaba simply renamed "ESC" to "ROXXY ESC" - and built a bug in that transmitter. The Roxxy is btw made by the same manufacturer in Korea where the ESCs of SJ (Graupner) are coming from. Annoying...
__________________
Tom (j-log.eu) |
12-22-2016, 06:54 AM | #3 (permalink) |
Registered Users
Join Date: Oct 2015
|
I'm struggling with Futaba integration some help would be appreciated.
S32 just arrived and an 18SZ/Kosmik. Will this combo work as I am finding it hard? I have: Loaded pc software and S32 connects, Selected kosmik/sbus2/set motor poles and saved. Saved to a blank micro sd card and put in S32, Connected 32 to tx back and registered 6 times, Connected esc to port 5, Sbus2 to port 4. In tx telem getting all 6 sensors with ID code roxxy, temp, rpm, roxxy but no real time data. R7008SB in mode 2 1-7/sbus. S32 flashing green, flashing orange and solid red light. Now im stuck? UPDATE; I am now receiving data I think the SD card S32 file was the issue. After registering to the unit to the TX I then saved that file to the SD card and all seems to be working now. Some sensors don't show data but Roxxy shows the main things Capacity, Amp, Temp, RPM. Prob figure the rest out later. Last edited by MAJ1C; 12-22-2016 at 01:22 PM.. |
12-22-2016, 04:41 PM | #4 (permalink) |
Registered Users
Thread Starter
Join Date: Feb 2008
|
First: Please keep the firmware of S32 uptodate!
You do not need a SD for setup! Just "Save" from terminal to S32 through USB. It would confuse you if you change the setup via USB, then S32 starts w/ a config file on the SD, sees it, changes its setup according to the (different) content. Not a manual, some additional information: http://j-log.eu/s32/s32-en Futaba: http://j-log.eu/s32/s32-en/telemetry-futaba-s-bus2 Problem ist the T18SZ.. The current firmware has a bug. It just turned out but fortunately the issue has been accepted already as "official bug": See my post in another thread here: During registration the Tx recognizes the sensor "ESC" which has been renamed to "Roxxy ESC" now. So the Tx knows the sensor ID, even knows the name "Roxxy ESC" for this ID. But then... if you select a display of a "Roxxy ESC" (S32 uses two of them) - the transmitter crashes, recovers after 1..2 seconds. No display viewing of "Roxxy ESC" because this sensor is unknown in another sensor table of the transmitter. You may call it "bug", - I call that "crap" because of obviously zero testing by Futaba's development.
__________________
Tom (j-log.eu) |
03-21-2017, 05:35 PM | #5 (permalink) |
Registered Users
Join Date: Oct 2010
|
Do you know if Futaba is doing anything about this bug since a crashing transmitter sucks and I have this problem.
|
03-21-2017, 05:44 PM | #6 (permalink) |
Registered Users
Thread Starter
Join Date: Feb 2008
|
__________________
Tom (j-log.eu) |
03-22-2017, 06:29 PM | #7 (permalink) |
Registered Users
Join Date: Oct 2015
|
Assuming 18SZ I had the same problem with 6 sensor Roxxy setup. Use the 10 sensor setup and register all of those. Make sure your S32 has the latest firmware and I used the latest bootlog as well. Then programme as required for your esc and the telemetry should work fine and no crashing tx. The crash only happens with 6 sensors and tapping on roxxy so if you go 10 as roxxy isn't one of the sensors it won't crash and you can select all the telem you need.
|
01-12-2018, 10:23 AM | #8 (permalink) |
Registered Users
Join Date: Feb 2015
|
I have also run into the problem ROXXY bug. Therefore I used "No ESC" 10 sensors setup. All 10 sensors had been registered in the Tx after removing the previous 6 sensors.
But I have not managed to get any data in the TX. I was running the ESC several times and every time there was a different status of the S32: sometimes the blue led was blinking constantly, sometimes the red led was blinking, sometimes first both of them were blinking together, then, in a second or two, the red led went out, sometimes the S32 was absolutely dark. I have broken my mind and need help. Something went wrong, but what? The setup is the following: - Futaba T18SZ, v.3.2E with R7008SB receiver. - Kontronik Jive Pro 120+HV, v.1.8. - Vbar Neo. - S32. v.1.66. UPDATE: The data values in the TX are "0", if the S32 is not flashing. Why 0? Where are current values? The data values in theTX are "--", if the blue led is blinking. Last edited by Vladimir K; 01-12-2018 at 02:25 PM.. |
01-13-2018, 09:42 AM | #9 (permalink) |
Registered Users
Join Date: Feb 2015
|
One more update.
I have repeated the test with another ESC: JivePro 80. The same result: zero, zero, zero... on the TX's screen. I have checked the cable between ESC and S32. It's OK. I pulled the cable out from the Port.5 and powered the ESC. All the same! Does it mean the S32 interprets a missing signal as zero? I doubt both JIVEs are defective. Most likely, the data coming from ESC get lost inside the S32. BTW. The latest T18SZ firmware version is 3.2. It cannot be v.6. I have to add. I have never seen the green led blinked. As far as I understand the data are not coming from the ESC in this case. Am I righ? It seems I was inattentive enough. The ESC version must be 1.10 or higher. Will update the info after the ESC has updated. The ESC has been updateg to v.1.10. Now I can watch green and blue leds are blinking at the same time. There are "---" on the TX's screen intead of values. What else? Judging by the blinking blue led, data are not transfering to the TX. UPDATE: WOW! After 6th time of switching on, the green led is blinking only and I can see all the parameters correctly! My congrats to me! The only problem remains unchanged still: the S32 won't launch correctly at the first switching on. Is there any decision? Last edited by Vladimir K; 01-15-2018 at 02:08 AM.. |
01-14-2018, 10:43 AM | #10 (permalink) |
Registered Users
Thread Starter
Join Date: Feb 2008
|
Hi Vlad!
The blue LED blinking is not ok if there is no device on the data bus and is configured (CVS, BID, HV2BEC). Flashing means that the sbus2 connection is not ok. S32 constantly loosing the receiver (sbus2) and therefore switching to registering protocol. In reg prot, the transmitter is the peer, the tx is nothing speaking until you push a key like "register". Therefore S32 assumes, if nothing running in, that it is in tx's butt and has to switch to 9k6 baud and reg prot. In S32terminal is a "special ESC" selectable called "(== test values ==)". If you select it, S32 is sending changing test values for all data items into the selected telemetry, regardless which one. --------- JIVEpro, KOSMIK: shortly after powerup the ESC scans its option port(s) for the existence of a TelMe (JLog is a TelMe). Thus, at ESC's startup S32 has to be already in the option port of the ESC. With S32 it is not necessary that S32 is powered that time because the Jpro/KOSMIK connection is an own power domain, galvanically decoupled, supplied by the ESC. JLog2.x needs to be powered for the identification process but is also powered by the ESC through the connection. Afterwards, after the ESC has seen JLog as TelMe, you can disconnect/reconnect.
__________________
Tom (j-log.eu) Last edited by dl7uae; 01-14-2018 at 11:15 AM.. |
01-15-2018, 01:58 AM | #11 (permalink) |
Registered Users
Join Date: Feb 2015
|
Thanks a lot for your help, Tom.
|
01-18-2018, 07:23 AM | #12 (permalink) |
Registered Users
Join Date: Feb 2015
|
Does anyone know, will the data on the SD be overwritten if the SD is overfull?
|
01-18-2018, 01:16 PM | #13 (permalink) |
Registered Users
Thread Starter
Join Date: Feb 2008
|
No. If the file system is full (FAT32), just no new log file can be created or later filled sucessfully.
Maximum log file number is 65532. Activate the "R" checkbox in S32terminal to delete all log files and directories at next start. |
01-18-2018, 01:48 PM | #14 (permalink) |
Registered Users
Join Date: Feb 2015
|
Thanks again, Tom. I don't know what I would do without you.
By the way. Please, look at the photo. Do you know, will it work if I solder the pin myself? I just plugged a connector into the port 1 to check the Buffer alarm and took the connector out together with the pin. |
01-18-2018, 03:27 PM | #15 (permalink) |
Registered Users
Thread Starter
Join Date: Feb 2008
|
Photo?
Missed it, Vlad. |
01-18-2018, 03:49 PM | #16 (permalink) |
Registered Users
Join Date: Feb 2015
|
Cannot you see the picture? I can. I have inserted an URL from Dropbox.
This is the link: https://www.dropbox.com/s/36al1f2eyq..._0147.JPG?dl=0 |
01-18-2018, 04:09 PM | #17 (permalink) |
Registered Users
Thread Starter
Join Date: Feb 2008
|
Sorry, Vlad, I do not understand what you did, and especially not why..
All servo ports are universal, pinmux application assigned by the terminal. So no good idea to modify anything on S32's connectors. Buffer alarm: The buffer is giving a status signal, low-active, so high in idle state, - and S32 is evaluating to generate a warning as "Ubec alarm" if the buffer seems to be alone, buffered source has failed. It will also trigger an alarm when you disconnect the buffer status line once after S32 has seen the buffer (high).
__________________
Tom (j-log.eu) |
01-18-2018, 04:14 PM | #18 (permalink) |
Registered Users
Thread Starter
Join Date: Feb 2008
|
But now.
The pin came out? Strange.. Of course you can solder by yourself, depends on how (big) your solder "iron" looks like. Compared to all other SMD components such a pad is a monster. Give me your postal address please by PM and I will trigger MHM to send you another one.
__________________
Tom (j-log.eu) |
01-18-2018, 04:19 PM | #19 (permalink) |
Registered Users
Join Date: Feb 2015
|
As far as I understand, you have managed to see the photo. I didn't modify anything on the S32. Why did you decide I did it? Just plugged in and pulled out the connector, but unfortunately with the pin.
After I powered the system, the alarm started immediatelly. I powered all off to check if I had connected everything correctly. That's all I did. |
Thread Tools | |
Display Modes | |
|
|