The setup -- RV-7 with Dual G3X Touch, GMA 245 Audio, GEA 24, etc. etc. Ad $-eum. Dual Plasma III ignitions, key switch.
The symptom -- Each Plasma III "ignition active" signal is connected to the GP inputs on the GEA 24, and are configured to generate a CAS message when active (LO). During run up @ 2000RPM, selecting "L" ignition generates a "BONG" and a flashing RED CAS message, selecting "R" ignition also generates a "BONG" and a flashing RED CAS message.
Starting with the 9.14 update (or so), when switching to the "R" ignition the "BONG" has stopped -- most of the time; the RED CAS message appears and is correct. If I wait for 4+ seconds or more when switching between ignitions, I can make the "BONG" happen.
I do not believe this is related to the specific inputs of triggers in the CAS but a new queueing delay added at some point between CAS events. Perhaps this is a side effect of the GP combination logic (If-then-else) that was added to the software release.
G3Xpert - can you look into this?
Anyone else run into this behavior?
Brian
The symptom -- Each Plasma III "ignition active" signal is connected to the GP inputs on the GEA 24, and are configured to generate a CAS message when active (LO). During run up @ 2000RPM, selecting "L" ignition generates a "BONG" and a flashing RED CAS message, selecting "R" ignition also generates a "BONG" and a flashing RED CAS message.
Starting with the 9.14 update (or so), when switching to the "R" ignition the "BONG" has stopped -- most of the time; the RED CAS message appears and is correct. If I wait for 4+ seconds or more when switching between ignitions, I can make the "BONG" happen.
I do not believe this is related to the specific inputs of triggers in the CAS but a new queueing delay added at some point between CAS events. Perhaps this is a side effect of the GP combination logic (If-then-else) that was added to the software release.
G3Xpert - can you look into this?
Anyone else run into this behavior?
Brian
