Messages

1701

General Mach Discussion / Re: Z speed limiting xy speed

« on: February 19, 2018, 01:05:48 PM »

Hi,
steps per mm and Speed is one thing,
acceleration is an other Point.

i don't know the dimensions of your machine, but i would start with some test's
by entering command into mdi.

for example:

F500
G1 X500 -> measure the needed time

 F500
G1 Y500 -> measure the needed time

F500
G1 X500 Y500 -> measure the needed time

just to make sure not one of the 'major' axis are making the Limit.

then

F500
G1 X500 Y500 Z5 -> measure the needed time

to get a 'feeling' what is 'pushing' the brake.

Thomas
 

1702

CS-Lab / Re: No motor Movement

« on: February 19, 2018, 11:13:46 AM »

what i don't understand:

if
-e-stop is ok
-jog mode is on
-cslab is comunicating with mach

axis dro's should Change if you jog, even if Motor Drivers does nothing.

maybe someone else has got an idea.

Thomas

1703

CS-Lab / Re: No motor Movement

« on: February 19, 2018, 09:30:29 AM »

i mean this Jog on.

sorry asking this, but i am wondering that you don't see axis dro changing.

1704

CS-Lab / Re: No motor Movement

« on: February 19, 2018, 08:58:24 AM »

but e-stop is ok? (reset on 1024 screenset ist green)

1705

CS-Lab / Re: No motor Movement

« on: February 19, 2018, 08:45:11 AM »

Mach 3. Yes jog is turned on. I hit the tab button. Mpg is selecting the correct axis and cycling through the increment selection as it should. Thanks for the input though.

and if you use the Keyboard arrow key's?

1706

CS-Lab / Re: No motor Movement

« on: February 19, 2018, 08:43:49 AM »

Its my understanding that the ENable pins do not have to be wired, but I could be wrong.

if i have a look to Manual of 4042 drive the enable is required.

1707

CS-Lab / Re: No motor Movement

« on: February 19, 2018, 02:11:42 AM »

i assume you are using Mach3.

silly question - jog is turend ON ?

1708

General Mach Discussion / Re: Scripter Compile Error bites again :(

« on: February 19, 2018, 01:52:05 AM »

Hi Dave,

i had the same Thing a couple of years ago, well without the self Fixing after 45 minutes.

the only Thing i noticed, when i watched my M3 macro with a HEX Editor was,
that the EOF() was directly behind the ")" of the DoSpinCW().

All i did was to put a couple of 'empty' lines (CRLF) after the DoSpinCW().

The Problem never came up again.

i really can't tel you wether it was

-coincidence
-woodoo
-or just luck.

Thomas
 

1709

General Mach Discussion / Re: macro for turret for boxford tcl

« on: February 18, 2018, 05:09:37 AM »

hey thats a macro for a boxford 125 i have written some time ago for an other guy here.
sorry it is in german, but with a Little Google translator you should be able to understand it.

Code: [Select]


' TPS 29.01.2018 Version 1.0
' BOXFORD 125TCL
' 8 Positionen Werkzeugwechsler mit A-Achse

Sub Main()

  Dim newtool As Integer
  Dim acttool As Integer
  Dim grad_pro_tool As Integer
  Dim grad_nach_pin As Integer
  Dim grad_rueckwaerts as Integer
  Dim Anzahl_Takte As Integer
  Dim Dist_schnell As Double
  Dim F_fast As Integer
  Dim F_slow As Integer

If IsLoading() Then
'wenn ein neues File geladen wird nichts tun
' Exit Sub
Else

grad_pro_tool = 45 ' Distanz für einen Werkzeugschritt
grad_nach_pin = 10 ' freifahren Pin
grad_rueckwaerts = 25 ' zurückfahren an Pin
f_fast = 4000 ' Speed drehen schnell
f_slow = 2000 ' Speed rückwärts gegen Pin

newtool = GetSelectedTool() ' die neue Werkzeugnummer holen
acttool = GetCurrentTool() ' die aktuelle Werkzeugnummer holen

'lass uns ein paar Basic's checken

' neues und altes Werkzeug = 0
If ((newtool = 0) and (acttool = 0)) Then
message("neues und altes Werkzeug = 0 -> nicht's tun")
Sleep(500)
Exit Sub
End If

' neues Werkzeug = 0
If (newtool = 0) Then
message("neues Werkzeug = 0 -> nicht's tun")
Sleep(500)
Exit Sub
End If

' neues und altes Werkzeug sind gleich
If newtool = acttool Then
message("neues und altes Werkzeug sind gleich -> nicht's tun!")
Sleep(500)
Exit Sub
End If
 
  'Werkzeugnummer gültig ?
If  (((newtool > 8) Or (newtool < 1)) and (newtool <> 0)) Then
DoButton(3)
Sleep(500)
Message (" Werkzeugnummer " & newtool & " nicht im Bereich (1-8). Abbruch ! ")
Exit Sub
End If

'X-Achse nicht referenziert
If GetOEMLED(807) Then
DoButton(3)
Sleep(500)
Message ("X-Achse nicht referenziert -> Abbruch !!")
Exit Sub
End If

'Z-Achse nicht referenziert
If GetOEMLED(809) Then
DoButton(3)
Sleep(500)
Message ("Z-Achse nicht referenziert -> Abbruch !!")
Exit Sub
End If

'jetzt geht's los
Message "Werkzeugwechsel von: " +CStr(acttool) + " nach: " + CStr(newtool)

'Anzahl der Takte zwischen den Werkzeugen berechnen
If newtool > acttool Then Anzahl_Takte = newtool - acttool  
If newtool < acttool Then Anzahl_Takte = 8 - acttool+newtool
    
'Distantz in Schritte umrechnen
Dist_schnell = (Anzahl_Takte * grad_pro_tool) + grad_nach_pin

msgbox("Takte: " + cstr(Anzahl_Takte) + " Distanz schnell: " + Cstr(Dist_schnell))

Message "Wechsel X-Achse freifahren"
Code "G90 G53 G0 X2"
While IsMoving()
Sleep(15)
Wend

Message "Wechsel Z-Achse freifahren"
Code "G90 G53 G0 Z2"
While IsMoving()
Sleep(15)
Wend

'A-Achse nullen
Code "G92 A0"
'incremental Mode , Einheiten pro Minute , Exakter Stop
Code "G91 G94 G61"

'A-Achse plus schnell
Message "A-Achse plus schnell zum neuen Werkzeug"
Code "G01 A" & Dist_schnell & "F" & f_fast
While IsMoving()
Sleep(15)
Wend

'A-Achse langsam zurückfahren
Message "A-Achse zurueck langsam zum Pin"
Code "G01 A-" & grad_rueckwaerts &  "F" & f_slow
While IsMoving()
Sleep(15)
Wend

'neues Werkzeug im System anmelden
SetCurrentTool(newtool)

'wieder auf Absolutmodus schalten
Code "G90" ' back to absolute movement

Message ""
End If

End Sub              




1710

General Mach Discussion / Re: MACH3PLASMA LIMIT SWITCHES FOR G540/PROMA

« on: February 17, 2018, 02:57:57 AM »

My G540 board crashed and I’m working on getting that fixed.

when i read this, an the other "strange" things witch are Happening,
have you thought about noise , grounding , shielding ?

just a thinking.

Thomas