New Diagnostic Software for MBE ECU
Discussion
Are you sure the USB/COM-Port Adaptor is on COM5 ? Some notebooks with Bluetooth show some COM-Ports which could be related to a Bluetooth Connection. Is the COM5 Port the only Port which is available in MBETool ? Did you look into the Device Manager to acknowledge COM5 ?
Did you press the Plip after Ignitin ON to power up the ECU ?
Are you sure that the cable is OK ?
Did you press the Plip after Ignitin ON to power up the ECU ?
Are you sure that the cable is OK ?
The adaptives are stored in memory of the ECU and they are re-adjusted everytime you drive. Resetting the adaptive means setting both adaptive maps to zero. The Ecu will then rebuild them. If after a long run one bank is out of the normal range you know that you have a problem on this bank.
Yes, I have made some modifications so it only goes offline after loosing the COM-Port without an error.
You only have to reconnect afterwards.
I'm only waiting to make the new version public, because I want to have implemented the Read Adaptive Maps before.
Unfortunealy I spent some time on my Wideband Lambda project which runs fine now, last week was the 3 Nations Gathering, next weekend is Zolder Continental Meeting.
If you send me a PN with your eMail, I could send you an interims version.
You only have to reconnect afterwards.
I'm only waiting to make the new version public, because I want to have implemented the Read Adaptive Maps before.
Unfortunealy I spent some time on my Wideband Lambda project which runs fine now, last week was the 3 Nations Gathering, next weekend is Zolder Continental Meeting.
If you send me a PN with your eMail, I could send you an interims version.
Regarding the wrong values:
I programmed the detection of the ECU over the serial port not very strict. So it can happen, if you have selected a wrong port which is responding in some manner, that the software shows random values.
But I see an advantage in this simple detection: The Software connects easier with the different ECUs and I don't need to make changes to the program for every MBE ECU which TVR fitted.
If you look in the footer of the window, you can see 'MBE Type found'. So the type is missing, should be something like 'ECU #94130116 found'...
I programmed the detection of the ECU over the serial port not very strict. So it can happen, if you have selected a wrong port which is responding in some manner, that the software shows random values.
But I see an advantage in this simple detection: The Software connects easier with the different ECUs and I don't need to make changes to the program for every MBE ECU which TVR fitted.
If you look in the footer of the window, you can see 'MBE Type found'. So the type is missing, should be something like 'ECU #94130116 found'...
Edited by EvoOlli on Saturday 21st June 13:07
clive f said:
all set up on the new laptop, works a treat on windows 8, no problems at all, thanks Ollie, let me know when the adaptive maps are available.
Nice to hear, thank you....at present weather is too beautiful to sit in the dark office and program little tools....much more nicer going out with the Sag ;-)So hope for rain and the adaptive maps menu will be finished finally (hopefully).
Should be the speed of the graph, how fast it srolls from the right to the left.
But I changed this in the meantime, the graphs are now separated and there's a simple way to zoom in.
When I'm finished with the adaptive maps I will make an Analyzing program where you can get more information from the logged files...stay tuned ☺
But I changed this in the meantime, the graphs are now separated and there's a simple way to zoom in.
When I'm finished with the adaptive maps I will make an Analyzing program where you can get more information from the logged files...stay tuned ☺
Take a look into the Device Mangager. There you will see if the correct driver is loaded. Maybe an yellow exclamation mark beside the USB Adapter ? This shows a failed driver installation.
If the driver is loaded and the Adapter has got a virtual COM-Port name, but MBETool doesn't show this Com-Port in the List, you can manually type it into the lower entry field.
If the driver is loaded and the Adapter has got a virtual COM-Port name, but MBETool doesn't show this Com-Port in the List, you can manually type it into the lower entry field.
Windows CE is dead, so there won't be any version for this from me.
But look at my Wideband Lambda Thread and you'll get an idea how my solution with a good display looks alike...
I have a small display / diagnosis solution ready without all the Lambda things at the moment. If I get the time I will present it in the next days in this thread.
But look at my Wideband Lambda Thread and you'll get an idea how my solution with a good display looks alike...
I have a small display / diagnosis solution ready without all the Lambda things at the moment. If I get the time I will present it in the next days in this thread.
Edited by EvoOlli on Friday 25th July 06:42
Yes, my mobile version works without the Lambda things and hopefully fits into a small enclosure with a size of around 120x70x30mm. Hard- and Software is finished, only problem at the moment is finding a good case.Today I will get some enclosures which will go onto my (very small) milling machine on the weekend.
I will call it a 'MBETool Light' because it doesn't have the logging facilities of it's big brother :-)
I will call it a 'MBETool Light' because it doesn't have the logging facilities of it's big brother :-)
Hi Craig,
not a direct upgrade possible, but you can reuse the Display Shield, which is the most expensive part of the setup.
The 'Light' Version consists of an Arduino Uno with Serial interface and the Touch Display.
The 'Full' Version is based on an Arduino Mega with an extra level converter for the serial port.
So main difference is only the Arduino board. The Uno doesn't have enough memory to hold the full version.
Best combination would be a small Arduino Uno with serial interface, but with the bigger processor of the Mega. But there isn't any on the market.
not a direct upgrade possible, but you can reuse the Display Shield, which is the most expensive part of the setup.
The 'Light' Version consists of an Arduino Uno with Serial interface and the Touch Display.
The 'Full' Version is based on an Arduino Mega with an extra level converter for the serial port.
So main difference is only the Arduino board. The Uno doesn't have enough memory to hold the full version.
Best combination would be a small Arduino Uno with serial interface, but with the bigger processor of the Mega. But there isn't any on the market.
Gassing Station | Speed Six Engine | Top of Page | What's New | My Stuff