- First Name
- Richard
- Joined
- Feb 25, 2023
- Threads
- 0
- Messages
- 3
- Reaction score
- 0
- Location
- La Mesa, CA
- Vehicle(s)
- F-150
- Engine
- 2.0L EcoBoost
I'm using this one:
Sponsored
Sponsored
Forscan on a MacOS
- Thread starter Maverick2023
- Start date
- Watchers 4
- First Name
- Richard
- Joined
- Feb 25, 2023
- Threads
- 0
- Messages
- 3
- Reaction score
- 0
- Location
- La Mesa, CA
- Vehicle(s)
- F-150
- Engine
- 2.0L EcoBoost
As a quick followup:
I had also installed FORScan into a Windows XP PC, but it didn't work there either. I found it was because of the drivers I had installed. I had follow instructions for generic FTDI devices and I needed to install the specific driver pointed to by the company's Amazon page. Once I removed the other drivers and installed the correct one, the Windows XP version worked just great. I have now made the modifications I wanted.
I had also installed FORScan into a Windows XP PC, but it didn't work there either. I found it was because of the drivers I had installed. I had follow instructions for generic FTDI devices and I needed to install the specific driver pointed to by the company's Amazon page. Once I removed the other drivers and installed the correct one, the Windows XP version worked just great. I have now made the modifications I wanted.
- First Name
- Jose
- Joined
- May 26, 2024
- Threads
- 6
- Messages
- 94
- Reaction score
- 249
- Location
- California
- Vehicle(s)
- 2024 Maverick XLT
- Engine
- 2.0L EcoBoost
Okay reviving this. I got it to work on my M2 Mac air. Using Homebrew and Wine. My issue is the fact that it takes 15 minutes just to get some modules to show up. Tried increasing the baud rate only to have it fail. Most I could get it to was like 37 kbps. Any chance there’s anyone with a workaround?
Sponsored
