I have an INPA cable (bought one that was linked by another NAMer) and am trying to get it setup with my computer. When plugged into the computer, it shows up as Com3. When I go to the 'Properties' for that port/device and click 'Advanced' so that I can change the port to Com1, I get a message that says I need permission to write to the registry for that device. I am an administrator on the machine. I have spent a lifetime avoiding Windows so I am at a loss as to what to do to get past this. Can anyone point me in the right direction?

 

^^^ Assumption that Com1/Com2 already in use, thus Com3 the next available port for your INPA USB cable. Why not use that port?

 

I wish that I could give a more satisfying answer to your question but I'm afraid that I can't explain the underlying reason for the need to use Com1; all I can do is offer the imperfect reply that multiple sets of instructions indicate that the INPA cable must use Com1. I can report that I am unable to get the cable to communicate with the car using Com3.

 

Can you determine what device is currently using Com1, disconnect/disable that, then use for INPA? All my networking devices are Windows, Chromebook or Android but that hardly makes me an Windows expert. When I had Adrian do the remote tune from Romania, I just plugged into an available USB-A port on my Win10 Pro laptop and the program was ready for him to start "driving". Seems unlikely that port was Com1...

 

Thanks for your reply, @MCS4FUN . In the Device Manager, no other ports appear to be in use. Though this wasn't the case once upon a time, the ports are now virtual. In other words, you can change the port for a device (though the device manager) without changing the physical USB port to which the device is connected. What I'm up against is that Device Manager is telling me that I don't have permission to make the change -- at least I think that's what it's telling me.

 

Although it's been years (4/5), I use to hack/modify Windoze on a daily basis. It seems to me you may need to "Take Ownership" protocol - even if you are admin. There is a simple tool that you can do that with that easily enables "T O" w/ a simple click.
I'm not in front of my PC right now but Google : Take Ownership. I hope that maybe a solution (?).

 

Thanks Here2Go. I read a bit about TO. Before trying it, I thought I would make sure that I had a valid driver. After downloading a driver from FTDI, I tried to install it. At that point, Windows informed me that I already had the best driver installed. Then I tried again (one last time) to change the com port before diving more deeply into TO. For some reason, it worked. I have no idea what (if anything) was different from yesterday. So I can now use NCSExpert and NCSDummy. I made a few changes (windows auto up, comfort closing, auto unlock when engine turned off) and am researching other changes I want to make.

Currently, I'm trying to figure out what role the profile file plays in coding. When I launch NCSExpert and chose File -> Load Profile, there are 6 or 8 options. I'm not clear on what effect choosing different ones will have. I used NCS Dummy Default for the first session.

 

In case anyone finds this thread later when looking for information regarding NCS profiles, according to Adrian you can use either the Expertenmodus profile or NCS Dummy profile.