work in progress Project: Poncho
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
hasMafSensor boolean flag was not exposed in TunerStudio - fixed
"analoginfo" does not display MAP if hasMafSensor = false but ADC subsystem still enables MAF while hasMafSensor = false. Fixed.
the green capital letters OK after "fatal error" is the one saying that the project matches the firmware, just changed that to 'version'
But overall I do not understand what's the issue.
Let's use an un-fair workaround for now:
1) please download latest bundle & update the firmware. console & TS could stay as is
2) please execute set_engine_type 35 in console
3) that would set all your settings according to https://svn.code.sf.net/p/rusefi/code/trunk/firmware/config/engines/chevrolet_camaro_4.cpp
(technically there is a 30 delay between SVN and build_server so right now you would get a FATAL about TPS/MAP conflict, but that would already be progress)
if it works via the set_engine_type 35 we would still kind of need to figure out what was this issue about did you set debugger already?
"analoginfo" does not display MAP if hasMafSensor = false but ADC subsystem still enables MAF while hasMafSensor = false. Fixed.
the green capital letters OK after "fatal error" is the one saying that the project matches the firmware, just changed that to 'version'
But overall I do not understand what's the issue.
Let's use an un-fair workaround for now:
1) please download latest bundle & update the firmware. console & TS could stay as is
2) please execute set_engine_type 35 in console
3) that would set all your settings according to https://svn.code.sf.net/p/rusefi/code/trunk/firmware/config/engines/chevrolet_camaro_4.cpp
(technically there is a 30 delay between SVN and build_server so right now you would get a FATAL about TPS/MAP conflict, but that would already be progress)
if it works via the set_engine_type 35 we would still kind of need to figure out what was this issue about did you set debugger already?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Thanks for all the help.
I erased the chip and reloaded your version from earlier today and started a new project, reset all the pins and configured as I desired it in TS. All looked good so far except the trigger in DevConsole.
I'm going to update the firmware with your newest version and I'll get back to you.
I erased the chip and reloaded your version from earlier today and started a new project, reset all the pins and configured as I desired it in TS. All looked good so far except the trigger in DevConsole.
I'm going to update the firmware with your newest version and I'll get back to you.
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Some success, Tuner Studio is happy, Dev console is happy, but the trigger looks like below. I have it set up in TS as shown in the picture. The cam signal and the cranks signals are getting through to the pins verified by the oscilloscope. Any suggestions?
- Attachments
-
- Trigger Set up TS.JPG (56.6 KiB) Viewed 16703 times
-
- First Trigger Test.JPG (316.51 KiB) Viewed 16703 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
It's my mistake with the LS 24 trigger shape skeleton but the more I think the more I like it. The reason the signal shows the way it shows is because I mistakenly set the trigger to use just one wire, so it's only reading CAM right now and that's how CAM looks like.
But I actually like it this way. Your logs shows a full cycle as one CAM fall/rise and two revolutions of crank signal, two times 24. On the one hand, we can record this as a 1+24+24=49 tooth two-channel signal but that's not the best way to do it. I suggest you flip your input settings temporary so that primary input becomes PA5 and the secondary you can turn off or set to PC6.
We would record just the CRANK, 24 tooth we expect it to be. Once we have the precise CRANK signal, I would need to implement https://sourceforge.net/p/rusefi/tickets/177/ and once we have #177 we would turn CAM off the right way. While we do not have #177 implemented you would temporary use only CRANK which should be good enough for the first two weeks, you would have to use wasted spark/batched injection but hopefully that would work.
Thank you for your patience
But I actually like it this way. Your logs shows a full cycle as one CAM fall/rise and two revolutions of crank signal, two times 24. On the one hand, we can record this as a 1+24+24=49 tooth two-channel signal but that's not the best way to do it. I suggest you flip your input settings temporary so that primary input becomes PA5 and the secondary you can turn off or set to PC6.
We would record just the CRANK, 24 tooth we expect it to be. Once we have the precise CRANK signal, I would need to implement https://sourceforge.net/p/rusefi/tickets/177/ and once we have #177 we would turn CAM off the right way. While we do not have #177 implemented you would temporary use only CRANK which should be good enough for the first two weeks, you would have to use wasted spark/batched injection but hopefully that would work.
Thank you for your patience
- Attachments
-
- screenshot.png (54.83 KiB) Viewed 16693 times
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Perfect, Thanks for catching that. I swapped the triggers and attached are the readings.
From here I'll try out the batched spark and see if I can get it to match the OEM signals.
From here I'll try out the batched spark and see if I can get it to match the OEM signals.
- Attachments
-
- Crank As Trigger1.png (82.35 KiB) Viewed 16688 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
hold on! We still do not have the trigger shape, it just looks ok but its totally not ok.
Plz attach the log files from that latest run. Is your sensor sniffer in trigget catch mode?
I've expanded http://rusefi.com/wiki/index.php?title=Manual:Software:Trigger#Unknown_trigger_type and http://rusefi.com/wiki/index.php?title=Manual:Software:UnknownTrigger a bit - still needs work but hope it makes things a bit more clear.
Plz attach the log files from that latest run. Is your sensor sniffer in trigget catch mode?
I've expanded http://rusefi.com/wiki/index.php?title=Manual:Software:Trigger#Unknown_trigger_type and http://rusefi.com/wiki/index.php?title=Manual:Software:UnknownTrigger a bit - still needs work but hope it makes things a bit more clear.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Hi,
Thanks. Sorry, I got caught up doing body work on the car. So I just ran the engine with sensor sniffer set to TRIGGER, and attached the images. I also ran the engine for a minute or so and attached the CSV file.
I think those clear it up a bit. Are we thinking of taking the 24 tooth signal and offsetting to find TDC, and firing cylinder 1 and whichever is opposite (batch firing)?
When/if I get some time, I'll browse through the .cpp file page and get familiar with its operation. It looks like there's a wealth of information on there.
Cheers,
Thanks. Sorry, I got caught up doing body work on the car. So I just ran the engine with sensor sniffer set to TRIGGER, and attached the images. I also ran the engine for a minute or so and attached the CSV file.
I think those clear it up a bit. Are we thinking of taking the 24 tooth signal and offsetting to find TDC, and firing cylinder 1 and whichever is opposite (batch firing)?
When/if I get some time, I'll browse through the .cpp file page and get familiar with its operation. It looks like there's a wealth of information on there.
Cheers,
- Attachments
-
- 2016-05-28 18_29rpm_1872_sensor.png (15.45 KiB) Viewed 16678 times
-
- 2016-05-28 18_30rpm_1807_maf_NaN.png (29.57 KiB) Viewed 16678 times
-
- MAIN_rfi_report_2016-05-28 18_35.csv
- (939.43 KiB) Downloaded 733 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
2016-05-28 18_57: EngineState: confirmation_triggerinfo:11
2016-05-28 18_57: EngineState: Template CUSTOM (0) trigger TT_GM_LS_24 (27) useRiseEdge=Yes onlyFront=No gapBothDirections=No useOnlyFirstChannel=No
2016-05-28 18_57: EngineState: trigger#1 event counters up=125608/down=125607
2016-05-28 18_57: EngineState: expected cycle events 48/0/0
2016-05-28 18_57: EngineState: trigger type=27/need2ndChannel=No
2016-05-28 18_57: EngineState: expected duty #0=0.50/#1=0.00
2016-05-28 18_57: EngineState: synchronizationNeeded=No/isError=No/total errors=4 ord_err=2/total revolutions=5235/self=No
2016-05-28 18_57: EngineState: primary trigger input: PA5
2016-05-28 18_57: EngineState: primary trigger simulator: PD1 OM_DEFAULT freq=1200
2016-05-28 18_57: EngineState: trigger error extra LED: NONE OM_DEFAULT
2016-05-28 18_57: EngineState: primary logic input: NONE
2016-05-28 18_57: EngineState: secondary logic input: NONE
2016-05-28 18_57: EngineState: zeroTestTime=5 maxHowFarOff=26165
2016-05-28 18_57: EngineState: advanceLookupTime=1052 now=-296924928 fuelCalcTime=2024
2016-05-28 18_57: EngineState: ignitionMathTime=21 ignitionSchTime=1324 injectonSchTime=1984
2016-05-28 18_57: EngineState: mapTime=23234/hipTime=0/rpmTime=1388/mainTriggerCallbackTime=1792
2016-05-28 18_57: EngineState: maxLockTime=0 / maxTriggerReentraint=0
2016-05-28 18_57: EngineState: maxEventQueueTime=5026
2016-05-28 18_57: EngineState: hipLastExecutionCount=0
2016-05-28 18_57: EngineState: hwSetTimerTime 242
2016-05-28 18_57: EngineState: totalTriggerHandlerMaxTime=44136
2016-05-28 18_57: EngineState: Template CUSTOM (0) trigger TT_GM_LS_24 (27) useRiseEdge=Yes onlyFront=No gapBothDirections=No useOnlyFirstChannel=No
2016-05-28 18_57: EngineState: trigger#1 event counters up=125608/down=125607
2016-05-28 18_57: EngineState: expected cycle events 48/0/0
2016-05-28 18_57: EngineState: trigger type=27/need2ndChannel=No
2016-05-28 18_57: EngineState: expected duty #0=0.50/#1=0.00
2016-05-28 18_57: EngineState: synchronizationNeeded=No/isError=No/total errors=4 ord_err=2/total revolutions=5235/self=No
2016-05-28 18_57: EngineState: primary trigger input: PA5
2016-05-28 18_57: EngineState: primary trigger simulator: PD1 OM_DEFAULT freq=1200
2016-05-28 18_57: EngineState: trigger error extra LED: NONE OM_DEFAULT
2016-05-28 18_57: EngineState: primary logic input: NONE
2016-05-28 18_57: EngineState: secondary logic input: NONE
2016-05-28 18_57: EngineState: zeroTestTime=5 maxHowFarOff=26165
2016-05-28 18_57: EngineState: advanceLookupTime=1052 now=-296924928 fuelCalcTime=2024
2016-05-28 18_57: EngineState: ignitionMathTime=21 ignitionSchTime=1324 injectonSchTime=1984
2016-05-28 18_57: EngineState: mapTime=23234/hipTime=0/rpmTime=1388/mainTriggerCallbackTime=1792
2016-05-28 18_57: EngineState: maxLockTime=0 / maxTriggerReentraint=0
2016-05-28 18_57: EngineState: maxEventQueueTime=5026
2016-05-28 18_57: EngineState: hipLastExecutionCount=0
2016-05-28 18_57: EngineState: hwSetTimerTime 242
2016-05-28 18_57: EngineState: totalTriggerHandlerMaxTime=44136
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
Do you have a timing gun and a timing mark somewhere on the engine?
If you do not have a timing mark on the engine you can make a timing mark yourself as long as you have OBD showing you current ignition timing while running on stock ECU. Either existing or your own timing mark would tell you a reference point on your engine with known timing advance value.
Please update firmware to version 20160528 in about 30 minutes and that you give the real LS 24 trigger shape. What it would not give you is the correct zero degree location, and that's something you need to figure out either using a timing gun and a known reference point or any other way
One of your links says
If you do not have a timing mark on the engine you can make a timing mark yourself as long as you have OBD showing you current ignition timing while running on stock ECU. Either existing or your own timing mark would tell you a reference point on your engine with known timing advance value.
Please update firmware to version 20160528 in about 30 minutes and that you give the real LS 24 trigger shape. What it would not give you is the correct zero degree location, and that's something you need to figure out either using a timing gun and a known reference point or any other way
One of your links says
The data we have collected so far isThe crankshaft reluctor wheel is mounted on the rear of the crankshaft. The wheel is comprised of four 90 degree segments. Each segment represents a pair of cylinders at TDC , and is further divided into six 15 degree segments. Within each 15 degree segment is a notch of 1 of 2 different sizes. Each 90 degree segment has a unique pattern of notches.
the 15 degree segments are assuming a 360 disk and it looks like in the code it uses a 720 logical cycle so 15 degrees segments becomes 30 degrees segments, so 27.59 is probably our precision of 30 and say 57.58 is probably our precision of 60. I guess this precision is good enough for now.s->addEvent(22.2733333333334, ch, TV_RISE);
s->addEvent(27.59333333333338, ch, TV_FALL);
s->addEvent(51.18333333333338, ch, TV_RISE);
s->addEvent(57.58333333333338, ch, TV_FALL);
s->addEvent(81.17333333333337, ch, TV_RISE);
s->addEvent(87.61333333333339, ch, TV_FALL);
s->addEvent(111.30666666666671, ch, TV_RISE);
s->addEvent(117.81000000000004, ch, TV_FALL);
s->addEvent(141.50000000000006, ch, TV_RISE);
s->addEvent(148.05666666666673, ch, TV_FALL);
s->addEvent(153.41333333333338, ch, TV_RISE);
s->addEvent(178.29333333333338, ch, TV_FALL);
s->addEvent(183.51000000000005, ch, TV_RISE);
s->addEvent(208.3266666666667, ch, TV_FALL);
s->addEvent(213.50000000000006, ch, TV_RISE);
s->addEvent(238.26000000000005, ch, TV_FALL);
s->addEvent(243.51000000000005, ch, TV_RISE);
s->addEvent(268.27000000000004, ch, TV_FALL);
s->addEvent(273.53666666666675, ch, TV_RISE);
s->addEvent(298.35, ch, TV_FALL);
s->addEvent(321.86333333333334, ch, TV_RISE);
s->addEvent(328.4966666666667, ch, TV_FALL);
s->addEvent(333.81000000000006, ch, TV_RISE);
s->addEvent(358.66, ch, TV_FALL);
s->addEvent(363.8633333333334, ch, TV_RISE);
s->addEvent(388.7033333333334, ch, TV_FALL);
s->addEvent(393.88000000000005, ch, TV_RISE);
s->addEvent(418.62000000000006, ch, TV_FALL);
s->addEvent(441.9566666666667, ch, TV_RISE);
s->addEvent(448.6700000000001, ch, TV_FALL);
s->addEvent(472.1000000000001, ch, TV_RISE);
s->addEvent(478.9333333333334, ch, TV_FALL);
s->addEvent(484.08000000000004, ch, TV_RISE);
s->addEvent(509.1333333333334, ch, TV_FALL);
s->addEvent(514.2666666666667, ch, TV_RISE);
s->addEvent(539.1733333333334, ch, TV_FALL);
s->addEvent(562.5166666666668, ch, TV_RISE);
s->addEvent(569.1133333333333, ch, TV_FALL);
s->addEvent(592.5400000000001, ch, TV_RISE);
s->addEvent(599.1433333333334, ch, TV_FALL);
s->addEvent(622.6300000000001, ch, TV_RISE);
s->addEvent(629.2633333333334, ch, TV_FALL);
s->addEvent(634.6, ch, TV_RISE);
s->addEvent(659.5, ch, TV_FALL);
s->addEvent(683.1133333333333, ch, TV_RISE);
s->addEvent(689.77, ch, TV_FALL);
s->addEvent(695.0666666666667, ch, TV_RISE);
s->addEvent(720.0, ch, TV_FALL);
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
I will have to make a timing mark on this engine.
I have the signals coming from the OEM in parallel, I was hoping to be able to scope the two signals simultaneously and then progressively change the offset until they lined up.
Using the firing order, I put together the attached table to show the cylinders' operations. If using batched we can probably chose the ignition to go off when the cylinders are at TDC ign & TDC Open. (basically sparking like a two stroke).
Oh now the 24x wheel is starting to make sense, it's nice to see the falling events almost lining up to the expected angles.
I'll have the new firmware updated in a minute and head out to the shop to start it up.
I have the signals coming from the OEM in parallel, I was hoping to be able to scope the two signals simultaneously and then progressively change the offset until they lined up.
Using the firing order, I put together the attached table to show the cylinders' operations. If using batched we can probably chose the ignition to go off when the cylinders are at TDC ign & TDC Open. (basically sparking like a two stroke).
Oh now the 24x wheel is starting to make sense, it's nice to see the falling events almost lining up to the expected angles.
I'll have the new firmware updated in a minute and head out to the shop to start it up.
- Attachments
-
- Cylinder Operation.JPG (71.78 KiB) Viewed 16681 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Here is the run with updated Firmware
- Attachments
-
- MAIN_rfi_report_2016-05-28_22_21.csv
- (68.03 KiB) Downloaded 735 times
-
- 2016-05-28_22_23rpm_1418_maf_NaN.png (33.44 KiB) Viewed 16676 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
You are very close to have rusEfi control fuel or spark I will need to implement that #177 soon.
the defect you were hitting is fixed - https://sourceforge.net/p/rusefi/tickets/288/Nehrenholz wrote:I have the MAP sent into INP3 which goes to PA0. On tuner studio I tried to disable both, tried to set one up with PA0 and the other disabled but no luck. Any ideas?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Thank you it definitely had me stumped for a while! My Internet modem is broken, getting replaced soon, so no activity until Friday unfortunately.
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
I bench tested the output for the spark in both dev and TS. The pin outputs for the bench test, but not when running? Any thoughts? I ran out of gasoline so I'm not able to run for tonight.
- Attachments
-
- IMG_20160603_215732.jpg (424.99 KiB) Viewed 16622 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
Please post your CurrentTune.msq and your log file. Please elaborate where and how are you testing on a bench?
Just to check, do you have a VP<>5v or VP<>12v jumper on your high side drivers?
PS: also looks very similar to http://rusefi.com/forum/viewtopic.php?f=3&t=660#p18863
Just to check, do you have a VP<>5v or VP<>12v jumper on your high side drivers?
PS: also looks very similar to http://rusefi.com/forum/viewtopic.php?f=3&t=660#p18863
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
The bench test is just activating the HL pins via the dev console or the TS ( it just sends what I can see as a momentary pulse on the oscilloscope). I'll send the tune out to you as soon as I get back. And yeah that thread looks pretty similar I'll subscribe and work through with that one too.
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
I would also remove the spark plugs and leave them on something metal on the block to see the actual spark while testing IO.Nehrenholz wrote:The bench test is just activating the HL pins via the dev console or the TS ( it just sends what I can see as a momentary pulse on the oscilloscope).
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
That would do it. I'll put the some 5V jumpers in and get back to you.russian wrote:Just to check, do you have a VP<>5v or VP<>12v jumper on your high side drivers?
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
So here are some short videos of the signals. Channel 1 (yellow) is the OEM timing and channel two is the RUSEFI. In TS I haven't been able to offset the signal, I'm probably doing it incorrectly. I am going Engine>Trigger>globalOffsetAngle(deg) Typing in a value pressing burn and nothing happens. I also tried reseting the ST board, no luck yet. Is there a command for the DevConsole to initiate the offset?
It looks like there's only 4 ingniter signals being used for the batched timing, is that correct? I'll start off by trying to only control 4 cylinders for now until we get the 8 sequential code working.
https://www.youtube.com/watch?v=1BiUUmlIzN8
https://www.youtube.com/watch?v=2obcLBi5VW4
https://www.youtube.com/watch?v=Wrsd36Kisig
MSQ is attached
It looks like there's only 4 ingniter signals being used for the batched timing, is that correct? I'll start off by trying to only control 4 cylinders for now until we get the 8 sequential code working.
https://www.youtube.com/watch?v=1BiUUmlIzN8
https://www.youtube.com/watch?v=2obcLBi5VW4
https://www.youtube.com/watch?v=Wrsd36Kisig
MSQ is attached
- Attachments
-
[The extension msq has been deactivated and can no longer be displayed.]
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Cylinder two. OEM yellow. RusEFI blue.
- Attachments
-
- IMG_20160606_145852.jpg (438.74 KiB) Viewed 16541 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
In wasted/batch you have half the number of cylinders number of different signals, by default these are routed if half the number of cylinders wires since usually two spark plugs on coil or two injectors on a wire. If your case of individually wired everything you can use "Two wire batch injection" and/or "Two wire wasted igntion" to send the same signal into two wires.
Does rusEfi RPM match OEM tach RPM?
Is your orange LED constantly blinking? I believe orange LED is trigger decoding error indicator.
Please disable SD card logging or add an SD card so that the warning goes away so that we might see other warnings, I need to add warning priority of some sort.
Please upload rusEfi log file.
Should not matter much in your case but FYI the chip cannot burn changes into flash memory while your engine is running - see 'writeconfig' notes @ http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands
The command you've asked about is set_global_trigger_offset_angle XXX
console is really unreliable over TTL, microUSB VCP seems much better
Does rusEfi RPM match OEM tach RPM?
Is your orange LED constantly blinking? I believe orange LED is trigger decoding error indicator.
Please disable SD card logging or add an SD card so that the warning goes away so that we might see other warnings, I need to add warning priority of some sort.
Please upload rusEfi log file.
Should not matter much in your case but FYI the chip cannot burn changes into flash memory while your engine is running - see 'writeconfig' notes @ http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands
The command you've asked about is set_global_trigger_offset_angle XXX
console is really unreliable over TTL, microUSB VCP seems much better
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Here's the output from trying to offset command. The Rusefi file was too big to attach I'll run a shorter one.
2016-06-06 16_14: EngineState: confirmation_set_global_trigger_offset_angle 20:34
2016-06-06 16_14: EngineState: Template CUSTOM/0 trigger TT_GM_LS_24/LM_SPEED_DENSITY/3
2016-06-06 16_14: EngineState: configurationVersion=1
2016-06-06 16_14: EngineState: rpmHardLimit: 7000/operationMode=2
2016-06-06 16_14: EngineState: globalTriggerAngleOffset=20.00
2016-06-06 16_14: EngineState: === cranking ===
2016-06-06 16_14: EngineState: crankingRpm: 550
2016-06-06 16_14: EngineState: cranking injection IM_SIMULTANEOUS
2016-06-06 16_14: EngineState: cranking charge charge angle=10.00 fire at 0.00
2016-06-06 16_14: EngineState: === ignition ===
2016-06-06 16_14: EngineState: ignitionMode: IM_INDIVIDUAL_COILS/enabled=Yes
2016-06-06 16_14: EngineState: timingMode: TM_DYNAMIC
2016-06-06 16_14: EngineState: ignitionOffset=0.00
2016-06-06 16_14: EngineState: === injection ===
2016-06-06 16_14: EngineState: injection IM_SEQUENTIAL offset=0.00/enabled=Yes
2016-06-06 16_14: EngineState: injectionPins: mode OM_DEFAULT
2016-06-06 16_14: EngineState: injection #1 @ PE6
2016-06-06 16_14: EngineState: injection #2 @ PE5
2016-06-06 16_14: EngineState: injection #3 @ PD7
2016-06-06 16_14: EngineState: injection #4 @ PC13
2016-06-06 16_14: EngineState: injection #5 @ PE3
2016-06-06 16_14: EngineState: injection #6 @ PE4
2016-06-06 16_14: EngineState: injection #7 @ PD3
2016-06-06 16_14: EngineState: injection #8 @ PE2
2016-06-06 16_14: EngineState: ignitionPins: mode OM_DEFAULT
2016-06-06 16_14: EngineState: ignition #1 @ PC9
2016-06-06 16_14: EngineState: ignition #2 @ PC7
2016-06-06 16_14: EngineState: ignition #3 @ PE14
2016-06-06 16_14: EngineState: ignition #4 @ PE12
2016-06-06 16_14: EngineState: ignition #5 @ PE10
2016-06-06 16_14: EngineState: ignition #6 @ PE8
2016-06-06 16_14: EngineState: ignition #7 @ PD9
2016-06-06 16_14: EngineState: ignition #8 @ PD8
2016-06-06 16_14: EngineState: idlePin: mode OM_DEFAULT @ PB7 freq=200
2016-06-06 16_14: EngineState: malfunctionIndicatorn: NONE mode=OM_DEFAULT
2016-06-06 16_14: EngineState: fuelPumpPin: mode OM_DEFAULT @ PB8
2016-06-06 16_14: EngineState: fanPin: mode OM_DEFAULT @ PB9
2016-06-06 16_14: EngineState: mainRelay: mode OM_DEFAULT @ PD5
2016-06-06 16_14: EngineState: alternator field: mode OM_DEFAULT @ NONE
2016-06-06 16_14: EngineState: map_avg=Yes/mil=Yes/fp=Yes/ts=Yes/wa=Yes/it=Yes/fastAdc=Yes
2016-06-06 16_14: EngineState: isManualSpinningMode=No/isCylinderCleanupEnabled=Yes
2016-06-06 16_14: EngineState: clutchUp@NONE: No
2016-06-06 16_14: EngineState: clutchDown@NONE: No
2016-06-06 16_14: EngineState: boardTestModeJumperPin: PB0/nesting=3
2016-06-06 16_14: EngineState: digitalPotentiometerSpiDevice 0
2016-06-06 16_14: EngineState: digitalPotentiometer CS0 PD7
2016-06-06 16_14: EngineState: digitalPotentiometer CS1 NONE
2016-06-06 16_14: EngineState: digitalPotentiometer CS2 PD5
2016-06-06 16_14: EngineState: digitalPotentiometer CS3 NONE
2016-06-06 16_14: EngineState: spi 1=No/2=No/3=Yes
2016-06-06 16_14: EngineState: EL accel th=5.00/mult=2.00
2016-06-06 16_14: EngineState: EL decel th=0.00/mult=0.00
2016-06-06 16_14: EngineState: TPS accel th=40.00/mult=0.04
2016-06-06 16_14: EngineState: added to wall=0.00/sucked=0.00
2016-06-06 16_14: EngineState: EL accel th=5.00/mult=2.00
2016-06-06 16_14: EngineState: EL decel th=0.00/mult=0.00
2016-06-06 16_14: EngineState: TPS accel th=40.00/mult=0.04
2016-06-06 16_14: EngineState: added to wall=0.00/sucked=0.00
2016-06-06 16_14: EngineState: Stimulator: updating trigger shape: 1/1 351620
2016-06-06 16_14: EngineState: applyNonPersistentConfiguration()
2016-06-06 16_14: EngineState: initializeTriggerShape(TT_GM_LS_24/27)
2016-06-06 16_14: EngineState: gap=NaN/NaN/NaN @ 0 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: error: synchronizationPoint @ index 28 expected 48/0/0 got 29/0/0
2016-06-06 16_14: EngineState: gap=0.62/1.60/0.99 @ 1 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/0.62/1.60 @ 3 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.51/0.39/0.62 @ 5 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.59/2.51/0.39 @ 7 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.62/1.59/2.51 @ 9 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/0.62/1.59 @ 11 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/1.00/0.62 @ 13 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=4.05/0.39/1.00 @ 15 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.24/4.05/0.39 @ 17 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=3.94/0.24/4.05 @ 19 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.61/3.94/0.24 @ 21 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.03/0.61/3.94 @ 23 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.03/0.61 @ 25 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.00/1.03 @ 27 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/1.00/1.00 @ 29 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.52/0.39/1.00 @ 31 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.99/2.52/0.39 @ 33 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/0.99/2.52 @ 35 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.00/0.99 @ 37 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.60/1.00/1.00 @ 39 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.24/1.60/1.00 @ 41 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.51/0.24/1.60 @ 43 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.99/2.51/0.24 @ 45 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.60/0.99/2.51 @ 47 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.62/1.60/0.99 @ 1 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/0.62/1.60 @ 3 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.51/0.39/0.62 @ 5 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.59/2.51/0.39 @ 7 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.62/1.59/2.51 @ 9 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/0.62/1.59 @ 11 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/1.00/0.62 @ 13 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=4.05/0.39/1.00 @ 15 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.24/4.05/0.39 @ 17 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=3.94/0.24/4.05 @ 19 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.61/3.94/0.24 @ 21 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.03/0.61/3.94 @ 23 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.03/0.61 @ 25 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.00/1.03 @ 27 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/1.00/1.00 @ 29 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.52/0.39/1.00 @ 31 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.99/2.52/0.39 @ 33 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/0.99/2.52 @ 35 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.00/0.99 @ 37 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.60/1.00/1.00 @ 39 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.24/1.60/1.00 @ 41 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.51/0.24/1.60 @ 43 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.99/2.51/0.24 @ 45 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.60/0.99/2.51 @ 47 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: confirmation_set_global_trigger_offset_angle 20:34
2016-06-06 16_14: EngineState: Template CUSTOM/0 trigger TT_GM_LS_24/LM_SPEED_DENSITY/3
2016-06-06 16_14: EngineState: configurationVersion=1
2016-06-06 16_14: EngineState: rpmHardLimit: 7000/operationMode=2
2016-06-06 16_14: EngineState: globalTriggerAngleOffset=20.00
2016-06-06 16_14: EngineState: === cranking ===
2016-06-06 16_14: EngineState: crankingRpm: 550
2016-06-06 16_14: EngineState: cranking injection IM_SIMULTANEOUS
2016-06-06 16_14: EngineState: cranking charge charge angle=10.00 fire at 0.00
2016-06-06 16_14: EngineState: === ignition ===
2016-06-06 16_14: EngineState: ignitionMode: IM_INDIVIDUAL_COILS/enabled=Yes
2016-06-06 16_14: EngineState: timingMode: TM_DYNAMIC
2016-06-06 16_14: EngineState: ignitionOffset=0.00
2016-06-06 16_14: EngineState: === injection ===
2016-06-06 16_14: EngineState: injection IM_SEQUENTIAL offset=0.00/enabled=Yes
2016-06-06 16_14: EngineState: injectionPins: mode OM_DEFAULT
2016-06-06 16_14: EngineState: injection #1 @ PE6
2016-06-06 16_14: EngineState: injection #2 @ PE5
2016-06-06 16_14: EngineState: injection #3 @ PD7
2016-06-06 16_14: EngineState: injection #4 @ PC13
2016-06-06 16_14: EngineState: injection #5 @ PE3
2016-06-06 16_14: EngineState: injection #6 @ PE4
2016-06-06 16_14: EngineState: injection #7 @ PD3
2016-06-06 16_14: EngineState: injection #8 @ PE2
2016-06-06 16_14: EngineState: ignitionPins: mode OM_DEFAULT
2016-06-06 16_14: EngineState: ignition #1 @ PC9
2016-06-06 16_14: EngineState: ignition #2 @ PC7
2016-06-06 16_14: EngineState: ignition #3 @ PE14
2016-06-06 16_14: EngineState: ignition #4 @ PE12
2016-06-06 16_14: EngineState: ignition #5 @ PE10
2016-06-06 16_14: EngineState: ignition #6 @ PE8
2016-06-06 16_14: EngineState: ignition #7 @ PD9
2016-06-06 16_14: EngineState: ignition #8 @ PD8
2016-06-06 16_14: EngineState: idlePin: mode OM_DEFAULT @ PB7 freq=200
2016-06-06 16_14: EngineState: malfunctionIndicatorn: NONE mode=OM_DEFAULT
2016-06-06 16_14: EngineState: fuelPumpPin: mode OM_DEFAULT @ PB8
2016-06-06 16_14: EngineState: fanPin: mode OM_DEFAULT @ PB9
2016-06-06 16_14: EngineState: mainRelay: mode OM_DEFAULT @ PD5
2016-06-06 16_14: EngineState: alternator field: mode OM_DEFAULT @ NONE
2016-06-06 16_14: EngineState: map_avg=Yes/mil=Yes/fp=Yes/ts=Yes/wa=Yes/it=Yes/fastAdc=Yes
2016-06-06 16_14: EngineState: isManualSpinningMode=No/isCylinderCleanupEnabled=Yes
2016-06-06 16_14: EngineState: clutchUp@NONE: No
2016-06-06 16_14: EngineState: clutchDown@NONE: No
2016-06-06 16_14: EngineState: boardTestModeJumperPin: PB0/nesting=3
2016-06-06 16_14: EngineState: digitalPotentiometerSpiDevice 0
2016-06-06 16_14: EngineState: digitalPotentiometer CS0 PD7
2016-06-06 16_14: EngineState: digitalPotentiometer CS1 NONE
2016-06-06 16_14: EngineState: digitalPotentiometer CS2 PD5
2016-06-06 16_14: EngineState: digitalPotentiometer CS3 NONE
2016-06-06 16_14: EngineState: spi 1=No/2=No/3=Yes
2016-06-06 16_14: EngineState: EL accel th=5.00/mult=2.00
2016-06-06 16_14: EngineState: EL decel th=0.00/mult=0.00
2016-06-06 16_14: EngineState: TPS accel th=40.00/mult=0.04
2016-06-06 16_14: EngineState: added to wall=0.00/sucked=0.00
2016-06-06 16_14: EngineState: EL accel th=5.00/mult=2.00
2016-06-06 16_14: EngineState: EL decel th=0.00/mult=0.00
2016-06-06 16_14: EngineState: TPS accel th=40.00/mult=0.04
2016-06-06 16_14: EngineState: added to wall=0.00/sucked=0.00
2016-06-06 16_14: EngineState: Stimulator: updating trigger shape: 1/1 351620
2016-06-06 16_14: EngineState: applyNonPersistentConfiguration()
2016-06-06 16_14: EngineState: initializeTriggerShape(TT_GM_LS_24/27)
2016-06-06 16_14: EngineState: gap=NaN/NaN/NaN @ 0 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: error: synchronizationPoint @ index 28 expected 48/0/0 got 29/0/0
2016-06-06 16_14: EngineState: gap=0.62/1.60/0.99 @ 1 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/0.62/1.60 @ 3 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.51/0.39/0.62 @ 5 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.59/2.51/0.39 @ 7 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.62/1.59/2.51 @ 9 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/0.62/1.59 @ 11 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/1.00/0.62 @ 13 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=4.05/0.39/1.00 @ 15 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.24/4.05/0.39 @ 17 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=3.94/0.24/4.05 @ 19 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.61/3.94/0.24 @ 21 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.03/0.61/3.94 @ 23 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.03/0.61 @ 25 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.00/1.03 @ 27 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/1.00/1.00 @ 29 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.52/0.39/1.00 @ 31 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.99/2.52/0.39 @ 33 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/0.99/2.52 @ 35 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.00/0.99 @ 37 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.60/1.00/1.00 @ 39 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.24/1.60/1.00 @ 41 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.51/0.24/1.60 @ 43 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.99/2.51/0.24 @ 45 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.60/0.99/2.51 @ 47 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.62/1.60/0.99 @ 1 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/0.62/1.60 @ 3 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.51/0.39/0.62 @ 5 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.59/2.51/0.39 @ 7 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.62/1.59/2.51 @ 9 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/0.62/1.59 @ 11 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/1.00/0.62 @ 13 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=4.05/0.39/1.00 @ 15 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.24/4.05/0.39 @ 17 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=3.94/0.24/4.05 @ 19 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.61/3.94/0.24 @ 21 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.03/0.61/3.94 @ 23 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.03/0.61 @ 25 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.00/1.03 @ 27 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.39/1.00/1.00 @ 29 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.52/0.39/1.00 @ 31 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.99/2.52/0.39 @ 33 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/0.99/2.52 @ 35 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.00/1.00/0.99 @ 37 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.60/1.00/1.00 @ 39 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.24/1.60/1.00 @ 41 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=2.51/0.24/1.60 @ 43 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=0.99/2.51/0.24 @ 45 while expected 1.20/2.00 and 0.75/1.25 error=1
2016-06-06 16_14: EngineState: gap=1.60/0.99/2.51 @ 47 while expected 1.20/2.00 and 0.75/1.25 error=1
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
The orange LED is blinking. I tried unmountsd but couldn't disable the SD card.
- Attachments
-
- MAIN_rfi_report_2016-06-06_16_09.csv
- (7.14 MiB) Downloaded 624 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
The one you want is disable sd - http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands#Logging
false alarm - blinking orange is communcation, it is probably solid orange which is trigger error
false alarm - blinking orange is communcation, it is probably solid orange which is trigger error
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
I do not have a tach out for the engine but the RPMs seem close, and the signals seem to be operating on the same frequency or possibly a multiple of the frequency.
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
I tried a 45 offset in TS and a 30 in devconsole. But it is still the same signal. I configured to two wire batched.
- Attachments
-
- IMG_20160606_163453.jpg (397.55 KiB) Viewed 16497 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
TTL console sucks - it takes a number of attempts to execute "set_global_trigger_offset_angle XXX" but I definitely see the green vertical line moving in relation to the trigger pattern, so the command does work on the fly. microUSB connectivity on the discovery works much better.
30 would be 5% of the 720 degree cycle, do you want to try 100, 200 or 300?
30 would be 5% of the 720 degree cycle, do you want to try 100, 200 or 300?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Thanks, Still giving the warning though.
2016-06-06 16_42: EngineState: confirmation_disable sd:10
2016-06-06 16_42: EngineState: [sd] disabled
2016-06-06 16_43: EngineState: WARNING: Can't connect or mount MMC/SD
https://www.youtube.com/watch?v=SG4jJUuBwXs
Note the LEDs and there's one output LED (blue) that is stuck on.
2016-06-06 16_42: EngineState: confirmation_disable sd:10
2016-06-06 16_42: EngineState: [sd] disabled
2016-06-06 16_43: EngineState: WARNING: Can't connect or mount MMC/SD
https://www.youtube.com/watch?v=SG4jJUuBwXs
Note the LEDs and there's one output LED (blue) that is stuck on.
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
- AndreyB
- Site Admin
- Posts: 14327
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Project: Poncho
you need writeconfig/reset for 'disable s'd to be applied.
Just verified that TunerStudio trigger offset change work - I am changing by 100 at a time and I see the green line move on the engine sniffer tab.
Just verified that TunerStudio trigger offset change work - I am changing by 100 at a time and I see the green line move on the engine sniffer tab.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Nehrenholz
- Posts: 49
- Joined: Sat Oct 17, 2015 5:02 am
- Location: Vancouver
Re: Project: Poncho
Cylinder one lined up. 230 degrees offset.
- Attachments
-
- IMG_20160606_190221.jpg (421.37 KiB) Viewed 16473 times
Nathan Ehrenholz
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751
Mechatronic Systems Engineering Student
Simon Fraser University
e: nehrenho@sfu.ca | LinkedIn: http://ca.linkedin.com/pub/nathan-ehrenholz/46/b9a/751