I haven't tried the am32 version that alkamotors made. I just finished flashing it.

This is just a heads up for anyone else who flashed that hf32 crap- I couldn't read my esc's with esc-configurator.com or develop.esc-configurator.com after flashing hf32.

I had to use their hf32 esc configurator to flash it to am32:
https://hf32.neutron-rc.com/?spm=a2g0o.d...Q8WCQ8WCLJ

Then I could actually read my esc's via the usual esc-configurator. (or maybe I used the develop.esc, I don't remember, but you've gotta use their damn hf32 thing to flash back.)

Now that I can actually read my esc's, I've flashed this 35a aio to bf 4.5, and installed it in a 3" 4s build with 1506 4300kv motors. Hopefully it'll fly all good like.

Good stuff, I hope it runs well for you man. I've been using the official code (testcode version) and yet to flash 2.01 myself. This is why I stay away from the HF32 version as it will be frozen in time of the fork, missing updates.

---

I've been testing 6S as well with motor throttle lowered to 37%. Works well. Gotta reduce the startup power now, lol, still got it set high from the 2S stuff.

(13-Aug-2023, 10:30 AM)ph2t Wrote: Good stuff, I hope it runs well for you man.  I've been using the official code (testcode version) and yet to flash 2.01 myself.   This is why I stay away from the HF32 version as it will be frozen in time of the fork, missing updates.

---

I've been testing 6S as well with motor throttle lowered to 37%.  Works well.  Gotta reduce the startup power now, lol, still got it set high from the 2S stuff.

The test version of AM32 2.01 its working really well for me. I tested with 3s and 4s, as I moved to 3.5 inch propellers. No problem at all. Perhaps on 4S the tune needs some works, as I have some propwash on big split-s. I'm running bf 4.5.

After putting quite a few flights through it, my v1 35A aio is quite happy with AM32 v2.01, BF v4.5, on 4s with 1506 motors. No loss of power, twitches, or other weird random things. Seems it just wanted significantly more voltage to be happy, as well as an actual am32 developer to tweak the esc firmware.

Thanks for taking the time to do that, Alkamotors.

Only current issue is that average cell voltage and altitude disappear from my osd on hard punch outs and when my battery starts getting lower. I’m not sure if this is a BF v4.5 bug or a bug with the aio. It makes more sense to me that it’s a BF bug- I think if it was an aio bug, the osd elements would still be there even if the data was wrong or froze. Anyone else experiencing this?

I am experiencing the buggy baro readings. Also with BF 4.5. I have to power cycle to get rid of it. Sometimes the altitude is correct but after a hard whack or landing and takeoff (same pack) it will go buggy and show 200+ meters in altitude.

The STM32 monopoly has been broken. We'll see how the market reacts. Way to go

Second NeutronRC AIO with AT32 mounted and working, this time a V1.2.

Flywoo Explorer 4inch
4s 1404 2750kv motors
BF 4.5 and AM32 2.01

It's working fine, no mayor problem. Had to re-calibrate de current sensor, as it was way off. Besides that, the quad is flying better than ever, even in high wind conditions. RTH works perfectly even landing, did not saw the baro with weird numbers.

I'm quite happy, I order another AT32 FC, the betafpv 1s V3 for a 75mm digital whoop.

Excellent. I think you’re the first of us to order or try out the v1.2, I’m glad to hear that it seems to be a bit more mature than the v1.

The quad that my neutron AIO ended up in is the tadpole HD frame.  It's pretty heavy and can bottom out on tricks if you don't time the throttle properly for recovery.
I'm running a vista unit, started with a runcam camera which was a pos and converted to a caddx polar.  The night view on this cam is pretty good too.  

I set it up to run 4S and 6S.  I used PID profile for battery voltage function which is pretty nifty.  still have to set the motor scale (using a duplicate rates profile) though when switching between 4S and 6S.  I have the config shown on the OSD just to make sure.

I'm using one of those matek spike arrestor things with the diode/cap combo.   I get antsy with 6S on aios these days after killing a reaper aio ($$) due to spikes.


Running 1207 rcinpower motors, 5000kV with motor scaling set to 55%(4s) and 37%(6s) respectively.   HM EP1 receiver with mini-T antenna.

All the videos below are before I made it into a naked vista setup


Here are some videos.  They are all using blackbox logs available from the FC with gyroflow to stabilize the footage.  Footage taken from my dji googles (V2).

Very nice!! And crazy running those 1207s on 6S, looks like you got it tuned nicely!! Do they get hot, and what size 6S pack/flight time are you getting?
I had a few sets of those motors from back in the day, they were great and powerful but could really suck current at the top end.

Thank you mstc! I'm happy with the tune, there is a bit of stutter because it is heavy, but that has improved with the naked conversion. The motors come down very warm on 6S. on 4S they're cold, lol. packs are BONKA 4S 450mAh hv and CNHL 6S 450mAh. they are both ver old sets of packs and have seen better days, but i still get 3-4 mins, especially on the 4S if I'm cruising.

Hi ph2t,

Nice Build.    SWEET.    Good Job.  

I like watching your videos. Very Cool 

Later, My Friend, iFly  

After quite a few batteries, it appears that the v1 35a aio is now also quite happy on 3s with AM32 v2.01, BF v4.5.

No issues with motors starting up, no issues with a lack of power.

In the NEUTRONRCF435MINI (3-5S, 35A) flight controller you can connect one servo to the LED pin. I tried to use other pins TX1, TX2, TX3 to connect the second servo, but it failed. The sliders run in Betafligh 4.5.0, but only the servo on the LED pin works. I shared this information so that you don't waste time searching for a site for a second servo.

This is just an update on the issues I was having with altitude and average cell voltage disappearing from my osd on hard punch outs or when my battery got low.

After some back and forth with the BF devs, the issue was that I am running the latest stable release of Walksnail firmware.

Apparently osd fonts changed in bf 4.5. So, the fix is either run the latest Walksnail beta (I didn’t want to do this), or, run this cli command:

set ‎displayport_msp_fonts = 0,0,0,0

Running that command fixed it, and I am no longer losing important osd elements on this NeutronRC 35A aio.