Messages

6821

VB and the development of wizards / Re: Time estimation until tool change

« on: May 06, 2010, 12:18:17 AM »

The new WorkLog works with the new TC code.

Sample report:

"5/5/2010.....C:\Mach3\GCode\TestWorkLog.txt, StartTime 11:28:57 PM"
"__________ToolChange  T# 1 ,11:28:58 PM"
"__________ToolChange  T# 2 ,11:29:17 PM"
"__________ToolChange  T# 3 ,11:29:46 PM"
"__________ToolChange  T# 4 ,11:30:05 PM"
"          C:\Mach3\GCode\TestWorkLog.txt..........EndingTime11:30:26 PM"
"5/5/2010.....C:\Mach3\GCode\roadrunner.tap, StartTime 11:31:26 PM"
"__________ToolChange  T# 6 ,11:31:26 PM"
"__________ToolChange  T# 12 ,11:33:57 PM"
"__________ToolChange  T# 0 ,11:37:02 PM"
"          C:\Mach3\GCode\roadrunner.tap..........EndingTime11:37:10 PM"

6822

General Mach Discussion / Re: Mach pushes the motors faster than max speed... and it's not even ashamed of it!

« on: May 05, 2010, 11:48:32 PM »

It could be that you have a multi speed CPU feature where the cpu can slow down and speed up. IF Mach locked in on a lower cpu speed, and then the CPU sped up you might get faster than normal velocities.

Here the CPU runs a touch SLOWER that what mach locked in on SO everything is a touch lower than indicated  10IPM= 9.46IPM

Try rerunning the driver test to see IF it can lock in on the faster speed.

Just a thought

6823

VB and the development of wizards / Re: Time estimation until tool change

« on: May 05, 2010, 04:53:13 PM »

OK it is possible to do a SOSO countdown timer BUT you would need to input each leg or devise a scheme to use #vars in the preamble of your GCode to set #vars with the TC times.

NOW to integrate it into looking at T#s and the M6start macro to do a tool count.

6824

General Mach Discussion / Re: helix toolpath problem...

« on: May 05, 2010, 12:07:28 PM »

Just some thoughts,

 HOW is the gcode being generated? , Arcs or straight segments?

What do you have setup for Look ahead ?  200 works good for basic 3d moves

If small segments then maybe your computer is slow and cannot keep up??

Can you give a code example .

6825

VB and the development of wizards / Re: Time estimation until tool change

« on: May 05, 2010, 11:36:19 AM »

HUM that is a good idea Ian. You could also just look at the TC led to use to trigger the time function as the program ran.

 I think I will ADD that routine to the JOB REPORT function that we run. It might be handy to know the spans between tool changes along with total run time of the job.

Then if really needed you could run a simple countdown routine that you plugged in the span times and it would allow you to see the countdown time LIVE.

You could also add a function to output to a relay so a TC warning alarm could be used say 5min BTC the flashing light/buzzer goes off to alert you to an upcoming TC.

(;-)

6826

VB and the development of wizards / Re: Time estimation until tool change

« on: May 04, 2010, 04:45:59 PM »

I have looked through all my notes and don't have a solution. The only way to know when the next tool change would be is to let mach do an TIME estimate based on the gcode(feedrate * distance) to the next TC  THEN start a countdown timer running, BUT we don't have access to that info(;-).

That would need to be done at a pluin level OR the driver level.

You could use a digital Kitchen timer and set it for each segment?

PS: It is not a new question(;-) that was asked several years back along with a countdown timer for program end.

THERE IS a process that mach does when loading a new program file that checks the code for errors before it loads. THAT would be a place to include the countdown timer calculation process. You would just have to convince Brian that it is a good idea.

6827

General Mach Discussion / Re: edge finding/2.5D probing

« on: May 04, 2010, 09:47:25 AM »

The Pipe was just an example that I could decribe(;-)

The port is probed with a .375" ball on the end of a long probe shaft or sometimes a flat disk on the long shaft. The tip used depends on the port itself. You have to use a tip smaller than the smallest radius. Using a 4th axis machine sometimes you may have to index the port several times to get all the port scanned. 

THERE is no hurry take your time.


In reality the top end of the port is probed based in the centerline and then the head is indexed over to the other end and it is probed on the centerline as well. Then in the drawing the ends are aligned with the centerline. then the shape is converted to a cut file.

The head to be cut is then put into the fixture and indexed into position to cut.

6828

VB and the development of wizards / Re: limits on off in vb code

« on: May 03, 2010, 10:24:58 PM »

Thansk Bill (;-)

6829

VB and the development of wizards / Re: P, Q, R parameter

« on: May 03, 2010, 10:22:58 PM »

Then try the semaphore approach it does seem to work.  Do a search on this forum for semaphore Ray gives and example of how he did it.

6830

General Mach Discussion / Re: edge finding/2.5D probing

« on: May 03, 2010, 06:38:12 PM »

Here is a diagram of the port