Posts by r.boen

    Two other questions then, Richard...

    1. Does the RPM Pickup need to be mounted on the ignition housing, as shown in the photo, or can it be mounted elsewhere (such as the firewall)?


    2. Assuming that you mean "connecting with a Y adapter" to the port labeled "to Ignition, with RPM signal" (as shown in the instruction manual), is the Red (+ lead) disconnected, and only the signal and ground (-) leads are connected to the Y?


    A question concerning the use of a Modern CDI Tach Leads and the Sparkswitch Pro. For the best and most accurate telemetry, how should the tach lead be connected when used with the Sparkswitch Pro? Is a "Y" servo extension used.

    In a similar vein, How is the PBS-RPM Pickup used or connected? Is this device to be used when there is no tach output lead coming from the CDI?


    Richard... Tested the new software update on a NEW PBS-RPM sensor, and ran it on the ground on the same G-62 Bucker it was intended for. Sorry Richard, but you still have huge problems with this sensor. I accessed the menu, and used the .5X setting. The RPM read-out numbers were lower (as expected), but still were very erratic and jumped around all over the place.

    Also at first, I was getting good consistent throttle response (with and without a range test) but after 5 minutes or so, the servo went into complete lock-out, and went to full speed. Had I been in the air, I would have lost the aircraft. All other flight surfaces locked up as well.

    The PBS-RPM sensor is simply not ready for Prime-Time yet. I'm pulling what sensors I have out of the aircraft that have this sensor, and will fly without this telemetry data. This sensor not only need to be optically isolated internally, it also needs to be physically isolated as well (preferably by a fiber optic link) so there is no possible way in inducing an RFI/EMI signal back into the Rx.

    BTW... All your components for lower amplitude voltage CDI ignitions work very well, and I will continue to use the.


    Regarding my earlier post. The aircraft I was having problems with is a 1/3rd scale Bucker Jungmeister that is 10 years old, museum quality, and historically accurate that I purchased to re-condition and fly at our local Warbird events. It is the only such aircraft that I have which has a Magneto ignition, and is simply too valuable to test or risk loosing. I will be happy to test the new software, but may have to wait a bit until I line up a suitable aircraft / engine combination for testing.

    Consider it reported then. I have other PBS-RPM sensors in stock and I can test one at a later date, but not on this aircraft. I can also send the “suspect” sensor to PBS - America’s for evaluation if you wish.

    Maybe I'm missing something here... If so, somebody please point it out. I posted under another subject in this forum (Erratic PBS-RPM Reading) about using this device on a Zenoah G-62 Magneto Ignition gas engine over a month ago. At first startup, I was seeing an RPM reading of over 12,000 rpm on an engine that was actually running at 6,000 rpm. Throttle response was also erratic. Since then, we tried a maiden flight, during which the engine went into "full throttle" mode, and we lost partial control of the aircraft. We were able to kill the engine and get the aircraft back safely.

    Since then, we have done some bench testing with new servos for the throttle (with the PBS-RPM module still connected), and each time lost all contact with the throttle at anything over 1/4 throttle setting, and the throttle servo went to "full throttle" & locked out. We also lost all ability to control the flight surfaces as well.

    The PBS-RPM unit was removed from the aircraft completely, and the engine was restarted. We regained full use of the throttle servo and all the flight servo operated completely normally.

    It would appear that the use of the PBS-RPM sensor in conjunction with ANY magneto ignition engine will result in SEVERE RFI / EMI interference with the receiver, leading to possible loss of control of the aircraft, unless the sensor is optically isolated from the receiver. All my other gas engines are CDI ignitions, and use optically isolated devices for either telemetry or engine kill switches... so I do not have a problem in this area.

    So, am I missing something here? Should I be using some other device, or connecting the sensor differently, in order to use it safely?

    Any suggestions or workarounds?


    I have installed a PBS-RPM sensor on a magneto Zenoah G-62, which is routed through a PBS-Dock before going to the receiver. At first startup this weekend, I was getting wildly erratic reading through the Widget at idle, and as much as 13,500 rpm at full throttle. When scanned with an optical RPM meter, I'm actually getting a stable 1600 RPM at idle, and a max of 6200 RPM at full throttle, which is where it should be.

    Any ideas or suggestions on what going on here?


    Problem solved. The telemetry and data were reversed. Since this was my first Source and I was unfamiliar with it, I took a look at the shape & orientation of the telemetry/data socket in order to try and determine what the proper orientation of the ground wire should be (there were no polarity markings for the connection nearby). With the location of the two square corners of the socket, I felt the ground wire should be orientated towards the center of the Source... Wrong, and had no luck in getting the Source connected to the Core.

    I reviewed the instruction again to see what I might have missed. The only photo of the telemetry wire showed the brown ground wire orientated towards the outside of the case. I went back and reversed the polarity of both wires (had to force fit them a little), and had immediate success in connecting. I now have all 7 of my telemetry channels up and running just fine.

    I just received my first Source. Installing it in a new aircraft using twin PBR-9D’s. I have 6 telemetry channels up and operating correctly. When I connect the telemetry for the Source to either one of the PBR’s, I loose all the other telemetry channels except for the PBR’s and the Core. I have double checked the polarity and the connection position numerous times, but no success. When I remove the source from the other telemetry circuits, I get all my other telemetry sources back online. Any suggestions here on what is going on?