For any add-on boards such as VR conditioners, optos and OEM interface boards
User avatar
By digmorepaka
#56889
NickZ wrote: Tue May 10, 2022 10:25 pm from what i understand your saying, the Accelerator need one value to be going up and one to be going down?
My Toyota Prius pedal both go up.
throttlepedal.jpeg
The primary value has to be going up yes, however the secondary does not.

What you have posted is the throttle, actually the same as mine. In toyota naming VTA is throttle VPA is pedal. You seem to have the same throttle as my Verso. I am using parts off a 1ZZ corolla verso
Image
Image
#56899
NickZ wrote: Wed May 11, 2022 10:53 am I don't understand menu 7
I can draw an explanation graph if you want to set it up. Frankly even when you do understand it it's a pain in the ass to setup which is why my current priority is automating it.
#56903
Automatic pedal calibration working now, still requires input for where in the range the point is desired but the actual adc input correlation reading is done automatically. Next is throttle, after which I will push it to github. I think the process could be simplified further by including calibration profiles for known throttles, such as the Toyotas so the user can calibrate it without much trial and error.
#56911
@NickZ Auto calibration now working and pushed. For the Toyota throttle in menu 7 -> TPS -> absolute 370, 570 seems to work well with my resistor config. It might take a second on the throttle, on some levels it snaps instantly, on some it takes a couple seconds. If it's not getting there within ~45 seconds then you can try to push the throttle plate with your thumb back or forward a bit for it to find it's place(be careful if it slaps your finger it will hurt like a bitch!)
By NickZ
#56912
I ended up changing lines 268-269 to a value of 0 and being able to make it work to full throttle.
I have no idea about what its doing with the safety values.

TPS Error = 153
TPS = 292
Expected TPS2 = 264
TPS2 = 111
APP Error = 2
APP = 323
Expected APP2 = 162
APP2 = 160
safetyCount = 0
safetyMode = 0
325.00 500.00 562.00 865.00
162.00 650.00 715.00 744.00
283.00 327.00 602.00 897.00
105.00 691.00 1016.00 872.00
User avatar
By digmorepaka
#56913
NickZ wrote: Wed May 11, 2022 10:02 pm
325.00 500.00 562.00 865.00
162.00 650.00 715.00 744.00
283.00 327.00 602.00 897.00
105.00 691.00 1016.00 872.00
Other than min max these look like the defaults.

For the TPS you'd want to hit these. The second one doesn't really matter as long as it's between the minimum and third point. Third point in this case is where it becomes non-linear so you want that to be as close as possible to itself.
Image

(edit messed up the image, really need some sleep)
By NickZ
#56916
why can't the whole process be automated. couldn't you use some calculations from the calibration to make the safety points?
Would make it easier for the average user.
The controller could have a button for clearing calibrations, then powering it back up would automatically re calibrate, write the eeprom and away we go.
User avatar
By digmorepaka
#56918
NickZ wrote: Thu May 12, 2022 6:30 am why can't the whole process be automated. couldn't you use some calculations from the calibration to make the safety points?
It can, and hopefully will soon. I have to do a bit more research on the commonly used curves first. At the moment I'm focusing more on the core functionality rather than the user friendly-ness. For the Toyota a simple algorithm that would start with a linear map and then find the point of biggest error would do, but not everybody uses this arrangement.
NickZ wrote: Thu May 12, 2022 6:30 am The controller could have a button for clearing calibrations, then powering it back up would automatically re calibrate, write the eeprom and away we go.
Currently each calibration is a separate step because that's the best while testing. When I'm working on TPS calibration I don't want to erase my APP calibration and re-do it every time.

When the core functionality is finalized it is definitely something that I would consider adding.
By NickZ
#56992
Latest update is working well, ive worked out the calibration bit, if i use 1 and 1 it works fine.
after about 3/4 throttle you can hold and maintain it, but anything under that it will hold for about 3-5 seconds and then go into safety mode, I think the slight oscillation of the butterfly trips the safety.
What error tolerance is there with the APP and TPS and can it be adjusted?
20220517_212202 copy.jpg
20220517_212202 copy.jpg (405.74 KiB) Viewed 4804 times
this is my hardware design im playing with.

Hi, I am trying to assign Signed values to the x-a[…]

Vr Conditioner Noise when cranking

New version 202305 don't fix the issue. Now after[…]

blitzbox

I've finally figured out why MAP and Lambda weren'[…]

Hello, I bring news!! Let me tell you that after […]

Still can't find what you're looking for?