You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have loaded the STM32_F051_PA2_V11 Bootloader to the four uC´s and now I am able to flash a firmware.
I did not found a matching precompiled file for the Typhoon32 (I think it is from Airbot), so I have orientated my decision on a similar optic I have found on the "how to" from Oscar Lian ( https://oscarliang.com/flash-am32-blheli32-esc/) and flashed the FD6288 version.
The pinout seems to be wrong (the PWM did not sound ok) - so I switched to the MP6531 firmware and now the ESC is running fine...
Dshot600 works well and betaflight is getting the actual RPM values as expected - but I did not get any other (current, voltage,...) data from the ESC. In the past (when I was using BlHeli_32) the setup was that the KISS-Protocol was read by an UART with an dedicated wire.
This setup is still configured - on the ESC side I have activated the "30ms Telemetry" but still no telemetry available.
I checked the target.h file on git and I think this setup matches my needs:
#define HARDWARE_GROUP_F0_C
#define USE_SERIAL_TELEMETRY
Is there any other setup I have missed?
Is it possible to activate an "advanced telemetry" so the missing data can be transferred via Dshot600?
Kind regards,
Jago
The text was updated successfully, but these errors were encountered:
I have tested the RAZOR32_F051 firmware and the esc starts transmitting values to the FC - but the voltage value is to high and the esc currents are much to high... And the esc is rebooting every 5 seconds...
Hello,
I have loaded the STM32_F051_PA2_V11 Bootloader to the four uC´s and now I am able to flash a firmware.
I did not found a matching precompiled file for the Typhoon32 (I think it is from Airbot), so I have orientated my decision on a similar optic I have found on the "how to" from Oscar Lian ( https://oscarliang.com/flash-am32-blheli32-esc/) and flashed the FD6288 version.
The pinout seems to be wrong (the PWM did not sound ok) - so I switched to the MP6531 firmware and now the ESC is running fine...
Dshot600 works well and betaflight is getting the actual RPM values as expected - but I did not get any other (current, voltage,...) data from the ESC. In the past (when I was using BlHeli_32) the setup was that the KISS-Protocol was read by an UART with an dedicated wire.
This setup is still configured - on the ESC side I have activated the "30ms Telemetry" but still no telemetry available.
I checked the target.h file on git and I think this setup matches my needs:
#define HARDWARE_GROUP_F0_C
#define USE_SERIAL_TELEMETRY
Is there any other setup I have missed?
Is it possible to activate an "advanced telemetry" so the missing data can be transferred via Dshot600?
Kind regards,
Jago
The text was updated successfully, but these errors were encountered: