Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I can show you how that is done. Very easy!
What can I say I don't get out much LOL
Guest
-- Fit Spindle Speed with linear interpolation
function buildtbl()
rpmtbl = { points = 0,
addPoint = function (self, commandRPM, trueRPM )
self[tonumber(self.points)] = {}
self[tonumber(self.points)].commandRPM = commandRPM
self[tonumber(self.points)].trueRPM = trueRPM
self.points = self.points + 1
end,
linearInterp = function(self, RPM)
local low = -1
local high = -1
for i=0, self.points-1,1 do-- loop through the points and get the high and the low around the requested RPM
if (self[i].commandRPM <= RPM) then
low = i
end
if (self[i].commandRPM >= RPM) then
high = i
break
end
end
--check to see if the point is on the table, if not simply return what was input
if(high == -1 or low == -1)then
return RPM
end
if(high == low) then
return self[low].trueRPM
end
--y = y1 + ((x – x1) / (x2 – x1)) * (y2 – y1)
--time to figure it out!
local NewRPM = self[low].trueRPM + ( (RPM - self[low].commandRPM) / ( self[high].commandRPM -self[low].commandRPM )) * (self[high].trueRPM - self[low].trueRPM )
return NewRPM
end,
}
--To add a point call the addPoint function with the Requested PRM, Than the True RPM (this must be done without this function active)
-- Example Command 500 RPM Spindle is teally going 750
-- The following call would be made rpmtbl:addPoint(500 ,750)
rpmtbl:addPoint(100,10)
rpmtbl:addPoint(200,100)
rpmtbl:addPoint(2000,2500)
rpmtbl:addPoint(3000,5000)
end
function calcRPM(rpm)
-- take the requested RPM and adjust based on the table fitting points
if(rpmtbl == nil) then--build a global table on the first scan
buildtbl()
end
local adjRPM = rpmtbl:linearInterp(101)
end
local SpindleRPM = 2500
local outputRPM = calcRPM(SpindleRPM)
funny enough this is how I made the code for surface mapping and screw mapping. The problem and the users change but the math to solve them stays the same lol. I suspect I could make this code in a few hours or so. Make a deal, if I do this we can post the code here and you tell how to make it work, a white paper is what I would call it. Sound like a plan?
I know it can be fun to try to make the low cost ones work but they can really make you angry trying to set them up.
. Because you didn't have the file it was causing a pointer to go out in memory and stomp on memory! On my PC it will messing with my OpenGL and crashing the machine. Steve found the issue (took days and he is REALLY good) and he patched it up and rebuilt the libs. So next version you should be all good. The latest Dev version has what you need if you want to try it. Wanted everyone to know it was fixed and that you helped to delay release LOL . We have started release testing over AGAIN because of this. The QA part of getting software out takes longer than making the code I think! Mach4 is a MASSIVE project with so many ways to use / customize it that it takes a lot of pokes to see if everything is working as it should.