Hello Guest it is March 28, 2024, 08:21:23 AM

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.


Topics - tagrace

Pages: 1
1
General Mach Discussion / Feed rate after tool change problem
« on: September 19, 2008, 07:23:31 PM »
Hi gang. I've been pretty quite here for a long time but I think I have found a bug.

It's not a big deal and it's an easy code fix. I use Sheetcam to generate almost all of my gcode. Sheetcam's Mach post jams an F1 into the init code. Les says it's to keep Mach quite during the init. Don't really know what that means.

Anyway, The F1 comes before the tool change. When run, the mill goes to the tool change location and waits. On continue the next move, which is a G00 to some location, the mill runs at F1 speed like it was a G01 move.

I think it has been like this forever. It still does it in the latest dev version as well. I have just gotten into the habit of changing that F1 to F50 in the editor each time I load a file.

Am I missing something or doing something wrong?

Thanks.

Ted

2
I'm working on a project and in my initial testing I am seeing some problems with running macros repetitively.

Here's what I have,
 M90001.m1s
  code "G31 z-10 f35"
  while IsMoving
  wend
  code "M3"
  code "G0Z1"

 M90002.m1s
  code "g31 z-10 f35"
  while IsMoving
  wend
  code "M5"
  code "G0Z1"

In my tap file I setup this test

M90001
g0y1
M90002
g0y0
m30

Note, the spindle command are controlling a vacuum pickup nozzle. The test is supposed to pick up an object whit the vacuum, move to the y1 location and drop the object.

This whole process runs perfectly each time I hit Cycle Start

BUT, as a test, I set up multipass for 100 repetitions to test my just completed digitize probe. It runs fine for a few iterations. Then the motors start making more and more noise. After about 6 iterations the motors ar grinding and an start to lock up.

If I hit Estop, reset, restart, it repeats this process each time. Runs fine and then  starts to grind.

Whats going on? My guess is that the PC is spending more and more resources opening and closing the Macro files robbing time from Mach3.

Anyone seen anything like this before? Would I be better of putting the scripts into buttons where disk access would not be involved?

Any Ideas?

Ted

Pages: 1