I made a calibration of RPM versus pulse width (throttle %) for the Plettenberg Orbit 25-10 and a Phoenix 35 in the Low RPM mode. Unfortunately, it appears that the High RPM mode of the Phoenix is too high and the Low RPM mode is too low for the Plettenberg, because the available RPM spacing (resolution or increment) for even 1/2 of 1% throttle changes becomes extremely large at the 9,000 to 11,000 RPM range -- like 200 RPM or more. (In comparison, the Schulze F2B provides nearly constant 30 RPM increments over this same range.)
If one can live with the large RPM spacing, flyers using the FM-9 system have been able to get usable RPMs by using the JetiSpin calibration of the FM-9, even though the tach values won't agree with the displayed RPM. That calibration does provide the 1/2 of 1% throttle changes (.005 ms), which is the minimum one can hope to be usable with the ESC.
It is possible that the Set RPM mode of the Phoenix can be used to provide better RPM control since it requires an input of the number of poles of the motor, but I haven't checked that out.
Another viable alternative for an ESC for the Plettenberg is the JetiSpin 66; it provides a BEC but it doesn't implement the nice data recording of the ICE. It does require an input of the number of poles (10 for the Plettenberg). When I specified timing of 15 degrees and a frequency of 8 kHz and end points of 1.0 and 2.0 milliseconds and 8,000 to 11,000 RPM, I found that RPM increments of about 20 were available, although a 4S battery only went to about 9450 RPM; a 5S battery took it to about 10,300 RPM (and would have gone higher). I'm thinking of incorporating this in the FM-9 Programmer as an alternate calibration for JetiSpin.