Hello Guest it is July 10, 2020, 07:38:38 PM

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 - Benjammann

Pages: 1
1
I've been running for the past few weeks with no issue. Now all of the sudden, the same code that worked fine now plunges to machine coordinates at the end of the run when it hits the line of code  "Z-.25" instead of going to the work coordinates. Also I had an issue where it was ignoring my model top height setting and just using the stock top. I did clear that up by restarting my ethernet smooth stepper. Could it be causing the other issue of plunging to machine coordinates?

Thanks
Ben

2
I'm trying to make a screen that I can switch to that is entirely just a tool path view, but all the tabs in the current default screen set leave the other controls at the bottom. How can I keep this layout, but be able to switch to a full screen view of the toolpath?

3
Mach4 General Discussion / SmoothStepper Motor Steps Per Unit
« on: January 12, 2019, 07:35:21 PM »
I'm running a SmoothStepper ESS with a Gecko breakout board. I'm having to set my nema 23 motor steps per unit to 40000 to get correct travel. Is this common? Seems high.

4
Hello,

  I'm having a strange issue where my Z will reset itself to be a few inches below what I set it to. It does not do this all the time, but very often. I set my X and Y, then Z. I leave the mill at Z zero and hit run. Due to the post processor I am using, the arbor then moves up and forward expecting a tool change, which i just skip though and then it goes and hovers to what I think is the retract plane I set in fusion 360, usually .6" above the part, until I hit run again and it finally starts cutting. Very often though it does not stop and hover, but somehow it keeps setting the z to be a few inches below the part, and it tries to plunge itself down into the table. I can usually catch it, just very frustrating. I have to stop, reset zero, then it will work usually.

I'm starting to think this might be some sort of conflict with my post processor and how I have the retract and clearance planes set up in Fusion 360. I don't think it's missing steps. Ive tuned my motors well.

Anyone have any ideas? Ive attached my post processor that shows the starting moves it's doing.

Thanks,
Ben

5
I finally got a triple edge finder and wired it up (somehow) correctly on the first try. (I think)

Then I got the hoss screenset which replaces the tool offset screen with the automated edge finder buttons.

When I try to use one of the routines, the Z axis moves down and touches the plate, then seems to back off a bit, then immediately throws an error that "plate is grounded" and moves into position to do the X edge find and stops.

I can make it go through the whole routine by simulating a Z by touching the plate to the mill then quickly taking it away. Then the error will not be produced and it runs the X Y edge finds.

I'm on a Taig mill using software limits.

It just seems to be doing some sort of double touch where it checks to see if it's grounded and it's still grounded because it just touched off and hasn't cleared out yet.

Any ideas?

Here's the code for the button:

Code: [Select]
Rem Probe Left

XNew = GetDro(0) - 3 'probe to current position - 3 inches
Code "G31 X" &XNew
While IsMoving() 'wait for prob move to complete
Wend
XNew = GetVar(2000) 'read the touch point

Rem move back To the hit point incase there was an overshoot

Code "G90 G0 Z.500"
Code "G90 G0 X" &XNew
Code "G91 X-" &CurrentToolDiameter/2  'moves the probe half the tool diameter to center on edge
       

While IsMoving ()
Wend
        Call SetDro (0,0.000)
        Code "G4 P0.25"
        Code "G91 G0 X-.200 Y1.0"
        Code "G90 G0 Z-.200"
Code "F" &CurrentFeed 'restore original feed rate
End If

Rem VBScript For probing In the Y- direction

If GetOemLed (825) <> 0 Then 'Check to see if the probe is already grounded or faulty
Call ProbeGrounded()
Exit Sub
Else
Code "G4 P1" 'Pause 1 second to give time to position probe plate

CurrentFeed = GetOemDRO(818) 'Get the current feedrate to return to later
Code "F4" 'Slow feedrate to 4 ipm

Rem Probe up

YNew = GetDro(1) - 3 'move to current y position + 3 inches
Code "G31 Y" &YNew
While IsMoving() 'wait for the move to finish
Wend
YNew = GetVar(2001) 'read the touch point

Rem move back To the hit point incase there was an overshoot

        Code "G90 G0 Z.500"
Code "G90 G0 Y" &YNew
        Code "G91 Y-" &CurrentToolDiameter/2  'moves the probe half the tool diameter to center on edge

While IsMoving ()
Wend
        Call SetDro (1,0.000)
        Code "G4 P0.25"
        Code "G90 G0 X0.0"
Code "F" &CurrentFeed 'restore original feed rate
        Code "(X, Y, and Z axis' are now zeroed)"
        Call ReturnG90G91State()
        Exit Sub
End If

Sub ProbeGrounded()
Code "(Probe plate is grounded, check connection and try again)"
Call ReturnG90G91State()
End Sub

Sub ReturnG90G91State()
If CurrentAbsInc = 0 Then 'if G91 was in effect before then return to it
Code "G91"
End If
If CurrentGMode = 0 Then 'if G0 was in effect before then return to it
Code "G0"
End If
End Sub




6
I'm on a Taig Micromill running a custom fusion 360 post processor. When I zero my Z and then hit cycle start, the processor has the Z go up and hit the soft limits for a tool change, then asks to resume, which it usually does so by going down and hovering .6" above the part, then waits for me to cycle start. I am on the latest version of Mach 3 (I hear that an older version works better?) So like 50 percent of the time when the tool goes down to it's .06" hover, it will either stop 2" above the part, seemingly having reset itself to a new Z, or it will try to bury itself into the work.

This issue seems to occur more after I have been working for a while, loading a few different programs, having Mach open for an extended time. If I restart mach, or sometimes the whole PC the Z issue clears up. Also, sometimes after a while when I try to jog my pendant wheel in .001" increments all motion will lock up.

Any ideas? Should I go to the older version of Mach 3?  Also, can I do that if my software is licenced under the person I bought the system from?

Thanks
Ben

Pages: 1