Anyone experience this with gasper FADEC.
#1
![Default](https://www.rcuniverse.com/forum/images/icons/icon1.gif)
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /><meta content="Word.Document" name="ProgId" /><meta content="Microsoft Word 10" name="Generator" /><meta content="Microsoft Word 10" name="Originator" /><link href="file:///C:\DOCUME~1\CHAITA~1\LOCALS~1\Temp\msohtml1\01\cli p_filelist.xml" rel="File-List" /><![if gte mso 9]><xml><w:WordDocument><w:View>Normal</w:View><w:Zoom>0</w:Zoom><w:Compatibility><w:BreakWrappedTables /><w:SnapToGridInCell /><w:WrapTextWithPunct /><w:UseAsianBreakRules /><w:UseFELayout /></w:Compatibility><w:BrowserLevel>MicrosoftInternetE xplorer4</w:BrowserLevel></w:WordDocument></xml><![endif]><style type="text/css"><! Font Definitions */ @font-face {font-family:SimSun; panose-1:2 1 6 0 3 1 1 1 1 1; mso-font-alt:宋体; mso-font-charset:134; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:3 135135232 16 0 262145 0;}@font-face {font-family:"\@SimSun"; panose-1:2 1 6 0 3 1 1 1 1 1; mso-font-charset:134; mso-generic-font-family:auto; mso-font-pitch:variable; mso-font-signature:3 135135232 16 0 262145 0;} Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:SimSun;}@page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;}div.Section1 {page:Section1;}></style><![if gte mso 10]><style> Style Definitions */table.MsoNormalTable{mso-style-name:"Table Normal";mso-tstyle-rowband-size:0;mso-tstyle-colband-size:0;mso-style-noshow:yes;mso-style-parent:"";mso-padding-alt:0in 5.4pt 0in 5.4pt;mso-para-margin:0in;mso-para-margin-bottom:.0001pt;mso-pagination:widow-orphan;font-size:10.0pt;font-family:"Times New Roman";}</style><![endif]><p class="MsoNormal">Hi Guys,
Just ran up my Wren 160 yesterday in my comp-arf flash. The turbine started first shot and came up to idle rpm very smoothly. I then did the 5 second calibration for the ECU. I then slammed opened thrust, and the engine spooled up nicely to 125000 RPM, when I got the stick back to idle the turbine shut down and the data terminal went blank. The turbine did not go into cooling cycle.</p><p class="MsoNormal">When I reached home I turned on the system again with the 160 data terminal connected, the system was still blank. I then tried connecting my super sport data terminal which was also blank. I switched off the system and turned it on again with the super sport data terminal connected and this time the display came on.</p><p class="MsoNormal">No matter what I do the 160 data terminal remains blank.</p><p class="MsoNormal"><o
></o
></p><p class="MsoNormal">My question is, is it just the data terminal which has failed? Or is there some problem with the fadec? If it was just the data terminal which failed, why did the turbine shut down?</p><p class="MsoNormal">Thanks for all the help. Just would not like to have a flame out on the maiden.</p><p class="MsoNormal"><o
></o
></p><p class="MsoNormal"><o
></o
></p><p class="MsoNormal">Chaitanya.</p>
Just ran up my Wren 160 yesterday in my comp-arf flash. The turbine started first shot and came up to idle rpm very smoothly. I then did the 5 second calibration for the ECU. I then slammed opened thrust, and the engine spooled up nicely to 125000 RPM, when I got the stick back to idle the turbine shut down and the data terminal went blank. The turbine did not go into cooling cycle.</p><p class="MsoNormal">When I reached home I turned on the system again with the 160 data terminal connected, the system was still blank. I then tried connecting my super sport data terminal which was also blank. I switched off the system and turned it on again with the super sport data terminal connected and this time the display came on.</p><p class="MsoNormal">No matter what I do the 160 data terminal remains blank.</p><p class="MsoNormal"><o
![Stick Out Tongue](https://www.rcuniverse.com/forum/images/smilies/tongue.gif)
![Stick Out Tongue](https://www.rcuniverse.com/forum/images/smilies/tongue.gif)
![Stick Out Tongue](https://www.rcuniverse.com/forum/images/smilies/tongue.gif)
![Stick Out Tongue](https://www.rcuniverse.com/forum/images/smilies/tongue.gif)
![Stick Out Tongue](https://www.rcuniverse.com/forum/images/smilies/tongue.gif)
![Stick Out Tongue](https://www.rcuniverse.com/forum/images/smilies/tongue.gif)
#4
![](/forum/images/badges/trading_plus_member.png)
My Feedback: (39)
Join Date: Jan 2003
Location: Decatur, IN
Posts: 1,284
Likes: 0
Received 0 Likes
on
0 Posts
![Default](https://www.rcuniverse.com/forum/images/icons/icon1.gif)
Chaitanya,
Sounds as though you have two separate problems:
On the first start, after your 160 establishes idle at 28,000...slowly advance the throttle to full rpm, and wait for it to settle at 126,000, then slowly return to idle..This will learn the system. Also check the deceleration value on your GSU display, as it is quite possible the motor quit due to a low value being set on the decel parameter.
As far as the blank screen, sounds as though you have a data plug partialy connected.
I'll forward this thread to Mike Murphy in England for further comments.
Ron
Sounds as though you have two separate problems:
On the first start, after your 160 establishes idle at 28,000...slowly advance the throttle to full rpm, and wait for it to settle at 126,000, then slowly return to idle..This will learn the system. Also check the deceleration value on your GSU display, as it is quite possible the motor quit due to a low value being set on the decel parameter.
As far as the blank screen, sounds as though you have a data plug partialy connected.
I'll forward this thread to Mike Murphy in England for further comments.
Ron
#5
![Default](https://www.rcuniverse.com/forum/images/icons/icon1.gif)
Hi Ron,
</p>
You may be right about increasing the decel value, I did increase the accel value to 25(factory set was 4) because the intakes on the flash are a bit small for the 160. I did increase the stick to full thrust over 5 seconds and then got the stick slowly down. The data plug was connected correctly. its just that the 160 data terminal is dead while the other data terminal shows display.
</p>
Chaitanya.</p>