FETtec OneWire (FETtec 4in1 ESC 45A, Cube Orange, GPS1/serial3) --> Not working

ArduCopter Copter 4.5
1

Dear all,
I am trying to setup a FETtec 4in1 ESC 45A via OneWire on a Cube Orange, GPS1/serial3. I did not use the bdshot option when uploading the firmware (v4.5.3).

I set everything up following this guide:
https://ardupilot.org/copter/docs/common-fettec-onewire.html#common-fettec-onewire

My connections between FC and ESC are:
GPS1 Pin 2 (GPS_TX = MCU_RX) → ESC TLM pad
GPS1 Pin 3 (GPS_RX = MCU_TX) → ESC S1-S2-S3-S4 (parallel connection)
GPS1 Pin 8 (GND) → ESC GND
(also tried swapping rx and tx)

My configuration:
SERIAL3_PROTOCOL = 38
SERIAL3_OPTIONS = 0
SERIAL3_BAUD = 2000 (not sure if this needs to be set)
MOT_PWM_TYPE = 0
MOT_PWM_MAX = 2000
MOT_PWM_MIN = 1000
SERVO1_FUNCTION = 33
SERVO2_FUNCTION = 34
SERVO3_FUNCTION = 35
SERVO4_FUNCTION = 36
SERVO_FTW_MASK = 15
SERVO_FTW_RVMASK = 0
SERVO_FTW_POLES = 24

The ESC initializes with 2 beeps and activates the motor brake. But I get the message “PreArm: FETtec: 4 of 4 ESCs are not running”

Is there anything I am overlooking…? Thanks!!

2

@teeZee can you take a look at this?
@Willa can you test this with a non CubePilot flight controller?

3

No, I only have the cube orange here. I am now testing GPS2… Will report in a minute.

4

Same on GPS2 :frowning:

Connection:
GPS2 Pin 2 (MCU_TX) → ESC S1-S2-S3-S4 (parallel connection)
GPS2 Pin 3 (MCU_RX) → ESC TLM pad
GPS2 Pin 6 (GND) → ESC GND

My configuration:
SERIAL2_PROTOCOL = 38
SERIAL2_OPTIONS = 0
SERIAL2_BAUD = 2000 (not sure if this needs to be set)
SERIAL3_PROTOCOL = 0
SERIAL3_OPTIONS = 0
MOT_PWM_TYPE = 0
MOT_PWM_MAX = 2000
MOT_PWM_MIN = 1000
SERVO1_FUNCTION = 33
SERVO2_FUNCTION = 34
SERVO3_FUNCTION = 35
SERVO4_FUNCTION = 36
SERVO_FTW_MASK = 15
SERVO_FTW_RVMASK = 0
SERVO_FTW_POLES = 24

5

@TeeZee : I bought the ESC directly from your shop a week ago, didn’t have the possibility to check the firmware on the ESC yet (i was assuming it was the latest one).

6

Hi @Willa

You might have to check with the esc firmware, Flash it with the latest and it should work just fine.
Kindly note
tlm 1& 2 Are serial 1&2
gps 2 is Serial 4

Use fettec web configurator : FETtec Configurator
connect FTDI adapter TX & RX with an diode and resistor (use 3.3v for vcc) and TLM and GND to the esc as per below pic

image
image537×513 42.3 KB

Install Latest FW [1.0.241]
Assign esc ID as 1-4 if they are different.

7

Thanks, I will try this.

8

I have the 45A version, so the latest available firmware is 1.0.224.
The firmware on the escs is 1.0.182

Unfortunately, I cannot yet fllash, because the configureator complains that “Many serial communication errors ocurred”.

Up to now, I tried ftdi (clone) and cp2102N. Will now try different diodes…

9

I hope the esc is disconnected from it signal connection with the FC and only FTDI is connected.
also pullup has to be provided previous schematic, use a fast diode.

If possible remove the parallel connection with esc’s for flashing purpose

10

Yes FC signals are disconnected. I tried the diodes SM4006PL and ES1DL, both give the same error. I think I’ll give up. If I could be sure that this is an ESC firmware issue, I might try again. But the firmware code isn’t public and therefore I can’t compare the changes. Release notes do not mention any issues with onewire.

11

it is because of FW, I have rigs running Fettec Onewire here.
just make sure about the ftdi circuit is correct and the job should be done. as simple as that.

try adding 1k ohm pull up to 3.3v

12

I tried 1k and 4k7 and 1M, nothing works. Circuit is as in your image. Telemetry inside the Fettec GUI works. I am giving up on this, thanks for your efforts!

13

And if the firmware really is such a big issue, then fettec could eventually have updated my esc before shipping. The firmware is 2.5 years old…

14

if telemetry works in GUI. fettec…, it should flash the esc without any issues. Try downloading offline GUI.

the configurator will download the firmware and install by itself.
under overview > Remote Firmware > select firmware version > flash

15

That was my first attempt after getting the error message in the Chrome GUI…