Hey Guys,
Sorry about the confusion, some of the information is incorrect and let me help clarify a few things.
The ESCs are indeed compatible with refresh rates below 400Hz, the ESCs are compatible with refresh rates from 50Hz up to 600Hz, with the standard 1520us widths Flight Controllers current use allowing up to 495Hz. The KDE Direct XF ESCs can push higher frequencies (up to 600Hz), but still waiting on a flight-controller than can take advantage of this and change down to 760us or alternate bands, something future technologies will bring.
Anyways, long story short - there does not appear to be a verified synchronization issue with the SuperX equipment, and it's being used by various customers worldwide. Freddie did see an issue with his setup, but we haven't confirmed there is a compatibility issue and there could be another issue occurring (such as amperage-limitation from the PDB). Does anyone have a direct contact at XA that I can speak with concerning their hardware?
We've been in discussions with 3DRobotics concerning their hardware and they are using our equipment on their machines, so I'll find out more where they are at with their control algorithm. The problem with the Pixhawk appears to be in their negative-ground, and it's not with the KDE Direct ESC, but with compatibility with true opto-isolation. The KDE Direct XF series are true opto-isolated to the control leads to prevent noise entering the controller and as such, the flight-controller needs to be designed to handle this. There are simple work-arounds, but I'll check in with them and find out the current plans moving forward with their hardware.