There is a lot of stuff in this thread, and I do not immediately have all of the answers. Some things that I can add, though:
1. The Eggbot Control extension does have a facility for adapting to the 1600 step/revolution resolution: Add a new, empty file in the directory called “motor1600”, and it will make that switch. Look in the code for how that works, and it should be straightforward to use that code to instead adapt it to work at 6400 step/revolution resolution. This one scaling factor should (hopefully) take care of most of the “hard coding” problems that you are describing.
2. The 1000 speed limit has never been a problem before, since the Eggbot does not generally work nearly that fast. An actual bug is that you should not be able to set the input value to 10,000, but instead to 1000 max.
3. The WaterColorBot extensions for Inkscape use much of the same code, but with a little more flexibility and fewer hard-coded values. It uses an external configuration file “wcb_conf.py” where you can set some of those numbers like DPI and relative speed scale. You may want to look at it for additional examples.
4. We did come up against the 1000 speed limit in the WaterColorBot code, and fixed it as follows:
Eggbot code:
nTime = int( math.ceil( 1000 / self.fSpeed * distance( self.nDeltaX, self.nDeltaY )))
WaterColorBot code:
nTime = 10000.00 / self.fSpeed * distance( nDeltaX, nDeltaY )
nTime = int( math.ceil(nTime / 10.0))
nTime = int( math.ceil(nTime / 10.0))
