I also looked at the numbers you provided and don't find any obvious typos.
I made a spread sheet to better visualize the data and that leads me to a recommendation.
It seems that you have chosen a FEED (.815) which, when divided by the STARTS (7) results in a PITCH (FEED/STARTS) 15 decimal places long (0.1164285714285710).
When you round that number to four decimal places (0.1164), times 7 starts, you get 0.8148, which is .0002 short of your FEED (.815).
That resulted in using Z offsets that are not exactly equal to the FEED/STARTS. You also added 0.0001 to the Z offsets between starts 2 and 3, also between starts 6 and 7. I don't know if any of those small numerical complexities and anomalies matter, however we are searching for the unknown factor, so below is my recommendation.
Instead of choosing a FEED number, calculate the FEED by choosing a PITCH (peak to peak, up to 4 decimal places) and multiply it by the STARTS.
That way, all the increments between STARTS are precisely equal and defined to 4 decimal places (no 15 decimal place numbers).
In the attached spreadsheet, I showed the numbers, in a way that I can absorb (so I hope it's helpful to others). Also, in there is everything you need to calculate the FEED and Z offset STARTs for a 7 start thread plus another for a 9 start thread. All you have to do is enter two desired values. In the yellow cells, enter PITCH and START 1 Z. The FEED and remaining Z offset values will be calculated for you (all precisely defined to 4 decimal places with no remainders).
If you don't have or uses Excel, let us know and I'm sure somebody here can get the spreadsheet into Google Docs(?). The spreadsheet is dead simple to use (insignificant learning curve compared to trouble shooting the thread problem).
Crap! The forum won't let me attach an Excel worksheet. I suspect it's because of no permission for a non-dues-paying slug like me.
Somebody (a paying member) PM me an email address and I will email the spreadsheet to you. Please post it for the benefit (I hope) of all.