[lbalan79]

Hi all,


I have issues connecting through the ICOM interface to my F25. I was able to connect using ISTA+ directly using an ENET cable connection but because I am looking to update the ILEVEL I got an ICOM Next.

Using ITool Radar I can see the connection and also when I start Easy Connect I can get the interface locked and reserved. However whenever I start ISTA+ and try to connect all connections drop and time out. I am not able to see the connections after trying to identify the vehicle and I get connection time out no matter what tool I use afterwards (including web admin interface). If I restart the process by disconnecting ICOM from car and rebooting it I can see it again until I try to connecting in ISTA+. Any help is appreciated.

Some specs: ICOM Next: ICOM A1 Firmware: 03.22.21 (VXDAS Clone)
ISTA+: 4.32.15
ITool Radar: 1.1.1 ( works fine)
Easy Connect: 7.3.0 (works fine) I use remote IP and BASE
Disabled all protection under Windows and everything works fine using ENET direct cable.

Please let me know what I am missing.

[zeronoo]

Had same problems with ISTA 4.32.15 and original ICOM NEXT latest ilevel firmware connected direct to laptop. Worked perfect for about 2 weeks then no more. Tried with different 4.3x version, same problem. It worked however with DHCP server (sw and hw) but pretty chaotic...never understood why.

[Sajuk]

Had these problems too.
Solution was using older firmware:

ICOM: 03-22-11
ICOM Next: 04-22-11

Works since downgrade to this firmware and make no problems at the moment.
Used currently ISTA_v4.36.40.27058

[ferrum]

It's not about the firmware, all Chinese clones need to be fixed in order for them to work

[zeronoo]

Well, my ICOM Next is original...

[CATAHA]

i had similar problem(s) in my case it was two things
1 firewall
2 (in windows) when i connected directly via cable i wasn't able to change from Public to Private, MAIN PROBLEM in Win10/11 networks been 169.xxx.xxx.xxx automatically go into untrusted mode(block everything)
2.a In Win7 i was able to do it via regedit, but in 
Windows 10/11 
adjusting via regedit DOES NOT WORK
adjusting via powershell DOES NOT WORK
ONLY WAY TO MAKE IT WORK via gpedit, about 5~7 settings

If you are able to adjust via regedit/powershell in Win10 then your build hasn't been updated in YEARS

[Mwahab]

Well, i have a pc with this particular ISTA, Don't lock the ICOM using easyconnect, when u are using ICOM, Open connection manager in ISTA, you will see your ICOM FREE, then go ahead

[lbalan79]

Thank you all for the help. Got it closer to work but I might have broken the current firmware settings. Here is what happened:
- I went to the admin web console and changed in Lan settings to a static IP that is local: 192.168.68.41
- I also changed the mode from ISPI to ISPI-Next
- I reconnected the ICOM Next to car and Lan
- I opened ISTA+ and now it is being seen but under status I see Firmware which tells me the firmware needs an upgrade. I was happy thinking I fixed it
The problem: 
- I cannot connect anymore to the new or older IP to the admin port or software update port
- IToolRadar sees the new two entries with the new ICOM IPs but under device state shows N/A. There is no way to even see properties when I click on the device like before
-  I tried updating using an USB formatted to FAT32, copying ICOM_Next-app-012310.tar.gz and ICOM_Next-rootfs-012310.tar.gz, pressing the front white button while plugging it in and as soon as leds are red pressing it 3 times. Every time, no matter what I do the device moves to having the System led blinking and then turning green. So no update happens.

I am lost of ideas on what to do .

[Vojno]

It is looks like ICOM has low memory?!

As Ferrum said, it must be "repaired" first then it can be properly updated.

But it seems to you thath your ICOM NEXT is ICOM A2 hardware, use appropriate firmware for this!

[lbalan79]

Thank you,

It showed A2 when iy was working. Should I use the next firmware ? Anyone has a link to exact files so I know which ines to use? 

Also I put another post about a system.settings file. Anyone has an example of a working one? Since system light seems ok I might be abke to have it work just by reverting to factory settings and upgrading. 

Any help appreciated.