So, i was very happy with my fs i6 and ia6b receiver, until this documentation came in life:
In this, they clearly say that i-bus telemetry is possible in fs i6 transmitter too!
So, i connected a jumper wire from Kakute H7 wing’s T7 (Serial 1, telem1) to the ia6b’s i-bus signal port.
Then i adjusted some parameters as told in the documentation:
”Set the following parameters for the telemetry port used:
SERIALx_PROTOCOL = 49
SERIALx_OPTIONS = 0 / cleared as the library will set its own options
SERIALX_BAUD doesn’t matter as the library will set its own baud”
And then i rebooted and went to the transmitter to configure for it.
But when i saw in the “RX setup: Sensor list”, Only the default 3 sensors got displayed there?
but docs say first 15 will get displayed, and on the home screen, only a few (in my case, 3) can be displayed:
And i dont understand which button is he saying me to press!? i tried moving the switch A which is assigned to ch7, but nothing happens?
Any idea what is happening over here?
Use the Custom Firmware Builder and enable i-bus telemetry for that board and then flash the flight controller. It’s not enabled by default as you will see.
Before asking any questions go to the Wiki and read it Custom Firmware Builder
And don’t assign any channels, you are on the wrong track there.
This was a totally new experience for me ! I read that doc given, created a new firmware build with i-bus Telemetry enabled (Yes! It was disabled previously as you said) and then i flashed that .apj file to the Kakute.
Not only this, yesterday I saw that Some good people out there have created a new “14-channel Flyplus firmware for fs-i6 transmitter”!
And after much researching on it for a few hours, I was able to successfully flash the new firmware to the fs i6 using an Arduino UNO R3 and some jumpers connected to Fs-i6.
This New firmware enables us to get all the Telemetry data (supports 2 and 4 byte sensors, and can handle upto 28 byte long Telemetry frames!) Directly at the home screen of fs i6, along with the RSSI too!
I assume your drone is on ground, not armed and uses the baro for altitude
I assume also the FC takes as long as the drone is not armed the baro reading as corrected relative altitude to zero.
At that time of writing above post, The drone was not ready to arm. But after continuously working on it, I made it ready to arm. I armed it, And still the transmitter altitude shows correct values for even less than 0.4 seconds and then again shows 0.00, then again correct values comes, then again reset to 0.00.
Why is this happening even after arming ? And for altitude, I have the on board baro, and Micro M10 GNSS also connected.
These all fields are also either showing a fix 0 or are simply blank:
Latitude, Longitude, GAlt, Head, CoG, Cell, Curr, AccX, AccY, AccZ, VSpe, MxAl, some S85 to S90 fields also.
But some of the fields really give accurate data. What is happening and where can i fix it?
But then why are all of these values getting displayed very properly?=>
Arm status:, Flight mode:, GPS status, Distance to home, Drone bat Volt, Drone MCU Temp, Fuel%, Roll, Pitch, Yaw, Rate of Climb, RPM, GPS Speed.
All these above fields show corect values.
I don’t know why but i am having a feel that it’s a Transmitter’s firmware bug. I think it’s mixing the values of “Alt: “ and “GAlt: “ field, In which drone updates GAlt always to 0 m and updates the Alt with correct baro altitude. That’s why It shows correct Baro Alt but soon it changes to 0 ?
I think you might be correct, Its been about 10 years since I last used ibus telemetry and it was on another flight controller firmware. It seems there are a lot of “if’s” for what values you will receive :
ArduPilot supports most standard i-BUS sensors for which it has a logical equivalent data source. Most receivers, however, will only request the first 15 available sensors and ignore the rest. Therefore the sensor types have been sorted in order of subjective value for use on transmitters with small screens such as entry-level Flysky transmitters.
Some sensors provide multiple values while only using one slot. Some (such as GPS location or XYZ data) are logical groups of information but require a sensor slot for each data point.
If any sensors require features that have been excluded from your board’s build, those sensors will be excluded from the list allowing lower priority sensors into the top 15 slots.
If you have a receiver that doesn’t follow the standard limit and opts to allow more sensors in exchange for a fractionally slower update frequency, you will receive extra telemetry.
The sensor priority order is:
Armed status (Armed/UnArmed on stock/modified firmware; 0/1 on OpenTX)
Flight mode (where an equivalent i-BUS mode exists, otherwise blank; just a number on OpenTX)
GPS Status (0: unhealthy, 1: no fix, 2: 2D fix, 3: 3D fix) plus number of satellites (using 1 slot total)
Remaining battery or fuel %
Battery voltage
Altitude
Distance from home
Climb rate / vertical speed
Ground speed
Roll, Pitch & Yaw angles (3 separate sensors using 3 slots)
Airspeed
Temperature and air pressure (2 separate sensors using only 1 slot)
RPM
Current usage
Average cell voltage
Compass heading (equivalent to Yaw)
Course over ground
GPS latitude & longitude (2 separate sensors using 2 slots)
GPS altitude ASL
Acceleration X, Y & Z (3 separate sensors using 3 slots)
They are pretty decent radios for the money. never had any returns. flysky RC and telemetry protocols are nice to work with as RC and telemetry are both on regular 115200 ttl serial, no funky inversion or non standard baud rates to deal with, The worst part of them was the software.
I mean you can’t order from China and any drone parts are stopped by customs. I sent him some old drone parts from the UK and it was blocked by Indian customs.
Well, that’s a bummer. Were these parts given a hard red light or was there a chance to still get it through if you submitted a document @RudrakshTek ?
But Radiomaster TX is available on a lot of sites here
I updated to the 14 channel Flyplus firmware and I am thinking the Bug is in this firmware.
On receiver (fs ia6b), the stock firmware is running.
.
I tried my level best.
I submitted all the documents I could, and even submitted an invoice of the items provided by geofrancis sir to me, with his digital signatures.
But no…
Indian customs (especially at Jaipur, Rajasthan), Are a complete bunch of crooks. They gave a red light and said any item related to category “DRONES” in any form is strictly prohibited to import.
My parents also visited there but Even after a quarrel there, Nothing good happened.
And just a week ago, A letter came from them after so long time, in which they are again calling us jaipur to Personally talk to them again.
.
Yes that’s available on Many sites. But we can’t just go on Radiomaster’s website and place a direct order there. Because There are many chances that it will get stopped at customs. + We have to pay customs duty also.
