Q&A Forum
I love this plugin!
makes logging from obd that i have wanted for a long time possible. however i get a error code when logging to gauges and make a run, after the run is finnished it disconnects the blue box and all data is rejected... How can i post a pic of the error message?
Something bout system argument out of range. Index outside of area
It needs to be non-negative result and so on...Yup I know about this error, And that logging doesnt acturally record properly. Was going to talk with Jostein at some point and work out a plan for logging plugin data and raw logs.
amazing job!! i was wondering how do Will log for OBD1 honda ecus? a bluetooth CN2 adapter maybe?
Serial TTL connection. So yeah a bluetooth to serial port adapter will work.
What is that " Flashscan 01 ? You're using ?
Software I made for tuning OBD2 Hondas.
Cool! as son as you made it i'd like to test it!
more info about that software for OBD2 hondas? it Works with OBd2 ecus? how does exactly read external rom?
Guys,
I looked at it. The crash is because we have two plugins that both provide the parameter Speed, and the program does not handle that (yet).
For now, just delete the SpeedAndDistance.dll plugin. I will add some sort of way to avoid this issue in the future.
I love this plugin!
makes logging from obd that i have wanted for a long time possible. however i get a error code when logging to gauges and make a run, after the run is finnished it disconnects the blue box and all data is rejected... How can i post a pic of the error message?
Something bout system argument out of range. Index outside of area
It needs to be non-negative result and so on...
Yup I know about this error, And that logging doesnt acturally record properly. Was going to talk with Jostein at some point and work out a plan for logging plugin data and raw logs.
amazing job!! i was wondering how do Will log for OBD1 honda ecus? a bluetooth CN2 adapter maybe?
Serial TTL connection. So yeah a bluetooth to serial port adapter will work.
What is that " Flashscan 01 ? You're using ?
Software I made for tuning OBD2 Hondas.
I saw that error too, I should be able to solve it from my side, I will take a look.
I love this plugin!
makes logging from obd that i have wanted for a long time possible. however i get a error code when logging to gauges and make a run, after the run is finnished it disconnects the blue box and all data is rejected... How can i post a pic of the error message?
Something bout system argument out of range. Index outside of area
It needs to be non-negative result and so on...
amazing job!! i was wondering how do Will log for OBD1 honda ecus? a bluetooth CN2 adapter maybe?
We had a crazy working week and havent many time for study, I have tried to see some C# tutorials... very easy 😱 🤣 🤣
For the knock logging the mic is a very good idea, I have seen this before here,
https://www.youtube.com/watch?v=r-5aeey8CPU
Also here is the pro version that use a interface, not directly to the sound card,but I suppose is the same
What is that " Flashscan 01 ? You're using ?
Used Kalmaker back in early 2000s in Dos. Was one of my first experiences working on a Holden ECU.
Back then it was all closed source and for even sharing a bin make in kalmaker on the Holden PCM news group you got your posted deleted.
Have you seen Ken Young's Kalmaker tuning software and hardware for Holden commodores'.
Many people sell his product badged but Ken is the original author/designer.
I'm having a lazy Sunday on my Samsung s8+. Looking on ebay for a another laptop.
I have 3 memcals that I Cut the chips out of and soldered a socket into.
24 pin, 28pin and 32pin memcals.
I use a Ostrich 2.0 emulator during the tune since its real time editable and can tell you what part of the memory is being accessed in real time so you can trace hex and assembly.
Then once tune is done I give them the option to either UV erase there current memcal and burn tune onto it. Or cut the chip out and fit a socket and burn tune onto EEPROM (27SF512 in most cases.)
Ok , the VN, VR, VS.... ecu's with removable memcal..... do you direct tune the early VN,R,S ECU's or do you remove the memcal and flash them and plug the memcal back into the ECU/PCM's ?
ALDU code is still a work in progress to be added. (Laid base logic as in you select those code paths and it unloads the OBD2 module and attempts to load the ALDU code base) I want to get all the Honda stuff fully added and stable first tho which at current progress is about 3-4 days.
I use my own software for GM/Holden. Very similar to tunerpro rt which is what I orignally used but was too limited by its functions since it supported HEX tracing but not assembly tracing which is what you need when you have a ECU that no ones ever taken the time to make tuning definition for.
Sure the HEX tracing is easy enough to find tables by the layout and number of access hits. But good luck trying to find the speed cut/revlimit and offset stuff in HEX. You really need to follow assembly though its excucution path to find those.
Its a bit harder to port that stuff over to C# compared to the Honda stuff since its a lot older GCC C++ and C code. Where the Honda and OBD2 stuff was already in MSVC++ and C#.
Yeah Iv heard a little bit about PCMTec when I was looking for stuff for tuning a barra boss, My work shop is mainly GM/Holden stuff tho (Corvettes, Camaros, HSV), My boss couldnt justify the expense for another tuning software for newer ford stuff. So just went with aftermarket ECU for that barra boss (Speeduino). Did the job well enough and the owner of the car crashed it few months later writing it off lol.
This time of year I look for any excuse to get on the computer since its got nice AC blowing on me thats currently set to 21C.
Its just too hot to work on my car in the garage lol, Thats more winter stuff for me.
Hi Bmgjet , ok thiught it was a microphone jack but was second guessing myself so i had to ask.
I'm old school and use two VT knock sensors mounted on individual small pieces of 10mm thick plate of steel with a 10mm open slot for ease of mounting it on any engine location to monitor knock via osciliscope for visual purposes plus i use a electronics phone head set side by side. I have a lot of data to absorb to make the right judgment adjustments, no data logging to analyse which would be nicer.
That RPM 12V to 13.5V DC voltage divider can be modified possibly by playing around with the two inline series resistors to drop it down further than 5V DC with some simple maths Voltage_in divided to Voltage_out can be brought down to what a safe level for the microphone jack to operate in plus taking into consideratin the milliamps. I cant see any numbers on the op_amp they are using?
What method would you lower the Voltage_out on tha circuit as you mentioned adding more to it?
Great so you have the ALDL VN,VR,VS... plug_in working. What tuning software/hardware do you use for the earlier models pre 2000 with the removable memcals?
Have you heard of PCMTec a new Australian Ford oriented tuning software that uses the Tactrix Openport 2.0 " ? Obd2 connector for linking up. They have aready worked out the PID's.
I'm more a FORD MAN nothing against Holden's , Honda's, Nissan's and any other automotive manufacturer, it's just the way we are humans we have a favorite.
I'm trying to still get my head around C# coding and using Visual Studio 2017 Community edition software negating it's environment is challenging I think that saying " you can't teach a old dog new tricks " , is TRUE! LOL.
Last few day's here was unbearable in the workshop. The temperature reacted 49C by my weather station , l couldn't work sweat was just pouring off me. I need to buy another laptop so i can practice more at home after working hours. Nothing beats having a shower, nice meal a beer and switching on the evaporative cooling system to a respectable 20C so i can concentrate more on what I'm doing.
You should soon have your own blue box delivered and be able to crunch more plug_ins which you are already contributing huge amounts to the yourdyno community. That is a great effort by you BMGJet. Keep up the great work, l'm in awe of the work you are doing.