Steve, The post regarding saturated injectors was archive # 62715 on 6 Aug, 2016. If you send me your email address, I can send this post directly and also send the program and instructions for reading the parameters and mixture correction table from the EC2. Steve Boese sboese@uwyo.edu From: Rotary motors in aircraft <flyrotary@lancaironline.net> on behalf of Stephen Izett <flyrotary@lancaironline.net> Sent: Sunday, August 7, 2016 7:24:04 PM To: Rotary motors in aircraft Subject: [FlyRotary] Re: Finding the gremlin Steve, I meant to ask about the saturated injectors. I don’t remember this post. Would you mind sending me the image so I know what I’m looking for and explain the symptoms etc. Cheers Steve Izett On 8 Aug 2016, at 9:06 AM, Steven W. Boese <flyrotary@lancaironline.net> wrote: Steve, I've attached a photo of the hardware from a system that I used to examine the signals and data frame from my EC2's. The DB37 connector is a TEE that has a straight through male-female connection with a third DB37 connector on it. This enables the connector to be inserted onto the EC2 without making any changes to the aircraft wiring. The third connector is used to capture 8 channels of data using a NI USB 6008 or NI USB 6009 module and a PC running NI Signalexpress software. The image posted recently of the saturated injector signals was generated with this system. The hardware also allows the PC to interrogate the EC2 to obtain its data frame which is decoded and the parameters shown on the screen while the engine is running. The mixture correction table can also be captured and modified while the engine is running. In addition, the mixture correction table can be captured to the PC, modified while disconnected from the EC2 and then uploaded back to the EC2 after re-establishing the connection. An EM(x) must not be active when doing this. The software I developed and instructions for doing this was available on a website I maintained, but the website was discontinued due to the limited interest shown in it. Steve Boese From: Rotary motors in aircraft <flyrotary@lancaironline.net> on behalf of steve Izett <flyrotary@lancaironline.net> Sent: Sunday, August 7, 2016 5:52:16 PM To: Rotary motors in aircraft Subject: [FlyRotary] Re: Finding the gremlin Your right Bobby, thats what I’m thinking. A male-female D-sub37 that I can plug into the current loom that brings out the CAS inputs, Coil and Injector outputs. Cheers Steve On 8 Aug 2016, at 1:45 AM, Bobby J. Hughes <flyrotary@lancaironline.net> wrote: Steve Last night I had the thought of making a DB37 breakout so I can easily get a CRO onto and monitor any input/outputs to the EC2. A simple screw terminal strip may be simpler use for testing. That would allow full access to the CAS wires to add an external 1k resistor and verify p-p voltage. Bobby Sent from my iPad On Aug 6, 2016, at 7:23 PM, steve Izett <flyrotary@lancaironline.net> wrote: Thanks Tracy The NOP indication is directly linked to RPM - about 6K (Dynon miss reads at the same point). But no missing occurs at this point, engine continues smooth. When the gremlin strikes (all hell breaks loose) it does appear clearly related to load - just before 24”Hg. Ive never checked the timing with a light or whats in the EC2 (dumb), just thought I'd zero’d all parameters in non volatile memory. I’m going past the hangar today so will fire her up and read the static timing setting via the EM3. As far as Earths. I have a noisy one and a quiet one and one for the gear pump. Each has 10 gauge wire 26 inches back to battery. Each Earth point is an AN bolt and nut clamping all those paticular earths lugs either side of the 10 gauge earth lug. All lugs are soldered. Power Busses are: Engine, Flight and Gear (30 amp pump) each fed by 10 gauge wire 36 inches back to battery. In order to easily get to all electrical systems I opted for a two buss blade fuse arrangement. (The gear power is a 30amp breaker) This does mean on the engine buss, EC2, EM3, Coils, Injectors, Pumps, are fed from the same point via 10 gauge wire rather than the EC2 independently back to to battery. Thanks Steve and Bobby I kept and ran the injector lines and coil trigger lines independently seperate from each other and all other wires where possible. eg. Coils go to the right and through the firewall. Injectors to the left and though the firewall. I do pull the throttle each time the gremlin strikes trying to minimise damage to the drive line. Last night I had the thought of making a DB37 breakout so I can easily get a CRO onto and monitor any input/outputs to the EC2. I’ll do this before next Friday enabling testing of electrical systems. I’ll check the CAS signal amplitude and check the injector signals. I would like to get a video recorder, recording everything as I always forget to check some parameter each time I’m testing. Steve On 7 Aug 2016, at 4:12 AM, Tracy <flyrotary@lancaironline.net> wrote: Steve wrote: "Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine?" Sort of. That NOP you are seeing is a good indication that the ec2/3 has been jolted out of its normal operating loop and is trying to reboot. The backfiring is too. Electrical noise (probably in the grounding scheme of electrical wiring layout) is the most likely candidate. Tracy Sent from my iPad On Aug 5, 2016, at 17:31, steve Izett <flyrotary@lancaironline.net> wrote: Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine? -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html <NI USB 3008 connections 2.JPG>-- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html
Steve,
The post regarding saturated injectors was archive # 62715 on 6 Aug, 2016.
If you send me your email address, I can send this post directly and also send the program and instructions for reading the parameters and mixture correction table from the EC2.
Steve Boese
sboese@uwyo.edu
On 8 Aug 2016, at 9:06 AM, Steven W. Boese <flyrotary@lancaironline.net> wrote: Steve, I've attached a photo of the hardware from a system that I used to examine the signals and data frame from my EC2's. The DB37 connector is a TEE that has a straight through male-female connection with a third DB37 connector on it. This enables the connector to be inserted onto the EC2 without making any changes to the aircraft wiring. The third connector is used to capture 8 channels of data using a NI USB 6008 or NI USB 6009 module and a PC running NI Signalexpress software. The image posted recently of the saturated injector signals was generated with this system. The hardware also allows the PC to interrogate the EC2 to obtain its data frame which is decoded and the parameters shown on the screen while the engine is running. The mixture correction table can also be captured and modified while the engine is running. In addition, the mixture correction table can be captured to the PC, modified while disconnected from the EC2 and then uploaded back to the EC2 after re-establishing the connection. An EM(x) must not be active when doing this. The software I developed and instructions for doing this was available on a website I maintained, but the website was discontinued due to the limited interest shown in it. Steve Boese From: Rotary motors in aircraft <flyrotary@lancaironline.net> on behalf of steve Izett <flyrotary@lancaironline.net> Sent: Sunday, August 7, 2016 5:52:16 PM To: Rotary motors in aircraft Subject: [FlyRotary] Re: Finding the gremlin Your right Bobby, thats what I’m thinking. A male-female D-sub37 that I can plug into the current loom that brings out the CAS inputs, Coil and Injector outputs. Cheers Steve On 8 Aug 2016, at 1:45 AM, Bobby J. Hughes <flyrotary@lancaironline.net> wrote: Steve Last night I had the thought of making a DB37 breakout so I can easily get a CRO onto and monitor any input/outputs to the EC2. A simple screw terminal strip may be simpler use for testing. That would allow full access to the CAS wires to add an external 1k resistor and verify p-p voltage. Bobby Sent from my iPad On Aug 6, 2016, at 7:23 PM, steve Izett <flyrotary@lancaironline.net> wrote: Thanks Tracy The NOP indication is directly linked to RPM - about 6K (Dynon miss reads at the same point). But no missing occurs at this point, engine continues smooth. When the gremlin strikes (all hell breaks loose) it does appear clearly related to load - just before 24”Hg. Ive never checked the timing with a light or whats in the EC2 (dumb), just thought I'd zero’d all parameters in non volatile memory. I’m going past the hangar today so will fire her up and read the static timing setting via the EM3. As far as Earths. I have a noisy one and a quiet one and one for the gear pump. Each has 10 gauge wire 26 inches back to battery. Each Earth point is an AN bolt and nut clamping all those paticular earths lugs either side of the 10 gauge earth lug. All lugs are soldered. Power Busses are: Engine, Flight and Gear (30 amp pump) each fed by 10 gauge wire 36 inches back to battery. In order to easily get to all electrical systems I opted for a two buss blade fuse arrangement. (The gear power is a 30amp breaker) This does mean on the engine buss, EC2, EM3, Coils, Injectors, Pumps, are fed from the same point via 10 gauge wire rather than the EC2 independently back to to battery. Thanks Steve and Bobby I kept and ran the injector lines and coil trigger lines independently seperate from each other and all other wires where possible. eg. Coils go to the right and through the firewall. Injectors to the left and though the firewall. I do pull the throttle each time the gremlin strikes trying to minimise damage to the drive line. Last night I had the thought of making a DB37 breakout so I can easily get a CRO onto and monitor any input/outputs to the EC2. I’ll do this before next Friday enabling testing of electrical systems. I’ll check the CAS signal amplitude and check the injector signals. I would like to get a video recorder, recording everything as I always forget to check some parameter each time I’m testing. Steve On 7 Aug 2016, at 4:12 AM, Tracy <flyrotary@lancaironline.net> wrote: Steve wrote: "Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine?" Sort of. That NOP you are seeing is a good indication that the ec2/3 has been jolted out of its normal operating loop and is trying to reboot. The backfiring is too. Electrical noise (probably in the grounding scheme of electrical wiring layout) is the most likely candidate. Tracy Sent from my iPad On Aug 5, 2016, at 17:31, steve Izett <flyrotary@lancaironline.net> wrote: Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine? -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html <NI USB 3008 connections 2.JPG>-- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html
On 8 Aug 2016, at 1:45 AM, Bobby J. Hughes <flyrotary@lancaironline.net> wrote: Steve Last night I had the thought of making a DB37 breakout so I can easily get a CRO onto and monitor any input/outputs to the EC2. A simple screw terminal strip may be simpler use for testing. That would allow full access to the CAS wires to add an external 1k resistor and verify p-p voltage. Bobby Sent from my iPad On Aug 6, 2016, at 7:23 PM, steve Izett <flyrotary@lancaironline.net> wrote: Thanks Tracy The NOP indication is directly linked to RPM - about 6K (Dynon miss reads at the same point). But no missing occurs at this point, engine continues smooth. When the gremlin strikes (all hell breaks loose) it does appear clearly related to load - just before 24”Hg. Ive never checked the timing with a light or whats in the EC2 (dumb), just thought I'd zero’d all parameters in non volatile memory. I’m going past the hangar today so will fire her up and read the static timing setting via the EM3. As far as Earths. I have a noisy one and a quiet one and one for the gear pump. Each has 10 gauge wire 26 inches back to battery. Each Earth point is an AN bolt and nut clamping all those paticular earths lugs either side of the 10 gauge earth lug. All lugs are soldered. Power Busses are: Engine, Flight and Gear (30 amp pump) each fed by 10 gauge wire 36 inches back to battery. In order to easily get to all electrical systems I opted for a two buss blade fuse arrangement. (The gear power is a 30amp breaker) This does mean on the engine buss, EC2, EM3, Coils, Injectors, Pumps, are fed from the same point via 10 gauge wire rather than the EC2 independently back to to battery. Thanks Steve and Bobby I kept and ran the injector lines and coil trigger lines independently seperate from each other and all other wires where possible. eg. Coils go to the right and through the firewall. Injectors to the left and though the firewall. I do pull the throttle each time the gremlin strikes trying to minimise damage to the drive line. Last night I had the thought of making a DB37 breakout so I can easily get a CRO onto and monitor any input/outputs to the EC2. I’ll do this before next Friday enabling testing of electrical systems. I’ll check the CAS signal amplitude and check the injector signals. I would like to get a video recorder, recording everything as I always forget to check some parameter each time I’m testing. Steve On 7 Aug 2016, at 4:12 AM, Tracy <flyrotary@lancaironline.net> wrote: Steve wrote: "Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine?" Sort of. That NOP you are seeing is a good indication that the ec2/3 has been jolted out of its normal operating loop and is trying to reboot. The backfiring is too. Electrical noise (probably in the grounding scheme of electrical wiring layout) is the most likely candidate. Tracy Sent from my iPad On Aug 5, 2016, at 17:31, steve Izett <flyrotary@lancaironline.net> wrote: Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine? -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html
Last night I had the thought of making a DB37 breakout so I can easily get a CRO onto and monitor any input/outputs to the EC2.
Thanks Tracy The NOP indication is directly linked to RPM - about 6K (Dynon miss reads at the same point). But no missing occurs at this point, engine continues smooth. When the gremlin strikes (all hell breaks loose) it does appear clearly related to load - just before 24”Hg. Ive never checked the timing with a light or whats in the EC2 (dumb), just thought I'd zero’d all parameters in non volatile memory. I’m going past the hangar today so will fire her up and read the static timing setting via the EM3. As far as Earths. I have a noisy one and a quiet one and one for the gear pump. Each has 10 gauge wire 26 inches back to battery. Each Earth point is an AN bolt and nut clamping all those paticular earths lugs either side of the 10 gauge earth lug. All lugs are soldered. Power Busses are: Engine, Flight and Gear (30 amp pump) each fed by 10 gauge wire 36 inches back to battery. In order to easily get to all electrical systems I opted for a two buss blade fuse arrangement. (The gear power is a 30amp breaker) This does mean on the engine buss, EC2, EM3, Coils, Injectors, Pumps, are fed from the same point via 10 gauge wire rather than the EC2 independently back to to battery. Thanks Steve and Bobby I kept and ran the injector lines and coil trigger lines independently seperate from each other and all other wires where possible. eg. Coils go to the right and through the firewall. Injectors to the left and though the firewall. I do pull the throttle each time the gremlin strikes trying to minimise damage to the drive line. Last night I had the thought of making a DB37 breakout so I can easily get a CRO onto and monitor any input/outputs to the EC2. I’ll do this before next Friday enabling testing of electrical systems. I’ll check the CAS signal amplitude and check the injector signals. I would like to get a video recorder, recording everything as I always forget to check some parameter each time I’m testing. Steve On 7 Aug 2016, at 4:12 AM, Tracy <flyrotary@lancaironline.net> wrote: Steve wrote: "Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine?" Sort of. That NOP you are seeing is a good indication that the ec2/3 has been jolted out of its normal operating loop and is trying to reboot. The backfiring is too. Electrical noise (probably in the grounding scheme of electrical wiring layout) is the most likely candidate. Tracy Sent from my iPad On Aug 5, 2016, at 17:31, steve Izett <flyrotary@lancaironline.net> wrote: Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine? -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html
On 7 Aug 2016, at 4:12 AM, Tracy <flyrotary@lancaironline.net> wrote:
Steve wrote:
"Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine?"
Sort of. That NOP you are seeing is a good indication that the ec2/3 has been jolted out of its normal operating loop and is trying to reboot. The backfiring is too. Electrical noise (probably in the grounding scheme of electrical wiring layout) is the most likely candidate.
Tracy
Sent from my iPad
On Aug 5, 2016, at 17:31, steve Izett <flyrotary@lancaironline.net> wrote:
Note to Tracy. - Did you incorporate in your code any way of knowing if the EC2 entered a watchdog routine?
--
Homepage: http://www.flyrotary.com/
Archive and UnSub: http://mail.lancaironline.net:81/lists/flyrotary/List.html