MSefi.com read only forum (Jan.15,2018)

Has anyone used one of these yeat? I am hoping to have my megasquirt uner the hood and would like to have wireless running to my laptop so I can tune from inside or around the car. And what about addind a bluetooth card right into the megasquirt? Is this A good Idea? I am going to seal my megasquirt, and put some desicant in it when I do install it, and was wondering if the db9-bluetooth adapter was weather resistant?

tried a Socket (www.socket.com) on mine. http://www.socketcom.com/product/connec ... 00-479.asp

It worked most of the time but its an expensive solution compared with a short run of cable an a db9 hidden under the dash and I didnt find it reliable. Loads of dropped comms and flash burn issues. Useless when trying to use Autotune. Some folks have had more success with other wireless systems though.

Jon

Hey thanks fo the info anyone else?

First off you DO NOT want the ECU under the hood. Descicant isn't going to cut it. The issue is heat, moisture and vibration. Not all the components in the ECU are rated for the heat and the extra vibration isn't good either.

If you absolutly had to have it under the hood, then you need to make some mods starting with a good potting of silicone over the entire top and bottom of the PCB, if you can't get a case thats not 100% enviromentaly sealed. These cases are not cheap either. If you do use a sealed case, your still goint to need to protect all the componets that are not flush mounted from vibration with some silicone support. You will need to change the connectors to automotive grade ones. These are also prohibitively expensive.

After all of this, you still have the issue of a lot of the components are not rated for the heat in the engine bay.

I have used several differant wireless adapters. I use the Socket one often enough. I never have had any issues with mine. But burning code into ANY ECU without a solid cable connection is probally not the best idea. I usally don't even burn code in the car, prefering to put the unit on a bench and use a reliable power supply and a stimulator. This is my personal rule from more than one code burn getting hosed in a car.

Thanks for the reply. The components in the ms2 v3 are for a good temp range they havent had the feed back from people who have put them under the hood to be sure. I will seal it and I can install all the conectors I need I get them for free! The vibrations under my hood are the same as the rest of my car. My road runner has lots of space under the hood I can find lots of places to mount it that dont get that hot.

I guess I should ask about all wireless conections not just bluetooth! My lap top has wireless and It is how I use it to do everything so I know this would work for megasquirt programing.

arlo#1 wrote:...My lap top has wireless and It is how I use it to do everything so I know this would work for megasquirt programing.

Its not that easy or everyone would be doing it. Simply put there is NO wireless solution thats perfect for this. Less expensive solutions have questionable links. Better links, cost more. Bluetooth is actualy about middle of the road for cost and link. And if you want to use the wireless in your laptop, the 802.11 protocols.... Those are the most expensive modules out there. Bu they are avalible. I think the 802.11 setup would be about the only one I would trust for reflashing my ECU over wireless.

hate to bring an old post from the dead..but..
i am putting my ms 2 v 3.0 together and i do have the db9 blue tooth. im not really clear on how i should go about installing it.

1. i am reading that they are not the best.

2. u need to use the serial to burn(or highly suggested).. mine came with a switch to change from 1 to the other. i am just unsure about installation..
3.i did the search..not sure if i worded it right or not. does anyone have a nice pic of 1 of these bad boys installed and have some kind of layman terminology to get me on track????




thanks gents! don

What sort of adapter do you have?

They do vary. Some will require a handshake, so you will need to make the modifications described here:
http://www.megamanual.com/com/bluetooth.html

Others do not. They just need to be configured with the proper serial settings for your set up and plug it in.

The v3.0 board has power on PIN 9, so If it powers off PIN that will power it.

The ones EFI Analytics sells are just plug into the DB9 and connect.

I have been using the bluetooth from Phil and it works without flaw to my phone running ShadowLogger(shameless plug, you should try it!). The bluetooth from my usb dongle in my laptop doesn't like to stay connected. It connects fine, runs for a while and then drops, reconnects and starts over... I think it is the dongles fault because the phone never has an issue. It seems that there may have been instruction that came with the EFI Analytics adapter that mentions adjusting a setting, I'll have to look for it.

Mark

this is the pic from the ebay page..rs232-ttl module? letme know ..don

floppy,
If you are running MSII B&G firmware over Bluetooth, you will likely need to raise the interWriteDelay.

Over Bluetooth TunerStudio doesn't have the fine grained control over the speed it sends bytes, they can end up in a buffer then flush all at once too fast for the firmware and it can miss bytes.

Try editing your mainController.ini and change interWriteDelay to say 15, if it doesn't solve keep raising it to 25 if needed.

Don, those BT boards can work. You can get them cheaper than that too. They have been narrowly tested with some people having more success than others, but there is no reason it should not work when configured correctly. Like all things there are pros and cons. The range will be about 1/4th that of a plug in class 1 adapter and the throughput will be lower. It does take less space though.

thanks for your input sir! on the auction it says that everything is already configured. it also says it's good for about 20 foot. well, i wil be using it in the car. i like the idea of it,since its a 76 mustang and i can pretty much hide it up in dash.i do have the shadow logger in my phone and i can wait to get started using it! when i bring it up is there a way to surf it, or does it need to connect to actually get into the shadowlogger? thanks..don russell

You can download and install Shadow Logger without anything to connect to, but there isn't much to see until you do

Try editing your mainController.ini and change interWriteDelay to say 15, if it doesn't solve keep raising it to 25 if needed.

I'm having a tough time finding the interWriteDelay setting that corresponds with my project. I have found several but none that seem to match my version.
MS2-2.888 and TS beta.
What is the path?
Thanks, Mark

It would be:
[PathToYourTunerStudioProject]\projectCfg\mainController.ini

I just checked a 2.88 ini file, and I see why you would have trouble finding interWriteDelay, it doesn't seem to have one defined... So it would be using the default 3
It is normally with the other timing commands at about line 135...
Anyway try adding this line:

interWriteDelay = 15

Sorry to be a pain but I am still having trouble finding the maincontroller .ini. In projectCfg there is no maincontroller.ini. There is a MSII 2.888.ini but when I open it there is solid full page text and is unlegible. I tried changing the properties with no luck in changing to a standard view. and goto line 135 didn't help. Am I missing something simple?
I did add the line in the mtCfg folder/megasquirt-II.ini file. It seems to be more stable but have not fully tested to see if it really helped.
Thanks, Mark

BTW- I am open to different firmware and have been considering MS2-Extra?

Hi floppy,
Is the MSII 2.888.ini the only ini in that folder?

Have you been using that project for a very long tim by chance?

Way back, maybe 2 or 3 years ago in the betas, TunerStudio did not set filename to mainController.ini, it would just copy what ever ini you selected to that folder with the same name it had.
So it you have been using the same project for 2+ years, that may just be your ini.

That is actually why I standardized it, so I know what it is called.

It doesn't actually have to be called mainController.ini, in the project.properties by the line starting with:
ecuConfigFile=

Hi Phil,

I have been using 2.888 for 2-3 years. It is the only ini in the project file.

I think I will jump to 2.905 just to be current.

Thanks, Mark

You should be able to edit that one.

If you upgrade to 2.905, you will end up with a mainController.ini, then edit that on...

I may need to put a place in the UI for users to over ride the interWriteDelay if needed for BT.