Just forked the v12 thread to https://rusefi.com/forum/viewtopic.php?f=3&t=1499mk e wrote: ↑Wed Jan 02, 2019 11:30 pmhttp://gemellocattivo.com/forum/viewtopic.php?f=2&t=8
Now back to ETB
[info] electronic throttle body control ETB
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
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
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
E38 1998 BMW 750 has two stepped motors with four windings driving each throttle plate - 8 windings per throttle body. Would it be possible to combine four "cos" wires and four "sin" wires to drive each ETB with one VNH2SP30TR-E?
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
Re: electronic throttle body control ETB
From the picture, I think no you cannot drive both from one driver. It appears to show the two are out of phase with each other. I think if you activate both, you'll fight with each other and have less effect than if you activated just one. I would wager that they allowed one motor to technically drive it, and the second one is semi-redundant. You could try driving it with only one of the motors and see what happens. I would suggest connecting the unused coils together, to prevent them from building up a charge.
I also suspect they step motor 1, then turn it off when they do motor 2. Most steppers are 100% on. However with 2 motors, motor 1 might only be on for around 50% of the time. The result is less heat in the motor driver, and less heat in the motor coils. I suspect that could be done like that as a method of micro-stepping with the slow transistors they had back in the late 90's.
Any how I suggest trying one driver, and see what happens. Also probably don't do it for very long, as it will likely get hot.
I think a long term solution is less easy than you might prefer. Perhaps you can do it with 2 drivers, with enable lines connected to the STM32. Same pulse and direction, but you add the enable lines to half step it.
I also suspect they step motor 1, then turn it off when they do motor 2. Most steppers are 100% on. However with 2 motors, motor 1 might only be on for around 50% of the time. The result is less heat in the motor driver, and less heat in the motor coils. I suspect that could be done like that as a method of micro-stepping with the slow transistors they had back in the late 90's.
Any how I suggest trying one driver, and see what happens. Also probably don't do it for very long, as it will likely get hot.
I think a long term solution is less easy than you might prefer. Perhaps you can do it with 2 drivers, with enable lines connected to the STM32. Same pulse and direction, but you add the enable lines to half step it.
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
The text on this picture mentions "two controllers" and "simultaneously". Also with the whole redundancy approach it has to be something really simple without inter-process synchronization.
I will start by trying one stepper with two sin wires connected together and two cos wires connected together and go from there.
I will start by trying one stepper with two sin wires connected together and two cos wires connected together and go from there.
- Attachments
-
- v12_etb.png (113.95 KiB) Viewed 40069 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
-
- running engine in first post
- Posts: 1495
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: electronic throttle body control ETB
I bet you can wire both steppers in parallel, and run them as a single stepper with double the torque, assuming the phases of each stepper are aligned. That loses you the redundancy of dual steppers, but saves the complexity for testing.
edit: looked closer at the diagram and re-read kb1gtt, it's not two steppers, it's a doubly wound single stepper. So it'll probably work if you use one set of windings (ie two pairs of wires), and ignore the other.
edit: looked closer at the diagram and re-read kb1gtt, it's not two steppers, it's a doubly wound single stepper. So it'll probably work if you use one set of windings (ie two pairs of wires), and ignore the other.
Re: electronic throttle body control ETB
If you ignore the other wires, I suggest connecting them together. Keep in mind there are magnetic fields, and these coils with out termination can potentially generate voltages. Those voltage could potentially exceed insulation, and cause damage.
Welcome to the friendlier side of internet crazy
Re: electronic throttle body control ETB
But from my experience with steppers, if you shorten the coil, it makes it harder to move the shaft, am I wrong?
Re: electronic throttle body control ETB
Its a break feature which means if you move fast it absorbs energy. I doubt he'll move it fast enough to care. My bigger concern is for him to set the amps of the stepper driver. That's a thermal issue, and I don't know how many amps he should be setting it to. It would be helpful if he had an operational system which he could measure.
Welcome to the friendlier side of internet crazy
Re: electronic throttle body control ETB
For E-Throttle I suggest you to develop for the most widely used system.
In 2001 Bosch started using MC33186 in all ecu's.
From 2005 - They have used TLE7209-2R.
It's basically the same, even pin-compatible.
The system uses two Pedal-sensors and two Throttle-motor position-sensors.
I see the same pedal etc. are used in lots of cars.
In 2001 Bosch started using MC33186 in all ecu's.
From 2005 - They have used TLE7209-2R.
It's basically the same, even pin-compatible.
The system uses two Pedal-sensors and two Throttle-motor position-sensors.
I see the same pedal etc. are used in lots of cars.
Re: electronic throttle body control ETB
For the pedal position one of the signals are
0.4 - 2v
The other signal:
0.7 - 4.1
The Throttle position sensor:
0,7 - 4.3
The second:
4.3 - 0.7
0.4 - 2v
The other signal:
0.7 - 4.1
The Throttle position sensor:
0,7 - 4.3
The second:
4.3 - 0.7
Re: electronic throttle body control ETB
The PierBurg Throttle-body are basically the same for all cars as well.
The same parts in different shapes:
https://www.google.com/search?q=PIERBURG+Throttle+Body&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiit7rTj7ngAhWqxKYKHblhDvIQ_AUIDigB&biw=800&bih=354
The same parts in different shapes:
https://www.google.com/search?q=PIERBURG+Throttle+Body&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiit7rTj7ngAhWqxKYKHblhDvIQ_AUIDigB&biw=800&bih=354
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
Tl;DR: large-scale movement is great, fine movements are not so great.
Status update:
0) Just a reminder that my test ETB is slightly open by default. To be more specific, default position is 4% open. With some electricity it can go to 0% which would reduce idle air flow. Our end goal is to
have some precise control in this 0-4-8% range assuming this is how we will control idle air without any additional valves.
1) now with direction control pins. If command duty cycle below 0, flip direction pins and use abs(command duty) as duty cycle. Fun fact is that my bench test VNH2SP30 chip seems to be 5v logic, I have no clue how did I get any results previously while I was driving it directly from stm32. Now using Frankenso 5v outputs to drive VNH2SP30.
2) now with feedforward curve. Some default curve attached based on mck1117's default curve. I have no idea how to make a better curve more suitable for my ETB.
3) now with explicit iTerm limits in addition to overall PID limits since I saw iTerm running away.
I have my rusEfi console command the same test sequence of throttle positions and accumulate standard deviation of control error. This would theoretically allow me to objectively compare different settings. Great news is that I even get somewhat repetitive results!
This picture shows two runs on the test sequence.
Above picture with current default values.
Following random different settings seem to be better for fine movements closer to idle position, did I get lucky here?
More on test sequence:
See also https://github.com/rusefi/rusefi/issues/494
Raw logs attached
Status update:
0) Just a reminder that my test ETB is slightly open by default. To be more specific, default position is 4% open. With some electricity it can go to 0% which would reduce idle air flow. Our end goal is to
have some precise control in this 0-4-8% range assuming this is how we will control idle air without any additional valves.
1) now with direction control pins. If command duty cycle below 0, flip direction pins and use abs(command duty) as duty cycle. Fun fact is that my bench test VNH2SP30 chip seems to be 5v logic, I have no clue how did I get any results previously while I was driving it directly from stm32. Now using Frankenso 5v outputs to drive VNH2SP30.
2) now with feedforward curve. Some default curve attached based on mck1117's default curve. I have no idea how to make a better curve more suitable for my ETB.
3) now with explicit iTerm limits in addition to overall PID limits since I saw iTerm running away.
I have my rusEfi console command the same test sequence of throttle positions and accumulate standard deviation of control error. This would theoretically allow me to objectively compare different settings. Great news is that I even get somewhat repetitive results!
This picture shows two runs on the test sequence.
Above picture with current default values.
Following random different settings seem to be better for fine movements closer to idle position, did I get lucky here?
More on test sequence:
2019-03-02 15_26: EngineState: confirmation_set mock_pedal_position 4.0:27
2019-03-02 15_26: EngineState: confirmation_set mock_pedal_position 4.0:27
2019-03-02 15_26: EngineState: confirmation_set mock_pedal_position 6.0:27
2019-03-02 15_26: EngineState: confirmation_set mock_pedal_position 8.0:27
2019-03-02 15_26: EngineState: confirmation_set mock_pedal_position 6.0:27
2019-03-02 15_26: EngineState: confirmation_set mock_pedal_position 4.0:27
2019-03-02 15_27: EngineState: confirmation_set mock_pedal_position 2.0:27
2019-03-02 15_27: EngineState: confirmation_set mock_pedal_position 0.0:27
2019-03-02 15_27: EngineState: confirmation_set mock_pedal_position 10.0:28
2019-03-02 15_27: EngineState: confirmation_set mock_pedal_position 6.0:27
2019-03-02 15_27: EngineState: confirmation_set mock_pedal_position 30.0:28
2019-03-02 15_27: EngineState: confirmation_set mock_pedal_position 50.0:28
2019-03-02 15_27: EngineState: confirmation_set mock_pedal_position 70.0:28
2019-03-02 15_27: EngineState: confirmation_set mock_pedal_position 100.0:29
2019-03-02 15_28: EngineState: confirmation_set mock_pedal_position 50.0:28
2019-03-02 15_28: EngineState: confirmation_set mock_pedal_position 70.0:28
2019-03-02 15_28: EngineState: confirmation_set mock_pedal_position 4.0:27
2019-03-02 15_28: EtbTestSequence: ETB test sequence done!
2019-03-02 15_28: EngineState: confirmation_set mock_pedal_position 0.0:27
2019-03-02 15_28: EngineState: confirmation_set mock_pedal_position 4.0:27
2019-03-02 15_28: EngineState: confirmation_set mock_pedal_position 4.0:27
2019-03-02 15_29: EngineState: confirmation_set mock_pedal_position 6.0:27
2019-03-02 15_29: EngineState: confirmation_set mock_pedal_position 8.0:27
2019-03-02 15_29: EngineState: confirmation_set mock_pedal_position 6.0:27
2019-03-02 15_29: EngineState: confirmation_set mock_pedal_position 4.0:27
2019-03-02 15_29: EngineState: confirmation_set mock_pedal_position 2.0:27
2019-03-02 15_29: EngineState: confirmation_set mock_pedal_position 0.0:27
2019-03-02 15_29: EngineState: confirmation_set mock_pedal_position 10.0:28
2019-03-02 15_29: EngineState: confirmation_set mock_pedal_position 6.0:27
2019-03-02 15_29: EngineState: confirmation_set mock_pedal_position 30.0:28
2019-03-02 15_30: EngineState: confirmation_set mock_pedal_position 50.0:28
2019-03-02 15_30: EngineState: confirmation_set mock_pedal_position 70.0:28
2019-03-02 15_30: EngineState: confirmation_set mock_pedal_position 100.0:29
2019-03-02 15_30: EngineState: confirmation_set mock_pedal_position 50.0:28
2019-03-02 15_30: EngineState: confirmation_set mock_pedal_position 70.0:28
2019-03-02 15_30: EngineState: confirmation_set mock_pedal_position 4.0:27
2019-03-02 15_31: EtbTestSequence: ETB test sequence done!
See also https://github.com/rusefi/rusefi/issues/494
Raw logs attached
- Attachments
-
- console_logs.7z
- (311.27 KiB) Downloaded 728 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
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
Since I have very little clue how to tune this growing space of parameters I am now trying random parameters on the same test sequence. Not great so far. Yellow line result at the end of the test is the thing I want to be as small as possible.
- Attachments
-
- random.png (100.4 KiB) Viewed 39925 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
Re: electronic throttle body control ETB
Can you create a list of output values over time, such that you can simply play back this list of outputs and see how fast you can possibly get. Basically you look at areas and simply decide to increase or decrease the output and see what you get. Once you know what your output should be under certain conditions, then you can try to make your algorithm generate the same outputs.
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
I have no idea what you are suggesting Is this assuming that for each throttle position, there is one specific DC duty cycle?kb1gtt wrote: ↑Sat Mar 02, 2019 10:31 pmCan you create a list of output values over time, such that you can simply play back this list of outputs and see how fast you can possibly get. Basically you look at areas and simply decide to increase or decrease the output and see what you get. Once you know what your output should be under certain conditions, then you can try to make your algorithm generate the same outputs.
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
Re: electronic throttle body control ETB
Lets say you have an 1 by 1000 table of numbers. This table number will be copied to your PWM output. Lets say that each mS you copy one of these numbers to the PWM output. You can then adjust each the output once for every mS. You then play these output values and see how well it was at getting to your desired position. If it has not reached your desired position, you can then adjust the values, play them again, and see if they have gotten any better.
Lets say you start with the ETB at 4%, and your PWM duty starts at 0% and your first desired position is 50%. In your table might have 100, 75, 50, 50, 50, etc.
Then you start the program. It starts at 0% duty, but immediately the duty goes to 100%, then 1mS later it goes to 75%, then at 3mS it goes to 50% and stays there. You then look at your log file, and you see if you are getting to your desired target quickly. You can then adjust the number and play it again and see how it reacts. Once you have adjusted these numbers until you are happy with how fast it reacts, you know what numbers your control algo should be generating. At this point you can adjust your algo until it makes these numbers.
I think that by doing this, you'll get a better understanding or gut feel for the effects of hysteresis and signal delays.
Lets say you start with the ETB at 4%, and your PWM duty starts at 0% and your first desired position is 50%. In your table might have 100, 75, 50, 50, 50, etc.
Then you start the program. It starts at 0% duty, but immediately the duty goes to 100%, then 1mS later it goes to 75%, then at 3mS it goes to 50% and stays there. You then look at your log file, and you see if you are getting to your desired target quickly. You can then adjust the number and play it again and see how it reacts. Once you have adjusted these numbers until you are happy with how fast it reacts, you know what numbers your control algo should be generating. At this point you can adjust your algo until it makes these numbers.
I think that by doing this, you'll get a better understanding or gut feel for the effects of hysteresis and signal delays.
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
For now I have implemented a Monte Carlo (if that's the right term here?) - my software is simply trying different random parameters and I programmatically pick best set.
First successful run, sorted by last column 'result' which is the metric of control quality for given test scenario:
First successful run, sorted by last column 'result' which is the metric of control quality for given test scenario:
Code: Select all
Sat Mar 02 18 50 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 32 pFactor 3.02 iFactor 0.26 dFactor 0.19 result 61.75430199
Sat Mar 02 17 51 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 22 pFactor 3.35 iFactor 0.19 dFactor 0.13 result 63.30895293
Sat Mar 02 17 50 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 72 pFactor 2 iFactor 0.26 dFactor 0.19 result 64.00471867
Sat Mar 02 19 8 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 42 pFactor 2.6 iFactor 0.23 dFactor 0.16 result 65.80440286
Sat Mar 02 19 9 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 76 pFactor 3.84 iFactor 0.26 dFactor 0.14 result 66.73304504
Sat Mar 02 18 41 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 0 pFactor 3.93 iFactor 0.1 dFactor 0.12 result 66.93453638
Sat Mar 02 18 15 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 60 pFactor 3.99 iFactor 0.15 dFactor 0.07 result 68.01089967
Sat Mar 02 17 56 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 84 pFactor 1.13 iFactor 0.26 dFactor 0.29 result 68.42649213
Sat Mar 02 18 12 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 99 pFactor 2.55 iFactor 0.28 dFactor 0.21 result 69.32302424
Sat Mar 02 19 2 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 17 pFactor 3.33 iFactor 0.26 dFactor 0.08 result 70.12480014
Sat Mar 02 18 44 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 79 pFactor 3.96 iFactor 0.26 dFactor 0.25 result 71.2091067
Sat Mar 02 19 56 22 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 90 pFactor 3.52 iFactor 0.18 dFactor 0.06 result 71.7108843
Sat Mar 02 18 27 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 70 pFactor 1.78 iFactor 0.17 dFactor 0.04 result 72.64242933
Sat Mar 02 18 47 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 20 pFactor 3.6 iFactor 0.19 dFactor 0.09 result 73.06019117
Sat Mar 02 19 20 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 2 pFactor 3.41 iFactor 0.17 dFactor 0.29 result 73.11698062
Sat Mar 02 17 53 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 34 pFactor 3.91 iFactor 0.15 dFactor 0.15 result 74.71511228
Sat Mar 02 20 0 52 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 53 pFactor 2.82 iFactor 0.13 dFactor 0.05 result 74.92574877
Sat Mar 02 19 42 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 83 pFactor 2.75 iFactor 0.2 dFactor 0.26 result 76.88702074
Sat Mar 02 20 14 22 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 92 pFactor 3.55 iFactor 0.14 dFactor 0.08 result 76.97680382
Sat Mar 02 18 26 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 4 pFactor 3.25 iFactor 0.08 dFactor 0.22 result 77.28637418
Sat Mar 02 20 11 22 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 38 pFactor 3.09 iFactor 0.16 dFactor 0.11 result 77.86908669
Sat Mar 02 19 51 52 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 4 pFactor 2.11 iFactor 0.18 dFactor 0.05 result 78.09483792
Sat Mar 02 19 30 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 81 pFactor 2.51 iFactor 0.12 dFactor 0.17 result 79.02709928
Sat Mar 02 19 45 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 13 pFactor 2.84 iFactor 0.15 dFactor 0.29 result 79.25462865
Sat Mar 02 19 32 21 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 15 pFactor 2.61 iFactor 0.28 dFactor 0.29 result 79.27676282
Sat Mar 02 19 50 22 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 4 pFactor 3.58 iFactor 0.07 dFactor 0.09 result 80.00909269
Sat Mar 02 17 48 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 14 pFactor 3.08 iFactor 0.25 dFactor 0.06 result 80.36636733
Sat Mar 02 19 29 21 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 83 pFactor 3.29 iFactor 0.26 dFactor 0.29 result 80.71865992
Sat Mar 02 18 56 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 72 pFactor 2.83 iFactor 0.26 dFactor 0.21 result 80.9093029
Sat Mar 02 18 48 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 15 pFactor 1.7 iFactor 0.21 dFactor 0.12 result 81.54213336
Sat Mar 02 19 27 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 85 pFactor 2.13 iFactor 0.27 dFactor 0.14 result 82.13582556
Sat Mar 02 18 33 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 33 pFactor 2.09 iFactor 0.24 dFactor 0.05 result 82.14328771
Sat Mar 02 19 44 21 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 22 pFactor 3.39 iFactor 0.13 dFactor 0 result 82.38224158
Sat Mar 02 17 45 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 26 pFactor 1.56 iFactor 0.15 dFactor 0.16 result 82.58208825
Sat Mar 02 19 41 21 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 81 pFactor 2.73 iFactor 0.22 dFactor 0.19 result 82.61504193
Sat Mar 02 20 5 22 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 95 pFactor 1.23 iFactor 0.28 dFactor 0.17 result 82.8731455
Sat Mar 02 18 51 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 96 pFactor 2.67 iFactor 0.21 dFactor 0.05 result 83.59444093
Sat Mar 02 20 6 52 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 75 pFactor 1.9 iFactor 0.25 dFactor 0.23 result 83.6595167
Sat Mar 02 17 57 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 17 pFactor 2.22 iFactor 0.09 dFactor 0.16 result 83.66532006
Sat Mar 02 18 11 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 68 pFactor 2.23 iFactor 0.29 dFactor 0.16 result 84.07996545
Sat Mar 02 18 8 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 38 pFactor 3.29 iFactor 0.15 dFactor 0.29 result 84.4232816
Sat Mar 02 19 57 52 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 52 pFactor 3.2 iFactor 0.21 dFactor 0.24 result 85.50245353
Sat Mar 02 19 48 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 8 pFactor 3.37 iFactor 0.05 dFactor 0.14 result 86.98500334
Sat Mar 02 19 18 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 44 pFactor 1.19 iFactor 0.1 dFactor 0.2 result 87.47912462
Sat Mar 02 18 54 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 57 pFactor 1.12 iFactor 0.09 dFactor 0.24 result 87.62219576
Sat Mar 02 19 38 21 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 93 pFactor 1.06 iFactor 0.28 dFactor 0.02 result 88.126511
Sat Mar 02 18 36 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 52 pFactor 3.6 iFactor 0.14 dFactor 0.21 result 89.32130212
Sat Mar 02 19 15 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 11 pFactor 2.53 iFactor 0.06 dFactor 0.11 result 89.63951632
Sat Mar 02 18 18 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 42 pFactor 3.24 iFactor 0.14 dFactor 0.04 result 91.11612474
Sat Mar 02 19 36 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 37 pFactor 1.79 iFactor 0.11 dFactor 0.22 result 91.17151809
Sat Mar 02 17 59 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 66 pFactor 2.6 iFactor 0.24 dFactor 0.26 result 91.71580264
Sat Mar 02 18 38 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 2 pFactor 3.07 iFactor 0.2 dFactor 0.02 result 91.7713249
Sat Mar 02 18 9 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 41 pFactor 3.7 iFactor 0.11 dFactor 0.02 result 91.81991106
Sat Mar 02 18 32 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 76 pFactor 1.2 iFactor 0.14 dFactor 0.28 result 92.02527994
Sat Mar 02 19 11 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 81 pFactor 1.41 iFactor 0.09 dFactor 0.07 result 92.46333918
Sat Mar 02 19 14 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 53 pFactor 2.02 iFactor 0.25 dFactor 0.29 result 92.96845508
Sat Mar 02 19 53 22 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 88 pFactor 1.87 iFactor 0.16 dFactor 0.15 result 93.11964916
Sat Mar 02 19 0 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 73 pFactor 2.83 iFactor 0.19 dFactor 0.18 result 93.20671923
Sat Mar 02 18 17 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 34 pFactor 2.9 iFactor 0.06 dFactor 0.26 result 93.48675189
Sat Mar 02 19 3 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 18 pFactor 1.76 iFactor 0.13 dFactor 0.15 result 93.76070124
Sat Mar 02 18 39 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 27 pFactor 1.61 iFactor 0.17 dFactor 0.17 result 94.01090733
Sat Mar 02 20 3 52 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 85 pFactor 2.86 iFactor 0.28 dFactor 0.25 result 94.45967849
Sat Mar 02 19 35 21 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 41 pFactor 3.34 iFactor 0.05 dFactor 0.23 result 94.51562621
Sat Mar 02 18 6 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 7 pFactor 1.67 iFactor 0.28 dFactor 0.21 result 94.67262593
Sat Mar 02 19 17 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 18 pFactor 3.15 iFactor 0.16 dFactor 0.01 result 94.95547943
Sat Mar 02 18 23 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 52 pFactor 1.06 iFactor 0.22 dFactor 0.05 result 95.15842649
Sat Mar 02 19 6 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 4 pFactor 3.51 iFactor 0.06 dFactor 0.02 result 96.3347408
Sat Mar 02 18 30 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 10 pFactor 1.26 iFactor 0.15 dFactor 0.15 result 96.85889892
Sat Mar 02 18 0 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 45 pFactor 2.4 iFactor 0.23 dFactor 0.08 result 96.91509279
Sat Mar 02 19 5 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 37 pFactor 1.83 iFactor 0.16 dFactor 0.1 result 97.18067982
Sat Mar 02 19 23 21 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 50 pFactor 1.56 iFactor 0.13 dFactor 0.24 result 97.28501268
Sat Mar 02 18 35 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 6 pFactor 1.41 iFactor 0.29 dFactor 0.25 result 97.43084849
Sat Mar 02 18 21 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 40 pFactor 1.95 iFactor 0.05 dFactor 0.15 result 97.6873371
Sat Mar 02 19 21 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 93 pFactor 3.56 iFactor 0.06 dFactor 0.18 result 97.8430605
Sat Mar 02 20 8 22 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 68 pFactor 2.61 iFactor 0.23 dFactor 0.19 result 97.84446588
Sat Mar 02 18 20 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 47 pFactor 2.27 iFactor 0.05 dFactor 0.16 result 98.68799975
Sat Mar 02 18 14 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 62 pFactor 1.16 iFactor 0.26 dFactor 0.21 result 98.89687351
Sat Mar 02 19 59 22 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 44 pFactor 1.59 iFactor 0.19 dFactor 0.26 result 99.75972145
Sat Mar 02 18 2 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 31 pFactor 1.55 iFactor 0.27 dFactor 0.06 result 102.4570084
Sat Mar 02 18 57 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 73 pFactor 2.38 iFactor 0.05 dFactor 0.04 result 103.3895305
Sat Mar 02 18 5 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 48 pFactor 1.48 iFactor 0.17 dFactor 0.01 result 104.5244684
Sat Mar 02 19 26 21 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 81 pFactor 2.4 iFactor 0.29 dFactor 0.06 result 104.9428772
Sat Mar 02 20 12 52 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 5 pFactor 1.61 iFactor 0.28 dFactor 0.19 result 107.0159811
Sat Mar 02 17 47 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 75 pFactor 1.77 iFactor 0.05 dFactor 0.06 result 108.5267687
Sat Mar 02 18 3 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 55 pFactor 1.11 iFactor 0.18 dFactor 0.22 result 108.7761223
Sat Mar 02 18 24 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 80 pFactor 1.64 iFactor 0.14 dFactor 0.15 result 114.2846976
Sat Mar 02 19 12 50 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 66 pFactor 3.62 iFactor 0.04 dFactor 0.16 result 114.7237401
Sat Mar 02 17 54 48 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 89 pFactor 1.53 iFactor 0.04 dFactor 0.07 result 122.6711496
Sat Mar 02 18 29 19 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 29 pFactor 1.59 iFactor 0.19 dFactor 0.03 result 126.5477698
Sat Mar 02 18 42 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 83 pFactor 3.97 iFactor 0.04 dFactor 0.04 result 129.5190879
Sat Mar 02 19 54 52 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 83 pFactor 1.12 iFactor 0.04 dFactor 0.2 result 129.8413629
Sat Mar 02 20 9 52 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 1 pFactor 2.58 iFactor 0.02 dFactor 0.14 result 136.3775182
Sat Mar 02 19 39 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 58 pFactor 1.96 iFactor 0.03 dFactor 0.05 result 138.9593131
Sat Mar 02 18 53 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 52 pFactor 1.41 iFactor 0.03 dFactor 0.09 result 139.6049513
Sat Mar 02 20 2 22 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 70 pFactor 1.9 iFactor 0.03 dFactor 0.13 result 146.1518518
Sat Mar 02 18 45 49 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 80 pFactor 1.01 iFactor 0.29 dFactor 0.08 result 153.3320802
Sat Mar 02 19 47 21 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 31 pFactor 2.05 iFactor 0.02 dFactor 0.12 result 154.3836483
Sat Mar 02 17 44 18 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 19 pFactor 3.61 iFactor 0.01 dFactor 0.13 result 164.1268476
Sat Mar 02 19 33 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 80 pFactor 1.58 iFactor 0.02 dFactor 0.26 result 212.5413146
Sat Mar 02 18 59 20 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 63 pFactor 3.87 iFactor 0.01 dFactor 0.2 result 225.4833084
Sat Mar 02 19 24 51 EST 2019<EOT> postMessage EtbMonteCarloSequence mcstats offset 74 pFactor 1.55 iFactor 0 dFactor 0.09 result 515.2170929
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
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
Results above seem to show that larger iFactor values are winning which means that for next iteration I should allow a wider iFactor range. Lowest iFactor sets are performing worst at least on this scenario.
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
Re: electronic throttle body control ETB
doesn't the airflow passing through the throttle body affect the force required to move the throtle?
Re: electronic throttle body control ETB
With the I factor getting larger, you increase the chances of integral windup issues. At minimum you should have limits on how much your integral term can effect the final result. If in your testing you discover your Integral term is typically 5% of your output, you should have a limit set to limit you to say 6%.
It is also common to have a band around your target, such that the integral term is not calculated unless you are with in something like 10% of your target. If you are father away than 10% from your target, then your integral term is 0. This also minimizes the effects of integral wind up.
Also with the I factor getting larger, keep an eye out on your phase delay. You might be getting to your target nicely, but it also might happen like 1 second after the command.
It is also common to have a band around your target, such that the integral term is not calculated unless you are with in something like 10% of your target. If you are father away than 10% from your target, then your integral term is 0. This also minimizes the effects of integral wind up.
Also with the I factor getting larger, keep an eye out on your phase delay. You might be getting to your target nicely, but it also might happen like 1 second after the command.
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
Just as a baseline we have OEM ETB on a real vehicle
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
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
Why did I suddenly stopped posting amazing Monte Carlo results? Because I've started to have functional issues.
Why did I suddenly started having functional issues? It's unclear, but the fact that I can no longer move the disconnected throttle body by hand might be hinting at the fact that I have fried it
@ I believe you've just swapped same ETB on your vehicle? Please do not throw away the old part...
Why did I suddenly started having functional issues? It's unclear, but the fact that I can no longer move the disconnected throttle body by hand might be hinting at the fact that I have fried it
@ I believe you've just swapped same ETB on your vehicle? Please do not throw away the old part...
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
Re: electronic throttle body control ETB
but that's a good reason to take it apart, have a look at it guts?
Re: electronic throttle body control ETB
A likely source is caused by small resistance in your connections. If you have even around 0.1 ohms in your connections, it can generate in excess of 300V internal to the motor. This high internal voltage is typically what causes motors to burn up. If you know your motors inductance, you probably know the capacitance of your power supply, you could calculate the ball park resonant frequency.
https://www.allaboutcircuits.com/tools/tank-circuit-resonance-calculator/
https://www.allaboutcircuits.com/tools/tank-circuit-resonance-calculator/
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
I have stripped wires screwed into 5mm terminals. What actions are necessary to change the outcome in your opinion?
Actually here's a video of what I am playing with right now.
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
Re: electronic throttle body control ETB
It is hard to see, but I think you have your ETB wires directly screwed into the PCB. That is likely good enough, but solder would be better. I also think I see some fat-ish wires going off to the right of the screen. I suspect that is your power supply. This likely has large capacitors in it, which are connected to a fairly large-ish inductor. If you could use a power supply with a low front end capacitance that would likely help. Hmmm, how to find a low capacitance power supply.
What amps does the ETB consume normally? Can you put a multi meter in series with your power supply and tell me what amps it is consuming?
What amps does the ETB consume normally? Can you put a multi meter in series with your power supply and tell me what amps it is consuming?
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14374
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: electronic throttle body control ETB
New test script contains both small and large movements. Attached is the picture of the best settings out of 250 attempts. Anyone to do any analysis on the full results pretty please? I am blind to data
Second ETB has lasted 10 hours and seized at 4am this morning Just ordered a couple of small thermistors to glue to the next ETB.
Code: Select all
Mon Mar 04 00 37 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 29367.358 mcstats offset 80 pFactor 1.07 iFactor 0.18 dFactor 0.24 result 151.4070387
Sun Mar 03 17 19 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 3066.084 mcstats offset 12 pFactor 1.05 iFactor 0.13 dFactor 0.21 result 160.6204592
Sun Mar 03 23 10 22 EST 2019<EOT> postMessage EtbMonteCarloSequence 24139.242 mcstats offset 68 pFactor 1.61 iFactor 0.16 dFactor 0.28 result 167.0229363
Sun Mar 03 18 31 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 7387.177 mcstats offset 38 pFactor 1.82 iFactor 0.05 dFactor 0.12 result 167.8733752
Mon Mar 04 00 7 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 27566.75 mcstats offset 53 pFactor 1.05 iFactor 0.19 dFactor 0.27 result 167.888015
Sun Mar 03 23 28 25 EST 2019<EOT> postMessage EtbMonteCarloSequence 25221.879 mcstats offset 61 pFactor 1.36 iFactor 0.17 dFactor 0.06 result 169.9110653
Sun Mar 03 16 34 08 EST 2019<EOT> postMessage EtbMonteCarloSequence 365.315 mcstats offset 44 pFactor 1.39 iFactor 0.1 dFactor 0.15 result 173.4172781
Mon Mar 04 02 31 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 36210.051 mcstats offset 32 pFactor 1.2 iFactor 0.04 dFactor 0.29 result 173.8724299
Mon Mar 04 03 16 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 38911.036 mcstats offset 76 pFactor 1.07 iFactor 0.09 dFactor 0.24 result 176.4551811
Mon Mar 04 03 43 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 40531.64 mcstats offset 37 pFactor 1.13 iFactor 0.02 dFactor 0.19 result 176.5036938
Sun Mar 03 17 7 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 2345.903 mcstats offset 84 pFactor 1.03 iFactor 0.15 dFactor 0.2 result 178.7370302
Mon Mar 04 03 10 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 38550.867 mcstats offset 29 pFactor 1.08 iFactor 0.05 dFactor 0.12 result 179.2610675
Sun Mar 03 19 55 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 12428.436 mcstats offset 31 pFactor 1.93 iFactor 0.12 dFactor 0.1 result 184.4757887
Sun Mar 03 23 52 29 EST 2019<EOT> postMessage EtbMonteCarloSequence 26665.61 mcstats offset 59 pFactor 1.1 iFactor 0.05 dFactor 0.21 result 186.2242139
Mon Mar 04 00 31 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 29007.241 mcstats offset 7 pFactor 1.61 iFactor 0.13 dFactor 0.2 result 198.3568048
Mon Mar 04 01 31 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 32608.612 mcstats offset 20 pFactor 1.07 iFactor 0.02 dFactor 0.05 result 198.3813464
Sun Mar 03 19 40 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 11528.212 mcstats offset 0 pFactor 1.39 iFactor 0.03 dFactor 0.18 result 201.6290868
Mon Mar 04 03 52 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 41071.78 mcstats offset 49 pFactor 1.91 iFactor 0.19 dFactor 0.24 result 203.5248564
Mon Mar 04 01 43 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 33328.996 mcstats offset 0 pFactor 1.84 iFactor 0.02 dFactor 0.24 result 209.6745594
Mon Mar 04 02 58 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 37830.635 mcstats offset 42 pFactor 1.25 iFactor 0.07 dFactor 0.22 result 220.0704742
Mon Mar 04 02 43 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 36930.3 mcstats offset 98 pFactor 1.15 iFactor 0.21 dFactor 0.23 result 230.9123796
Sun Mar 03 18 58 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 9007.566 mcstats offset 28 pFactor 1.21 iFactor 0.07 dFactor 0.12 result 233.4680353
Sun Mar 03 18 37 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 7747.261 mcstats offset 92 pFactor 1.11 iFactor 0.16 dFactor 0.21 result 235.114762
Sun Mar 03 18 28 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 7207.136 mcstats offset 44 pFactor 1.91 iFactor 0.14 dFactor 0.16 result 236.5074579
Sun Mar 03 19 7 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 9547.739 mcstats offset 53 pFactor 1.25 iFactor 0.06 dFactor 0.17 result 240.5716512
Sun Mar 03 23 16 23 EST 2019<EOT> postMessage EtbMonteCarloSequence 24499.721 mcstats offset 32 pFactor 1 iFactor 0.11 dFactor 0.08 result 244.0486027
Mon Mar 04 00 28 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 28827.131 mcstats offset 31 pFactor 1.04 iFactor 0.28 dFactor 0.29 result 251.4492467
Sun Mar 03 23 22 24 EST 2019<EOT> postMessage EtbMonteCarloSequence 24860.832 mcstats offset 71 pFactor 1.13 iFactor 0.19 dFactor 0.22 result 254.8550219
Mon Mar 04 01 16 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 31708.322 mcstats offset 24 pFactor 1.22 iFactor 0.1 dFactor 0.18 result 257.4230483
Sun Mar 03 23 37 26 EST 2019<EOT> postMessage EtbMonteCarloSequence 25763.355 mcstats offset 64 pFactor 1.36 iFactor 0.19 dFactor 0.05 result 273.87937
Sun Mar 03 22 40 16 EST 2019<EOT> postMessage EtbMonteCarloSequence 22333.219 mcstats offset 92 pFactor 1.22 iFactor 0.22 dFactor 0.21 result 282.9368249
Sun Mar 03 21 22 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 17649.632 mcstats offset 43 pFactor 1.27 iFactor 0.06 dFactor 0.08 result 287.9169548
Mon Mar 04 04 1 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 41611.925 mcstats offset 66 pFactor 1.59 iFactor 0.01 dFactor 0.27 result 288.4843646
Sun Mar 03 23 55 29 EST 2019<EOT> postMessage EtbMonteCarloSequence 26846.465 mcstats offset 98 pFactor 1.23 iFactor 0.1 dFactor 0.21 result 300.5057393
Sun Mar 03 20 37 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 14949.009 mcstats offset 65 pFactor 1.65 iFactor 0.03 dFactor 0.27 result 318.768954
Sun Mar 03 17 16 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 2886.039 mcstats offset 29 pFactor 1.09 iFactor 0.17 dFactor 0.14 result 319.8133594
Sun Mar 03 18 10 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 6126.861 mcstats offset 49 pFactor 1.46 iFactor 0.06 dFactor 0.27 result 332.3743627
Sun Mar 03 21 13 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 17109.498 mcstats offset 40 pFactor 1.91 iFactor 0.25 dFactor 0.07 result 335.1025225
Mon Mar 04 01 46 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 33509.047 mcstats offset 91 pFactor 2.31 iFactor 0.09 dFactor 0.1 result 335.8812127
Mon Mar 04 02 4 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 34589.408 mcstats offset 62 pFactor 1.31 iFactor 0.26 dFactor 0.02 result 342.737285
Sun Mar 03 22 37 15 EST 2019<EOT> postMessage EtbMonteCarloSequence 22152.231 mcstats offset 97 pFactor 1.5 iFactor 0.04 dFactor 0.07 result 350.8608502
Sun Mar 03 23 46 28 EST 2019<EOT> postMessage EtbMonteCarloSequence 26305.199 mcstats offset 17 pFactor 2.58 iFactor 0.02 dFactor 0.05 result 352.2939463
Mon Mar 04 00 22 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 28467.036 mcstats offset 70 pFactor 1.44 iFactor 0.08 dFactor 0.11 result 353.0634278
Mon Mar 04 00 52 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 30267.669 mcstats offset 65 pFactor 1.68 iFactor 0.26 dFactor 0.1 result 355.6172246
Mon Mar 04 01 19 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 31888.387 mcstats offset 64 pFactor 1.75 iFactor 0.17 dFactor 0.25 result 355.7400283
Sun Mar 03 19 31 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 10988.093 mcstats offset 49 pFactor 1.94 iFactor 0.12 dFactor 0.28 result 356.0719407
Sun Mar 03 22 25 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 21430.576 mcstats offset 56 pFactor 2.22 iFactor 0.09 dFactor 0.29 result 357.345554
Sun Mar 03 20 16 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 13688.743 mcstats offset 26 pFactor 1.4 iFactor 0.05 dFactor 0.09 result 357.3531618
Sun Mar 03 17 37 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 4146.342 mcstats offset 2 pFactor 3.17 iFactor 0.09 dFactor 0.19 result 358.0577468
Sun Mar 03 19 43 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 11708.251 mcstats offset 49 pFactor 2.71 iFactor 0.04 dFactor 0.28 result 358.6503135
Sun Mar 03 16 37 08 EST 2019<EOT> postMessage EtbMonteCarloSequence 545.361 mcstats offset 22 pFactor 3.35 iFactor 0.13 dFactor 0.22 result 360.3906056
Mon Mar 04 02 25 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 35849.886 mcstats offset 95 pFactor 2.36 iFactor 0.03 dFactor 0.23 result 360.6195689
Sun Mar 03 22 16 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 20890.421 mcstats offset 26 pFactor 2.59 iFactor 0.08 dFactor 0.18 result 361.1385208
Sun Mar 03 18 19 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 6667.007 mcstats offset 63 pFactor 1.23 iFactor 0.29 dFactor 0.29 result 362.1321321
Sun Mar 03 21 55 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 19630.129 mcstats offset 83 pFactor 1.48 iFactor 0.25 dFactor 0 result 362.2744551
Sun Mar 03 18 43 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 8107.344 mcstats offset 68 pFactor 2.35 iFactor 0.16 dFactor 0.21 result 362.4153454
Sun Mar 03 19 4 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 9367.692 mcstats offset 8 pFactor 2.73 iFactor 0.14 dFactor 0.17 result 362.5951515
Sun Mar 03 20 52 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 15849.227 mcstats offset 5 pFactor 2.87 iFactor 0.22 dFactor 0.2 result 362.8913025
Mon Mar 04 00 10 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 27746.8 mcstats offset 5 pFactor 1.63 iFactor 0.02 dFactor 0 result 362.9001241
Mon Mar 04 02 22 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 35669.757 mcstats offset 7 pFactor 3.01 iFactor 0.07 dFactor 0.03 result 365.961849
Mon Mar 04 00 16 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 28106.926 mcstats offset 8 pFactor 3.33 iFactor 0.19 dFactor 0.24 result 367.1035949
Sun Mar 03 21 10 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 16929.452 mcstats offset 41 pFactor 1.56 iFactor 0.03 dFactor 0.04 result 367.2094289
Sun Mar 03 21 1 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 16389.337 mcstats offset 82 pFactor 1.98 iFactor 0.23 dFactor 0.08 result 368.8065926
Mon Mar 04 01 55 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 34049.189 mcstats offset 84 pFactor 3.26 iFactor 0.09 dFactor 0.18 result 368.8658673
Mon Mar 04 01 7 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 31168.109 mcstats offset 59 pFactor 3.22 iFactor 0.18 dFactor 0.14 result 369.6916313
Mon Mar 04 00 49 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 30087.622 mcstats offset 88 pFactor 2.84 iFactor 0.13 dFactor 0.07 result 370.1134686
Mon Mar 04 04 4 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 41791.994 mcstats offset 17 pFactor 2.92 iFactor 0.12 dFactor 0.2 result 370.1845306
Sun Mar 03 19 1 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 9187.654 mcstats offset 99 pFactor 2.56 iFactor 0.22 dFactor 0.09 result 370.2316939
Sun Mar 03 18 49 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 8467.44 mcstats offset 57 pFactor 1.76 iFactor 0.03 dFactor 0.16 result 370.4777169
Sun Mar 03 20 55 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 16029.264 mcstats offset 50 pFactor 2.39 iFactor 0.17 dFactor 0.21 result 370.6165863
Sun Mar 03 22 19 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 21070.469 mcstats offset 95 pFactor 2.65 iFactor 0.15 dFactor 0.04 result 370.8169103
Sun Mar 03 18 16 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 6486.964 mcstats offset 43 pFactor 1.53 iFactor 0.27 dFactor 0.29 result 370.9105487
Sun Mar 03 17 43 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 4506.454 mcstats offset 28 pFactor 2.67 iFactor 0.22 dFactor 0.09 result 370.9346577
Mon Mar 04 01 49 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 33689.093 mcstats offset 49 pFactor 3.31 iFactor 0.2 dFactor 0.03 result 371.1870513
Sun Mar 03 18 55 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 8827.523 mcstats offset 69 pFactor 2.21 iFactor 0.15 dFactor 0.19 result 371.9626184
Sun Mar 03 19 10 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 9727.784 mcstats offset 33 pFactor 2.77 iFactor 0.03 dFactor 0.02 result 372.7638416
Sun Mar 03 21 43 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 18909.947 mcstats offset 40 pFactor 2.25 iFactor 0.07 dFactor 0.22 result 373.2839271
Mon Mar 04 03 31 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 39811.413 mcstats offset 23 pFactor 3.5 iFactor 0.25 dFactor 0.11 result 373.424823
Mon Mar 04 03 40 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 40351.601 mcstats offset 22 pFactor 3.89 iFactor 0.21 dFactor 0.17 result 373.5952533
Mon Mar 04 03 49 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 40891.742 mcstats offset 9 pFactor 2.6 iFactor 0.17 dFactor 0.18 result 373.5991433
Mon Mar 04 00 34 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 29187.305 mcstats offset 94 pFactor 2.46 iFactor 0.14 dFactor 0.15 result 374.2246957
Mon Mar 04 03 58 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 41431.864 mcstats offset 45 pFactor 2.95 iFactor 0.12 dFactor 0.19 result 374.2736207
Mon Mar 04 03 19 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 39091.091 mcstats offset 11 pFactor 3.17 iFactor 0.04 dFactor 0.19 result 375.1389077
Sun Mar 03 20 49 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 15669.187 mcstats offset 47 pFactor 3.06 iFactor 0.23 dFactor 0.13 result 375.8078801
Sun Mar 03 20 7 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 13148.603 mcstats offset 3 pFactor 2.42 iFactor 0.29 dFactor 0.2 result 376.568539
Sun Mar 03 16 46 08 EST 2019<EOT> postMessage EtbMonteCarloSequence 1085.515 mcstats offset 22 pFactor 3.56 iFactor 0.22 dFactor 0.14 result 377.0269973
Sun Mar 03 17 34 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 3966.299 mcstats offset 62 pFactor 3.19 iFactor 0.16 dFactor 0.13 result 377.6243736
Sun Mar 03 16 31 08 EST 2019<EOT> postMessage EtbMonteCarloSequence 185.261 mcstats offset 76 pFactor 3.8 iFactor 0.05 dFactor 0.28 result 378.5733133
Sun Mar 03 17 46 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 4686.498 mcstats offset 65 pFactor 3.65 iFactor 0.16 dFactor 0.25 result 378.6485257
Mon Mar 04 02 28 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 36029.974 mcstats offset 43 pFactor 3.95 iFactor 0.28 dFactor 0.15 result 378.7826848
Sun Mar 03 19 34 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 11168.13 mcstats offset 59 pFactor 2.36 iFactor 0.11 dFactor 0.25 result 379.2779159
Sun Mar 03 17 13 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 2705.99 mcstats offset 57 pFactor 3.99 iFactor 0.24 dFactor 0.16 result 379.6832216
Sun Mar 03 17 28 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 3606.212 mcstats offset 28 pFactor 3.45 iFactor 0.17 dFactor 0.08 result 379.9335011
Sun Mar 03 21 19 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 17469.585 mcstats offset 75 pFactor 3.44 iFactor 0.09 dFactor 0.04 result 380.8412718
Sun Mar 03 17 52 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 5046.585 mcstats offset 40 pFactor 3.17 iFactor 0.22 dFactor 0.29 result 381.0692995
Sun Mar 03 18 1 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 5586.716 mcstats offset 79 pFactor 2.83 iFactor 0.13 dFactor 0.02 result 381.3436109
Mon Mar 04 00 19 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 28286.989 mcstats offset 62 pFactor 2.96 iFactor 0.05 dFactor 0.06 result 381.8062341
Mon Mar 04 03 1 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 38010.693 mcstats offset 1 pFactor 3.29 iFactor 0.22 dFactor 0.16 result 382.0196166
Sun Mar 03 17 10 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 2525.948 mcstats offset 62 pFactor 2.57 iFactor 0.14 dFactor 0.28 result 382.1558881
Sun Mar 03 22 1 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 19990.212 mcstats offset 55 pFactor 3.11 iFactor 0.21 dFactor 0.1 result 382.3341637
Mon Mar 04 02 19 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 35489.661 mcstats offset 84 pFactor 2.79 iFactor 0.1 dFactor 0.24 result 382.3732018
Mon Mar 04 00 1 29 EST 2019<EOT> postMessage EtbMonteCarloSequence 27206.6 mcstats offset 81 pFactor 3.32 iFactor 0.11 dFactor 0.19 result 382.8077545
Mon Mar 04 02 13 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 35129.571 mcstats offset 52 pFactor 3.9 iFactor 0.07 dFactor 0.05 result 382.9221644
Sun Mar 03 18 40 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 7927.307 mcstats offset 92 pFactor 3.89 iFactor 0.18 dFactor 0.06 result 383.7012927
Sun Mar 03 18 22 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 6847.046 mcstats offset 41 pFactor 3.47 iFactor 0.2 dFactor 0.16 result 383.9407124
Sun Mar 03 19 52 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 12248.394 mcstats offset 91 pFactor 3.48 iFactor 0.15 dFactor 0.05 result 384.377088
Sun Mar 03 20 28 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 14408.894 mcstats offset 20 pFactor 2.86 iFactor 0.2 dFactor 0.22 result 384.4543551
Sun Mar 03 22 31 14 EST 2019<EOT> postMessage EtbMonteCarloSequence 21790.72 mcstats offset 27 pFactor 2.85 iFactor 0.18 dFactor 0.17 result 384.9245877
Mon Mar 04 02 10 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 34949.534 mcstats offset 46 pFactor 2.74 iFactor 0.23 dFactor 0.28 result 385.0073859
Sun Mar 03 23 19 23 EST 2019<EOT> postMessage EtbMonteCarloSequence 24679.824 mcstats offset 6 pFactor 3.06 iFactor 0.1 dFactor 0.18 result 385.5170143
Sun Mar 03 23 7 21 EST 2019<EOT> postMessage EtbMonteCarloSequence 23958.347 mcstats offset 2 pFactor 3.35 iFactor 0.08 dFactor 0.13 result 386.0406104
Sun Mar 03 19 25 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 10627.995 mcstats offset 96 pFactor 2.99 iFactor 0.27 dFactor 0.09 result 386.2679512
Sun Mar 03 22 52 18 EST 2019<EOT> postMessage EtbMonteCarloSequence 23055.197 mcstats offset 40 pFactor 2.4 iFactor 0.12 dFactor 0.29 result 386.8490782
Sun Mar 03 22 34 14 EST 2019<EOT> postMessage EtbMonteCarloSequence 21970.773 mcstats offset 83 pFactor 2.42 iFactor 0.1 dFactor 0.02 result 387.0040947
Mon Mar 04 03 46 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 40711.677 mcstats offset 79 pFactor 3.64 iFactor 0.19 dFactor 0.05 result 387.1283683
Mon Mar 04 01 28 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 32428.542 mcstats offset 17 pFactor 1.56 iFactor 0.05 dFactor 0 result 387.6575447
Mon Mar 04 01 34 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 32788.691 mcstats offset 23 pFactor 3.18 iFactor 0.04 dFactor 0.08 result 387.6932099
Mon Mar 04 01 22 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 32068.444 mcstats offset 1 pFactor 3.34 iFactor 0.22 dFactor 0.08 result 387.8536454
Sun Mar 03 19 37 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 11348.171 mcstats offset 71 pFactor 1.6 iFactor 0.24 dFactor 0.25 result 388.3248747
Mon Mar 04 02 7 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 34769.48 mcstats offset 65 pFactor 3.02 iFactor 0.05 dFactor 0.19 result 388.5095449
Mon Mar 04 03 22 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 39271.168 mcstats offset 66 pFactor 2.17 iFactor 0.26 dFactor 0.2 result 388.675324
Sun Mar 03 17 49 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 4866.543 mcstats offset 97 pFactor 3.11 iFactor 0.24 dFactor 0.25 result 388.9438147
Sun Mar 03 16 55 08 EST 2019<EOT> postMessage EtbMonteCarloSequence 1625.67 mcstats offset 2 pFactor 3.45 iFactor 0.22 dFactor 0.04 result 388.9598354
Sun Mar 03 16 43 08 EST 2019<EOT> postMessage EtbMonteCarloSequence 905.463 mcstats offset 74 pFactor 3.29 iFactor 0.24 dFactor 0.09 result 388.9704342
Mon Mar 04 00 40 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 29547.437 mcstats offset 59 pFactor 3.15 iFactor 0.12 dFactor 0.09 result 388.9865751
Sun Mar 03 21 28 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 18009.739 mcstats offset 64 pFactor 3.29 iFactor 0.26 dFactor 0.2 result 389.061538
Sun Mar 03 21 31 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 18189.788 mcstats offset 5 pFactor 3.65 iFactor 0.2 dFactor 0.25 result 389.0963925
Sun Mar 03 21 52 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 19450.09 mcstats offset 77 pFactor 2.12 iFactor 0.09 dFactor 0.04 result 389.2858508
Mon Mar 04 01 52 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 33869.139 mcstats offset 72 pFactor 3.98 iFactor 0.26 dFactor 0.05 result 389.353498
Mon Mar 04 01 10 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 31348.173 mcstats offset 49 pFactor 3.66 iFactor 0.18 dFactor 0.27 result 389.3558301
Mon Mar 04 00 58 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 30627.882 mcstats offset 97 pFactor 2.61 iFactor 0.14 dFactor 0.16 result 389.4784692
Mon Mar 04 01 37 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 32968.746 mcstats offset 16 pFactor 3.57 iFactor 0.2 dFactor 0.24 result 389.8189171
Mon Mar 04 01 1 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 30807.95 mcstats offset 9 pFactor 3.98 iFactor 0.15 dFactor 0.09 result 390.2758021
Sun Mar 03 17 22 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 3246.127 mcstats offset 13 pFactor 3.23 iFactor 0.13 dFactor 0.21 result 390.5244169
Mon Mar 04 03 28 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 39631.294 mcstats offset 89 pFactor 1.7 iFactor 0.13 dFactor 0.13 result 391.002802
Sun Mar 03 18 25 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 7027.098 mcstats offset 48 pFactor 2.24 iFactor 0.2 dFactor 0.08 result 391.094474
Sun Mar 03 21 58 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 19810.174 mcstats offset 79 pFactor 3.12 iFactor 0.16 dFactor 0.02 result 391.1625107
Mon Mar 04 03 37 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 40171.511 mcstats offset 40 pFactor 3.96 iFactor 0.17 dFactor 0.21 result 391.2935507
Sun Mar 03 19 16 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 10087.871 mcstats offset 97 pFactor 3.51 iFactor 0.17 dFactor 0.13 result 391.3473331
Mon Mar 04 02 40 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 36750.249 mcstats offset 50 pFactor 2.34 iFactor 0.21 dFactor 0.21 result 391.6647415
Sun Mar 03 21 16 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 17289.542 mcstats offset 70 pFactor 3.42 iFactor 0.16 dFactor 0.29 result 392.1482503
Sun Mar 03 21 49 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 19270.044 mcstats offset 66 pFactor 1.83 iFactor 0.11 dFactor 0.14 result 392.7156535
Sun Mar 03 21 37 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 18549.866 mcstats offset 49 pFactor 2.71 iFactor 0.05 dFactor 0 result 393.2555018
Mon Mar 04 01 13 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 31528.239 mcstats offset 46 pFactor 3.87 iFactor 0.24 dFactor 0.29 result 393.3194117
Mon Mar 04 00 13 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 27926.86 mcstats offset 57 pFactor 2.94 iFactor 0.14 dFactor 0.15 result 393.6487473
Sun Mar 03 22 58 20 EST 2019<EOT> postMessage EtbMonteCarloSequence 23416.719 mcstats offset 46 pFactor 3.02 iFactor 0.08 dFactor 0.19 result 393.7026566
Mon Mar 04 01 4 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 30988.025 mcstats offset 9 pFactor 3.86 iFactor 0.24 dFactor 0.04 result 393.7341359
Sun Mar 03 16 49 08 EST 2019<EOT> postMessage EtbMonteCarloSequence 1265.567 mcstats offset 72 pFactor 2.88 iFactor 0.19 dFactor 0.03 result 394.3443134
Sun Mar 03 22 28 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 21610.661 mcstats offset 41 pFactor 2.9 iFactor 0.01 dFactor 0.2 result 394.4796616
Mon Mar 04 03 55 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 41251.82 mcstats offset 35 pFactor 2.37 iFactor 0.03 dFactor 0.08 result 394.5538098
Sun Mar 03 23 31 25 EST 2019<EOT> postMessage EtbMonteCarloSequence 25402.425 mcstats offset 76 pFactor 3.64 iFactor 0.17 dFactor 0.03 result 394.6116621
Mon Mar 04 03 4 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 38190.738 mcstats offset 16 pFactor 2.96 iFactor 0.17 dFactor 0.03 result 395.1288364
Sun Mar 03 22 43 16 EST 2019<EOT> postMessage EtbMonteCarloSequence 22513.523 mcstats offset 75 pFactor 3.45 iFactor 0.09 dFactor 0.06 result 395.3103047
Sun Mar 03 18 52 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 8647.486 mcstats offset 30 pFactor 2.94 iFactor 0.14 dFactor 0.01 result 395.5194113
Sun Mar 03 23 4 21 EST 2019<EOT> postMessage EtbMonteCarloSequence 23777.775 mcstats offset 77 pFactor 2.29 iFactor 0.29 dFactor 0.29 result 395.7199665
Sun Mar 03 20 1 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 12788.52 mcstats offset 40 pFactor 1.94 iFactor 0.12 dFactor 0.08 result 395.8380018
Sun Mar 03 23 49 28 EST 2019<EOT> postMessage EtbMonteCarloSequence 26485.301 mcstats offset 64 pFactor 2.34 iFactor 0.12 dFactor 0.25 result 395.8409784
Mon Mar 04 01 40 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 33148.922 mcstats offset 23 pFactor 3.34 iFactor 0.29 dFactor 0.1 result 395.9910525
Mon Mar 04 00 46 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 29907.564 mcstats offset 21 pFactor 3.06 iFactor 0.04 dFactor 0.14 result 396.0276141
Sun Mar 03 17 58 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 5406.671 mcstats offset 94 pFactor 1.87 iFactor 0.08 dFactor 0.07 result 396.4048668
Sun Mar 03 22 22 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 21250.511 mcstats offset 89 pFactor 2.01 iFactor 0.26 dFactor 0.27 result 396.5989869
Sun Mar 03 16 52 08 EST 2019<EOT> postMessage EtbMonteCarloSequence 1445.623 mcstats offset 97 pFactor 1.21 iFactor 0.27 dFactor 0.22 result 396.8315365
Mon Mar 04 03 13 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 38730.975 mcstats offset 2 pFactor 3.01 iFactor 0.26 dFactor 0.15 result 397.0171141
Sun Mar 03 20 4 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 12968.564 mcstats offset 96 pFactor 3.56 iFactor 0.1 dFactor 0.02 result 397.0205886
Mon Mar 04 02 1 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 34409.298 mcstats offset 81 pFactor 2.27 iFactor 0.08 dFactor 0.05 result 397.1453369
Sun Mar 03 18 7 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 5946.804 mcstats offset 29 pFactor 3.92 iFactor 0.15 dFactor 0.21 result 397.1764396
Sun Mar 03 19 22 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 10447.957 mcstats offset 45 pFactor 2.87 iFactor 0.24 dFactor 0.01 result 398.821266
Sun Mar 03 23 58 29 EST 2019<EOT> postMessage EtbMonteCarloSequence 27026.543 mcstats offset 42 pFactor 2.22 iFactor 0.26 dFactor 0.02 result 399.0970066
Sun Mar 03 16 58 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 1805.75 mcstats offset 28 pFactor 3.88 iFactor 0.26 dFactor 0.1 result 399.4594054
Sun Mar 03 20 31 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 14588.931 mcstats offset 82 pFactor 3.58 iFactor 0.14 dFactor 0.22 result 399.807518
Sun Mar 03 22 55 19 EST 2019<EOT> postMessage EtbMonteCarloSequence 23235.903 mcstats offset 84 pFactor 3.99 iFactor 0.05 dFactor 0.17 result 399.8171077
Mon Mar 04 00 43 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 29727.489 mcstats offset 1 pFactor 3.8 iFactor 0.04 dFactor 0.25 result 400.1633259
Sun Mar 03 21 25 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 17829.672 mcstats offset 93 pFactor 1.08 iFactor 0.01 dFactor 0 result 400.5137158
Mon Mar 04 01 58 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 34229.246 mcstats offset 81 pFactor 2.63 iFactor 0.27 dFactor 0.01 result 400.7201934
Mon Mar 04 00 4 29 EST 2019<EOT> postMessage EtbMonteCarloSequence 27386.661 mcstats offset 30 pFactor 1.7 iFactor 0.26 dFactor 0.07 result 400.7775408
Sun Mar 03 20 10 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 13328.645 mcstats offset 96 pFactor 2.95 iFactor 0.25 dFactor 0.16 result 401.2244306
Mon Mar 04 02 46 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 37110.379 mcstats offset 12 pFactor 3.52 iFactor 0.19 dFactor 0.07 result 401.7674658
Sun Mar 03 22 4 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 20170.252 mcstats offset 54 pFactor 3.85 iFactor 0.18 dFactor 0.1 result 401.7710058
Sun Mar 03 20 25 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 14228.856 mcstats offset 62 pFactor 3.68 iFactor 0.12 dFactor 0.29 result 402.0873398
Mon Mar 04 04 7 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 41972.047 mcstats offset 83 pFactor 2.33 iFactor 0.13 dFactor 0.1 result 402.4967783
Sun Mar 03 19 13 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 9907.83 mcstats offset 10 pFactor 1.88 iFactor 0.05 dFactor 0.08 result 402.6554934
Sun Mar 03 20 13 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 13508.704 mcstats offset 39 pFactor 2.1 iFactor 0.18 dFactor 0.14 result 404.2833212
Sun Mar 03 21 34 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 18369.825 mcstats offset 40 pFactor 3.83 iFactor 0.17 dFactor 0.24 result 404.5393023
Mon Mar 04 03 25 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 39451.233 mcstats offset 42 pFactor 1.96 iFactor 0.29 dFactor 0.09 result 404.9617259
Sun Mar 03 23 1 20 EST 2019<EOT> postMessage EtbMonteCarloSequence 23597.607 mcstats offset 16 pFactor 2.06 iFactor 0.21 dFactor 0.18 result 405.1043491
Sun Mar 03 19 28 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 10808.048 mcstats offset 34 pFactor 2.09 iFactor 0.27 dFactor 0.02 result 405.9218859
Sun Mar 03 21 40 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 18729.904 mcstats offset 40 pFactor 3.79 iFactor 0.22 dFactor 0.09 result 406.9570137
Sun Mar 03 18 46 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 8287.395 mcstats offset 47 pFactor 1.63 iFactor 0.25 dFactor 0.17 result 407.2952605
Sun Mar 03 17 4 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 2165.857 mcstats offset 98 pFactor 2.93 iFactor 0.19 dFactor 0.24 result 407.6197347
Mon Mar 04 03 7 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 38370.779 mcstats offset 11 pFactor 3.53 iFactor 0.1 dFactor 0.13 result 408.0155947
Sun Mar 03 18 4 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 5766.757 mcstats offset 27 pFactor 1.3 iFactor 0.25 dFactor 0.06 result 408.4723245
Sun Mar 03 22 10 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 20530.342 mcstats offset 29 pFactor 1.13 iFactor 0.22 dFactor 0.02 result 408.478559
Sun Mar 03 17 40 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 4326.384 mcstats offset 42 pFactor 3.62 iFactor 0.19 dFactor 0.07 result 408.8028795
Sun Mar 03 21 7 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 16749.417 mcstats offset 94 pFactor 3.36 iFactor 0.06 dFactor 0.11 result 409.0360668
Sun Mar 03 22 13 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 20710.385 mcstats offset 48 pFactor 1.32 iFactor 0.29 dFactor 0.14 result 409.2333277
Mon Mar 04 02 49 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 37290.423 mcstats offset 0 pFactor 2.93 iFactor 0.21 dFactor 0.04 result 409.2604434
Sun Mar 03 20 43 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 15309.115 mcstats offset 78 pFactor 3.42 iFactor 0.13 dFactor 0.09 result 409.7366501
Sun Mar 03 19 19 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 10267.91 mcstats offset 25 pFactor 2.64 iFactor 0.09 dFactor 0.01 result 410.8469758
Sun Mar 03 17 25 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 3426.169 mcstats offset 17 pFactor 1.5 iFactor 0.29 dFactor 0.14 result 411.4017732
Mon Mar 04 02 52 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 37470.495 mcstats offset 87 pFactor 3.64 iFactor 0.28 dFactor 0.09 result 411.4888881
Sun Mar 03 23 25 24 EST 2019<EOT> postMessage EtbMonteCarloSequence 25041.479 mcstats offset 25 pFactor 1.15 iFactor 0.23 dFactor 0.02 result 411.928664
Sun Mar 03 17 31 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 3786.256 mcstats offset 40 pFactor 3.87 iFactor 0.25 dFactor 0.16 result 411.9970574
Sun Mar 03 20 40 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 15129.053 mcstats offset 96 pFactor 2.07 iFactor 0.05 dFactor 0.08 result 412.0791277
Sun Mar 03 21 4 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 16569.378 mcstats offset 5 pFactor 2.82 iFactor 0.28 dFactor 0.08 result 412.2158026
Mon Mar 04 00 55 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 30447.734 mcstats offset 85 pFactor 2.06 iFactor 0.03 dFactor 0.21 result 412.3386139
Sun Mar 03 20 34 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 14768.969 mcstats offset 14 pFactor 3.3 iFactor 0.06 dFactor 0 result 412.7112722
Sun Mar 03 18 13 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 6306.912 mcstats offset 8 pFactor 3.34 iFactor 0.29 dFactor 0.02 result 414.2935349
Mon Mar 04 02 55 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 37650.577 mcstats offset 95 pFactor 3.86 iFactor 0.12 dFactor 0.1 result 414.8168154
Mon Mar 04 02 16 32 EST 2019<EOT> postMessage EtbMonteCarloSequence 35309.614 mcstats offset 98 pFactor 3.4 iFactor 0.04 dFactor 0.17 result 416.5808052
Sun Mar 03 22 7 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 20350.293 mcstats offset 35 pFactor 3.79 iFactor 0.05 dFactor 0.29 result 417.0283248
Sun Mar 03 21 46 13 EST 2019<EOT> postMessage EtbMonteCarloSequence 19090.008 mcstats offset 25 pFactor 3.83 iFactor 0.1 dFactor 0.1 result 420.0146633
Sun Mar 03 22 49 17 EST 2019<EOT> postMessage EtbMonteCarloSequence 22873.735 mcstats offset 73 pFactor 2.92 iFactor 0.17 dFactor 0.13 result 420.91366
Sun Mar 03 19 49 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 12068.349 mcstats offset 2 pFactor 1.72 iFactor 0.25 dFactor 0.21 result 422.6931202
Sun Mar 03 20 46 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 15489.152 mcstats offset 25 pFactor 3.98 iFactor 0.01 dFactor 0.16 result 422.7713918
Sun Mar 03 20 19 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 13868.78 mcstats offset 65 pFactor 2.78 iFactor 0.15 dFactor 0 result 422.9530589
Sun Mar 03 23 43 27 EST 2019<EOT> postMessage EtbMonteCarloSequence 26124.136 mcstats offset 53 pFactor 3.93 iFactor 0.07 dFactor 0.11 result 424.3336633
Sun Mar 03 17 55 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 5226.626 mcstats offset 72 pFactor 3.38 iFactor 0.2 dFactor 0.06 result 425.8013481
Sun Mar 03 23 40 27 EST 2019<EOT> postMessage EtbMonteCarloSequence 25943.927 mcstats offset 73 pFactor 2.46 iFactor 0.01 dFactor 0.18 result 428.3924302
Mon Mar 04 01 25 31 EST 2019<EOT> postMessage EtbMonteCarloSequence 32248.499 mcstats offset 68 pFactor 1.78 iFactor 0.01 dFactor 0.18 result 433.505655
Sun Mar 03 19 58 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 12608.474 mcstats offset 28 pFactor 1.96 iFactor 0 dFactor 0.13 result 434.3284992
Sun Mar 03 23 13 22 EST 2019<EOT> postMessage EtbMonteCarloSequence 24319.436 mcstats offset 99 pFactor 3.62 iFactor 0.17 dFactor 0.25 result 435.2414507
Mon Mar 04 02 37 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 36570.155 mcstats offset 65 pFactor 1.99 iFactor 0.11 dFactor 0.01 result 435.6552579
Sun Mar 03 23 34 26 EST 2019<EOT> postMessage EtbMonteCarloSequence 25582.996 mcstats offset 17 pFactor 1.73 iFactor 0.19 dFactor 0.09 result 436.9173872
Sun Mar 03 18 34 10 EST 2019<EOT> postMessage EtbMonteCarloSequence 7567.214 mcstats offset 52 pFactor 1.38 iFactor 0.25 dFactor 0.01 result 438.0152025
Mon Mar 04 03 34 34 EST 2019<EOT> postMessage EtbMonteCarloSequence 39991.464 mcstats offset 85 pFactor 3.97 iFactor 0.03 dFactor 0.15 result 440.3342029
Sun Mar 03 22 46 17 EST 2019<EOT> postMessage EtbMonteCarloSequence 22693.685 mcstats offset 15 pFactor 3.31 iFactor 0.01 dFactor 0.11 result 444.1699974
Sun Mar 03 16 40 08 EST 2019<EOT> postMessage EtbMonteCarloSequence 725.412 mcstats offset 55 pFactor 3.61 iFactor 0.01 dFactor 0.08 result 444.4554706
Sun Mar 03 20 22 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 14048.818 mcstats offset 45 pFactor 2.52 iFactor 0 dFactor 0.2 result 445.6640605
Sun Mar 03 19 46 11 EST 2019<EOT> postMessage EtbMonteCarloSequence 11888.288 mcstats offset 52 pFactor 3.31 iFactor 0.01 dFactor 0.09 result 450.1616018
Mon Mar 04 00 25 30 EST 2019<EOT> postMessage EtbMonteCarloSequence 28647.088 mcstats offset 67 pFactor 1.88 iFactor 0.01 dFactor 0.14 result 464.0475839
Mon Mar 04 02 34 33 EST 2019<EOT> postMessage EtbMonteCarloSequence 36390.106 mcstats offset 39 pFactor 3.84 iFactor 0 dFactor 0.11 result 470.9389708
Sun Mar 03 17 1 09 EST 2019<EOT> postMessage EtbMonteCarloSequence 1985.811 mcstats offset 82 pFactor 3.78 iFactor 0 dFactor 0.06 result 473.9745847
Sun Mar 03 20 58 12 EST 2019<EOT> postMessage EtbMonteCarloSequence 16209.3 mcstats offset 78 pFactor 2.59 iFactor 0 dFactor 0.26 result 481.3195185
Mon Mar 04 05 19 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 46293.277 mcstats offset 48 pFactor 3.82 iFactor 0 dFactor 0.06 result 1226.868544
Mon Mar 04 04 16 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 42512.206 mcstats offset 79 pFactor 3.45 iFactor 0 dFactor 0.24 result 1226.950023
Mon Mar 04 04 58 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 45032.935 mcstats offset 9 pFactor 3.06 iFactor 0.28 dFactor 0.25 result 1227.238962
Mon Mar 04 04 37 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 43772.622 mcstats offset 46 pFactor 1.74 iFactor 0 dFactor 0.02 result 1227.671488
Mon Mar 04 04 28 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 43232.481 mcstats offset 59 pFactor 2.65 iFactor 0 dFactor 0.23 result 1227.711205
Mon Mar 04 04 13 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 42332.166 mcstats offset 94 pFactor 1.3 iFactor 0.08 dFactor 0.06 result 1227.76082
Mon Mar 04 05 16 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 46113.239 mcstats offset 51 pFactor 2.57 iFactor 0.19 dFactor 0.14 result 1227.972317
Mon Mar 04 04 34 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 43592.565 mcstats offset 31 pFactor 1.78 iFactor 0.15 dFactor 0.16 result 1228.454594
Mon Mar 04 04 19 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 42692.256 mcstats offset 17 pFactor 2.5 iFactor 0.01 dFactor 0.05 result 1228.755883
Mon Mar 04 05 7 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 45573.079 mcstats offset 19 pFactor 2.41 iFactor 0.14 dFactor 0.2 result 1228.929018
Mon Mar 04 05 10 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 45753.118 mcstats offset 9 pFactor 3.38 iFactor 0.23 dFactor 0.23 result 1228.94825
Mon Mar 04 04 49 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 44492.804 mcstats offset 37 pFactor 3.27 iFactor 0.11 dFactor 0.01 result 1228.952542
Mon Mar 04 05 13 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 45933.167 mcstats offset 35 pFactor 2.52 iFactor 0.17 dFactor 0.22 result 1228.993682
Mon Mar 04 05 4 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 45393.038 mcstats offset 18 pFactor 2.6 iFactor 0.01 dFactor 0.24 result 1229.376393
Mon Mar 04 04 46 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 44312.758 mcstats offset 39 pFactor 2.17 iFactor 0.06 dFactor 0.26 result 1229.69497
Mon Mar 04 05 22 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 46473.346 mcstats offset 5 pFactor 3.08 iFactor 0.1 dFactor 0.26 result 1230.199205
Mon Mar 04 05 1 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 45212.979 mcstats offset 79 pFactor 2.34 iFactor 0 dFactor 0.26 result 1230.37922
Mon Mar 04 04 31 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 43412.526 mcstats offset 70 pFactor 3.49 iFactor 0.29 dFactor 0.13 result 1230.551994
Mon Mar 04 04 40 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 43952.678 mcstats offset 79 pFactor 2.86 iFactor 0.24 dFactor 0.13 result 1230.556959
Mon Mar 04 04 10 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 42152.121 mcstats offset 18 pFactor 1.49 iFactor 0.22 dFactor 0.29 result 1230.562426
Mon Mar 04 04 22 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 42872.314 mcstats offset 76 pFactor 2.82 iFactor 0.19 dFactor 0.15 result 1230.947413
Mon Mar 04 04 43 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 44132.717 mcstats offset 79 pFactor 2.06 iFactor 0.1 dFactor 0.25 result 1231.077382
Mon Mar 04 04 25 35 EST 2019<EOT> postMessage EtbMonteCarloSequence 43052.404 mcstats offset 63 pFactor 1.85 iFactor 0.1 dFactor 0.21 result 1231.133348
Mon Mar 04 04 55 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 44852.898 mcstats offset 59 pFactor 1.17 iFactor 0.04 dFactor 0.19 result 1231.343703
Mon Mar 04 04 52 36 EST 2019<EOT> postMessage EtbMonteCarloSequence 44672.855 mcstats offset 27 pFactor 1.04 iFactor 0.17 dFactor 0.08 result 1232.668109
- Attachments
-
- random2.png (94.51 KiB) Viewed 39850 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
Re: electronic throttle body control ETB
you want to feed that data to some AI model?
Re: electronic throttle body control ETB
Speaking of that initial setup on BMW itself, did it use a separate valve for idle? The thing is, in cars with early ETBs, in addition to ETB itself they used a 'normal' stepper-based idle valve for some reason. Could it be so that those very ETBs wouldn't allow to control idle properly, so the engineers would keep both? The throttleangle/airvolume curve is too steep at low angles?
Wiki says, monte carlo is used for random processes, while controling throttle is not a random process? ziegler-nichols method doesn't work?
As for data, I am no way an expert, but I would pay attention to the difference between the two targets over time, and the way it affects the results. silly, but it could be, it requires different settings for different scenarios?
Wiki says, monte carlo is used for random processes, while controling throttle is not a random process? ziegler-nichols method doesn't work?
As for data, I am no way an expert, but I would pay attention to the difference between the two targets over time, and the way it affects the results. silly, but it could be, it requires different settings for different scenarios?
Re: electronic throttle body control ETB
these might be of interest:
https://www.researchgate.net/figure/E-lectronic-throttle-body-ETB-BOSCH-DV-E5_fig4_269272013In this project, the controller is built on National Instruments ’ configurable FPGA- FPGA -based based controller – the CompactRIO , and programmed with LabVIEW Real- Time , for a real- time, deterministic control. Various research has been reported on modeling and analysis of electronic throttle control. The intricate part of such system includes the hard nonlinearity of the pre- loaded spring, friction and unknown system parameters [2]. System identification is carried out with experimentation, data analysis an d understanding of system behaviour to determine the required parameters, following which, non- linear control design is carried out using input- output feedback linearization technique [2], [3]. In [4], nonlinear control of the throttle system is also propo proposed, sed, simulated and analyzed using SimMechanics and implemented with dSPACE RCP hardware, highlighting the friction compensator and joint stiction actuator, in addition to the nonlinear spring compensator, compe nsator, dead- zone and filtering. A discrete PI controller with w ith parameter scheduling, combined with feed- forward controller is simulated and tested in [5] but without friction or backlash compensation. A dual control algorithm is investigated in [6], using Xilinx- FPGA for process modeling and control implementation. implementation . For small initial throttle movement from zero, the system is regarded as linear and a large- signal control mode with PID controller is utilized. For all other instance, a small - signal control mode is employed, along with nonlinear friction, spring force compensation and air disturbance [6]