Jump to content

Auto Tech Wiring

Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Auto Tech Wiring's Achievements

  1. CDM v2.12.32 Beta for ARM64 drivers turn off driver signing and force install the drivers so far have to reinstall drivers for every ECU you connect to as G4x seems to start at Link ECU 1 and 2 and so on when u connect each ECU, supper annoying but is what it is. CDM v2.12.32 Beta for ARM64.zip
  2. Interesting wonder why it doesn't work then I will try again today and get back to you thanks.
  3. Does the Link G4x use FTDI to communicate there are 100% FTDI drivers for Windows ARM available but the ones I have tried so far did not work with Link G4x but did with other FTDI devices
  4. I have a similar issue but only with the G4x. I have managed to get all other ECU's to work using arm drivers as mentioned and other methods including virtual com ports. This has worked with all other ECU brands as well, the Link G4x seems to be the only one that I can't make work. Parallels works perfectly with the Intel MacBook and G4x but with the M1 you have to run Windows 10 ARM or Windows 11 ARM. If Link could provide what they are using to communicate with the ECU this problem could be solved with just ARM drivers that all Windows ARM users are going to need anyway. This is the direction technology seems to be heading anyway so can't see why Link wouldn't spend some time on solving this. So at this point all ARM based laptops can not communicate with G4x. Seeing as a lot of the long battery life track day friendly laptops are ARM based now and becoming more popular might be worth looking into. Its not so much a Mac issue as there are no ARM drivers for Link G4x.
×
×
  • Create New...