[Radioflyer]

I have a 13 inch Macbook (OS 10.7) running Parallels 6 and Windows 7. I'm tying to use some software written for Windows to communicate with an aftermarket Engine Control Unit or ECU. The purpose of the software is to monitor the engine's performance and to be able to edit control parameters and tables used by the ECU to measure air flow, fuel, timing, load and throttle position. The software runs OK, I can do everything I should be able to the version of the data stored on the computer.

My problem is the ECU will not respond to my computer and ultimately I need to gain access to the data files in the ECU. The Macbook is connected to the ECU via an ethernet cable. I turn the ECU ON, start up the software, execute a command to search for the ECU and the message is "no response". I've tried to set up a dedicated local network between my computer and the ECU and believe I've managed to turn off the Windows firewall. Since i'm not proficient with Windows I reverted back to the Mac OS to confirm the set up and assume the Mac is operating correctly in terms of the connection with the ethernet cable. From the Mac side I can see the IP address of the ECU and its as described in the manual.

At the end of phone call to the ECU Guru, he tells me he believes my Macbook will not work and I should get a "real PC". He might be right but I'm hoping I can get some advise which will lead me to identify what I need to do to get my Macbook to communicate with the ECU.

[ghporter]

The "ECU Guru" is an idiot. The issue here appears to be that the Ethernet connection in the ECU expects a direct connection to a real network adapter, and your Parallels pseudo-adapter isn't doing what it expects. I'd connect the MB to another computer while running Win7 in Parallels, and see if you can ping back and forth between the two machines (use the command line ping tool in Win7). If it doesn't work (I think that's about 50% probable) then you can tweak the settings between Parallels and the MacBook to make it work. If it does, then it's probably got something to do with the protocol the ECU is expecting not making it through the layers of virtualization between the actual Ethernet port on the MacBook and the software in Windows 7.

You might consider trying another means of running Windows on your MacBook-I have been using VirtualBox on a first gen MBP for quite some time to run the software I use at work-which is of course Windows only-without a single hiccup. It seems to automatically find whichever MBP network adapter I specify to bridge into Windows, and just run with it.

[Atheist]

I suspect the ECU isn't necessarily a network device as much as it's just utilizing the ethernet port to communicate with the software. I doubt any VM software will allow the guest OS to communicate directly with the ethernet adapter.

You may have to go the BootCamp route to get this to work.

[Radioflyer]

Originally Posted by Atheist 

I suspect the ECU isn't necessarily a network device as much as it's just utilizing the ethernet port to communicate with the software. I doubt any VM software will allow the guest OS to communicate directly with the ethernet adapter.

You may have to go the BootCamp route to get this to work.

Boot Camp works, I now have access to the EUC. I sure appreciate your help, Thank you very much. Huge relief.

And, Mr Porter, the EUC Guru is definitely not an idiot. Uniformed, unwashed maybe but he really knows his ECU stuff and fuel injected engines. With this success and the greater number of Macintosh computers being used I'm sure he will accept this as good news.

I have a grin from ear to ear that won't go away.

[cgc]

Originally Posted by Radioflyer 

...I have a grin from ear to ear that won't go away.

I have a taser that will help erase that smile if you'd like.

[ghporter]

OK, maybe he's "a computer idiot" rather than a complete idiot. But it looks like I was right-the translation from real network adapter to virtual adapter in Parallels wasn't doing what you needed. I'm glad you got it working.