ICOM Emulator Mysteries

tinkerman · 08-18-2013, 02:52 AM

The ICOM Emulator has left me with many unanswered questions. Some are:

1. How does the dongle security scheme work exactly?
Note: There is the ‘dongle-required’ version and a ‘dongle-free’(dongle-NOT required) version.

2. What is the role of Java within the ICOM Emulator?

3. What is ifhsrv32.exe(interface handler) doing exactly?
Is it ‘connecting’ ISID and EDIABAS that is installed within the ICOM Emulator VM? Or is it connecting to the host system?

4. Why is the ‘ecu’ folder within the EDIABAS installation in the ICOM Emulator VM practically empty (1-several files only)?
Note: My regular EDIABAS (7.3) installed in the host system has accumulated over 1,900 files.

5. Why does the ICOM Emulator make the system get so hot?
Even with the ISID VM NOT running, I noticed that when the ICOM Emu is activated, the system’s cooling fan rpm goes into full rpm, and the dongle gets really hot too.

Any ideas?

Sensible_ · 08-18-2013, 11:26 AM

ICOM emulator is a complicated bit of kit. As a fellow programmer I take my hat off to the developer.

I imagine it mimics the ICOM A firmware and this can use most cable types (ENET, DCAN, ops) as an I/O device to the car.

I would imagine there are several dongle checks whilst starting JICOM.dll. This dll no doubt checks serial number and other I'd features of a USB flash chip.

This can be bypassed in three ways -

1. Easiest. Patch dll to remove security calls to verify USB.

2. Clone USB if you have correct details, and correct USB.

3. Code your own emulator and install within ISID

I don't know about an emulator without dongle protection. I guess JICOM.dll has been patched.

I guess the heat issue is to do with VMWARE rather than any dongle code.

08-18-2013, 02:52 AM	#1
tinkerman Private First Class 57 Rep 104 Posts Drives: '07 320i (E90) Join Date: May 2013 Location: Korea iTrader: (0)	ICOM Emulator Mysteries The ICOM Emulator has left me with many unanswered questions. Some are: 1. How does the dongle security scheme work exactly? Note: There is the ‘dongle-required’ version and a ‘dongle-free’(dongle-NOT required) version. 2. What is the role of Java within the ICOM Emulator? 3. What is ifhsrv32.exe(interface handler) doing exactly? Is it ‘connecting’ ISID and EDIABAS that is installed within the ICOM Emulator VM? Or is it connecting to the host system? 4. Why is the ‘ecu’ folder within the EDIABAS installation in the ICOM Emulator VM practically empty (1-several files only)? Note: My regular EDIABAS (7.3) installed in the host system has accumulated over 1,900 files. 5. Why does the ICOM Emulator make the system get so hot? Even with the ISID VM NOT running, I noticed that when the ICOM Emu is activated, the system’s cooling fan rpm goes into full rpm, and the dongle gets really hot too. Any ideas?
	Appreciate 0 Tweet Quote

08-18-2013, 11:26 AM	#2
Sensible_ Colonel 529 Rep 2,503 Posts Drives: 2008 E90 Join Date: Feb 2012 Location: London iTrader: (1)	ICOM emulator is a complicated bit of kit. As a fellow programmer I take my hat off to the developer. I imagine it mimics the ICOM A firmware and this can use most cable types (ENET, DCAN, ops) as an I/O device to the car. I would imagine there are several dongle checks whilst starting JICOM.dll. This dll no doubt checks serial number and other I'd features of a USB flash chip. This can be bypassed in three ways - 1. Easiest. Patch dll to remove security calls to verify USB. 2. Clone USB if you have correct details, and correct USB. 3. Code your own emulator and install within ISID I don't know about an emulator without dongle protection. I guess JICOM.dll has been patched. I guess the heat issue is to do with VMWARE rather than any dongle code.
	Appreciate 0 Quote