PathPilot on a Novakon, Upgrade to Version 2.1.5 - Tool Table Issues.- SOLVED???

billyjack wrote: Hey snowgoer.
I've tried all the latest versions and cannot get the later versions to run. I keep getting a screen to pick my configuration from a list and the 1100-3 is not even listed. and it keeps going back to the same screen regardless of the selections. I've spent the day trying the different configurations and will attempt version 2.0 tomorrow which I hope will work for me. If I don't get some guidance or even a direction to look, I'll revert back to 1.9.7 with a learning experience I hope to soon forget. This has been a major disappointment.
Bill

Weird. I have an 1100-3 and it’s there when I go to the switcher. Maybe they added some new fun checks for modded firmware or something.

Weird. I have an 1100-3 and it’s there when I go to the switcher. Maybe they added some new fun checks for modded firmware or something.

I take it you have the bit file in the correct place and the load line in the ini file with the same bitfile

OK Guys, this is what I've learned by trial and error (with some thoughtful help from here)!
Tormach did make a change to expand their tool table starting with version 2.1.X. Now In My Opinion. They also are setting some sort of hardware switch for tormach machines. The use of software above the 2.0.4 for the Novakon Torus Pro (and maybe others????) will result in a corrupted tool table after the first restart. Thus the loss of the table.
To get me to the point of a functional 2.0.4. First thing, backup the system and tool data to a flash drive using the ADMIN SETTINGS BACKUP command. This will save the data to be transferred to version 2.0, I then installed the new software to a new SSD with the original 2.0 flash drive from tormach. This flashes the system with the original Tormach data and bit file.
I then added the all of the modified Novakon files to the mill directory and the Torus bit file to the mesa directory. We are still working on version 2.0. I also deleted the 1100-3 ini file. The Novakon modified files will generate a new 1100-3 file pointing to the Torus bit file in the Mesa directory. After restart the system flashed the Torus bit file and the system was functional, I then restored the backed up data by using the ADMIN SETTINGS RESTORE command. The tool data was back and remained after restart. .
I then update the system with the 2.0.4 update and performed the necessary changes for the Torus pro as identified above. The tool table remains and so far no problems. Thus (hopefully) the end of this less than great adventure.
I'll add the files I used just to complete this entry. I did not generate these files and actually copied them from here. Use at your own risk. I can't recall the programmers of the modified files but all I can say is you guys rock!!!
Many thanks again.
Bill

I am curious if your tool table problem will resurface if you update to 2.1.5?

Hey Steve;
Yes, I did have 2.1.5 installed and the same problem was there. There is a mistake in my above post as listed, the change to 2.1.X with the new 1000 tool table is where the problem exists at least with my configuration. So, 2.1.5 did not work for me.
Also as a side note, with the installation of the above files, my spindle was reversed with the 2.0.4 software. I had to modify the HAL file to correct this. But so far, everything else is fine.
Bill