This is how 12200 looks on the outside:
On the inside, on top is the 12200, bottom is xcross 160A (including the power managing chip):
The other side:
Aliminum covers:
Programmers:
12100 esc:
12200 vs Xcross 160A
Despite being very similar and having almost the same components, 12200 got a lot of improvements (ones that I noticed, I bet there are more improvements):
- Mosfets: Xcross - NCEP016N85LL 1.6mOhm. 12200 - HYG015N10NS1TA 1.2mOhm
- 12200 telemetry in the blheli32 version is way more accurate, it can be relied on.
- 12200 pcb has thick power rails - it can be seen in the photo
- First and foremost difference is the encompassing cooling solution, it really works, esc stays much cooler. Notice that the two aluminum halves are not glued in the middle and they have only a thin contact area.
- In the water I got the feeling that 12200 is stronger.
Firmware versions
12200 or 12100 come with three firmware versions: BlHeli32, Escape32, AM32. I tried all 3.
Programmers (a,b,c in the picture):
a. This one specifically works the best for blheli32 in old Windows. Only Windows. The new esc got a testing version, so download specific software from Sequre.
b. This works only for AM32 for me. Only Windows.
c. Only for escape32. Connects by wifi, configured in a browser.
Experience with these firmwares
Take into account that my experience with AM32 and escape32 happened half year ago, these are open source projects - they are evloving.
Blheli32 testing version
It has a slight starting issue while testing on the bench, but not felt in the water. Otherwise it is my choosen one.
Note: Because blheli32 does not have settings for motor number of poles, rpm telemetry data has to adjusted.
AM32 version
I know someone in the forum which got it working fluently, he used it in a buggy. But here is my experience testing it on a bench half year ago:
- could not enable telemetry.
- desync issues: if I pressed hard the throttle , it stuttered and stoped. Even if the motor is turning already, then pressed throttle hard , it stuttered
Escape32
Connection video: 'https://www.youtube.com/watch?v=J4iSgMs_MDM&t=3s
It was the worst experience:
- The start bareley managed
- Stall problems, especially in auto timing
- Had to set throttle same as on remote - not auto, otherwise it didn’t work
- Sometimes it get started by it’s own , for example it happened when I connected the wires to the programmer - frightening!
- And the cherry on top - pressing “upload firmware file” didn’t work, so could not update firmware!
Issues
While disconnecting programming wires of 12200, the power managing ic was lost, the esc would not draw any current. The chip number is SCT2A10ASTER. This chip is the same for Xcross 160A.
12100
Tested on the bench with an attached radiator:
- Max throttle got 100A bat current and 1.732*100A motor current
- 12s 40A for 1 minute, esc temperature reached 70c
- One session in the water, esc glued to external heatsink, heatsink allowed to catch air. 9m at 12s 30A bat current, temperature of the esc reached 90c, inside the pelican temperature was less than 50c.
My experience with Xcross is listed in this topic:
'ESC Flycolor X Cross HV3 settings on BlHeli 32
Notes
There is no problem running 12200 or Xcross with disconnected motor wires. At least for me was never a problem with that. Despite that I try to keep motor wires connected as much as possible during testing or during use.
Everyone welcome to add their experience!
3 Likes
Great summary & comparison of the 2 ESC’s, i’ve used both these with Blheli32 running with 12s. The cooling of the Sequre 12220 is far superior than that of the XCross (I have both on mounted on 10mm this aluminium plate).
My x-cross 160 died within a few weeks of use whilst the I’ve chucked everything at the Sequre 12200 and it’s been reliability has been solid.
1 Like