Sensors (displays) used by S32 and data assignment
In contrast to JLog2.x, S32 does not appear as 8 sensors than only 6.
You can register or re-register S32 sensors at any time. Just make sure that a sensor of S32 does not already exist in the transmitter before you register. S32 does not insist that all its sensors are registered at the transmitter.
Observe two LEDs on S32:
blue: Lights up if S32 does not see a S.Bus2 data stream from the receiver, means that S32 has gone into register mode automatically.
red: Lights constantly as long as not all of its 6 sensors have been registered sometime. Note that the registration may not have been done to the same transmitter or in the same model (profile)!
Registration data (slot assignments) are stored as part of S32′s setup. S32terminal displays them. You can copy registration data via file (also setup file on SD card read by S32 at its startup) from one S32 to another.
You have to leave some time before you press “Register” (respectively confirm) again (2 seconds), otherwise “the transmitter overrides itself”.
.
Data in the Displays (see figure above)
Sensor 1 “ESC“: CURRENT==Imot, VOLTAGE==Ubat, CAPACITY==mAh, RPM==rpmRotor, TEMP=tFET .. S32 Ubat and general (CVS,BID) voltage alarm: +50V added to Ubat .. S32 mAh alarm: mAh value gets negative. Pulsed alarm, less often if thr/pwm is below 10%
Sensor 2 “TEMP“: ==throttle
Sensor 3 “TEMP“: ==PWM
Sensor 4 “TEMP“: ==tBEC
Sensor 5 “ESC“: CURRENT==Ibec, VOLTAGE==Ubec; .. CAPACITY==speed, RPM==RPMext, TEMP==T1ext .. S32 Ubec voltage alarm: +50V added to Ubec
Sensor 6 “CURR“: CURRENT==LCN, VOLTAGE==LCV, CAPACITY==CVSalarms .. LCN: number of the cell with LCV, . LCV: Lowest Cell Voltage, . CVSalarms: OOIRD*100+OOB*10+UC … OOIRD: Outside Of the Inner Resistance Dynamics (“soft” cell) … OOB: Out Of Balance … UC: UnderCharge alarm (disabled, S32 has once reported motor current flow to CVS) … (OOIRD,OOB: each running 1 to 16 for cell 1..16. The number is OOIRD-1, OOB-1, – four cells of that status are logged. …. UC: 0|1 .. The maximum value of “CVSalarms” is thus 16*100+16*10+1=1761)
Futaba telemetry does not know about alarms sent by a sensor. Alarm thresholds to be set in the transmitter only. That may lead to zombie alarms (battery change, no receiving yet). On the other hand S32 uses the Ubat alarm as general alarm for all voltage-related warnings, especially for those based on CVS16 or a BID battery tag. In order to nevertheless be able to send alarms, S32 adds 50 to the current value in case of an alarm. One is setting a corresponding “greater than” warning threshold in the transmitter.
In case of a mAh alarm S32 gives the current value a negative sign. One defines a warning threshold for “lower than zero” in the transmitter. The purpose is to avoid that a mAh alarm could “drive us into the madness”. Once triggered, the alarm would never stop. – S32 is pulsing a mAh alarm. It also returns again and again but w/o persistent appearance. If throttle or PWM goes below 10%, the alarm is less often given (auto-rotation, after landing).
Another note: In the new firmware, Futaba has changed the general sensor name “ESC” to “Roxxy”. This is their thanks to the one who launched the world’s first sensors for the Futaba system in April 2012, before Futaba.
There seems to be a bug in version 6 of the firmware for the T18SZ, at least in the German version: The transmitter recognizes the sensor ID, names its displays as “Roxxy”, but it does neither know “ESC” nor “Roxxy” in its manual selection list. Result is a chrashing of the software if one selects a learned (registration) sensor “Roxxy”. — T14SG firmware version 6, “Roxxy”: no issue.
Hint: (any transmitter): If your transmitter denies to register all sensors although they are not registered already: “DATA RESET” on “TELEMETRY” only.
