Hello Guest it is December 02, 2020, 05:31:43 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.


Messages - TPS

941
General Mach Discussion / Re: DRO question
« on: October 01, 2018, 01:41:56 PM »
i think you have to read a Little bit about machine coordinates and work coordinates.

machine coordinates will only be set to Zero by doing a reference with reference Switches.

942
CS-Lab / Re: Completely lost with my CSMIO IP-m 4
« on: September 29, 2018, 03:27:00 AM »
if you use the CS-Lab email

office@cs-lab.eu

and ask for

Wojtek Trawicki

you normaly get a good Support.
i got allways an answer within two days.

943
can you post your G-Code ?

944
if you go to the settins page , right lower Corner, does it Show mm's or Inch ?

945
General Mach Discussion / Re: Macro in G-code pauses execution for 1 sec
« on: September 28, 2018, 02:03:36 AM »
or contact vital Systems customer Support?

946
General Mach Discussion / Re: Macro in G-code pauses execution for 1 sec
« on: September 27, 2018, 02:43:42 PM »
if you Show us your M29 macro, somebody will be able to help you.

947
something like this should work:

If IsActive(INPUT1) and (GetUserLed(2000) = false) Then
 SetOEMDro(2000,GetOEMDro(2000)+1)
End If

If IsActive(INPUT1)  Then
 SetUserLed(2000,1)
Else
 SetUserLed(2000,0)
End If

not tested, just written down

948
VB and the development of wizards / Re: macro for adjusting jog speed
« on: September 15, 2018, 02:56:00 AM »
there must be something else in your macro witch causes the Compiler error.

if i run

Call SetOemDro(3,2)

here it works fine, make sure that there is a CRLF at the end of the line.

949
create am macro, lets say M1000.M1s

code of the probemacro can be something like this:
Code: [Select]

Sub Main()

'get Parameter ------------------------------------------------------
Tool = Param1()
'--------------------------------------------------------------------------------


'ceck toolnumber----------------------------------------
If ((Tool < 1) or (Tool > 16)) then
    Message ("toolnumber not valid")
    GoTo Ende
End If
'--------------------------------------------------------------------------------

    'load the tool
    Code "M6 T" + cstr(Tool) + " M5"

    '-------------------------------------------------------------------------------- 

' !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
' PUT HERE SOME CODE TO DRIVE TO THE PROPBEPOSITIO
' !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


   
    'do the probing
ZM_in = 100 'max probing distance
    Code "G31 Z100" + CStr(ZM_In) +"F50"
    While IsMoving()
        z = GetOEMDRO(802) 'act Z-pos
        If z <= ZM_In Then
            DoOEMButton(1003) 'Stop if too far
            MsgBox ("probe not hit" )
            GoTo Ende
        End If
    Wend           
   
    'et the probepos
    ZProbePos = GetVar(2002)   


    'put the value into tooltable
    SetToolParam(Tool,2, ZProbePos)
    'save tooltable
    DoOEMButton(316)


' !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
' PUT HERE SOME CODE TO COME OUT OF THE PROBEPOS
' !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    'unload the tool
    Code "M6 T0"



Exit Sub
Ende:
    Code "M30"
    'Message ("error while probing")
   
End Sub




then you can do a probing with

M1000 P1 to probe tool 1 or
M1000 P2 to probe tool 2

the P-Parameter is the toolnumber.

now you can create a smal G-code file, where you can call M1000 for all your Tools.


be Patient, the posted code is not tested and not complete, it is just to give you an idea.









950
CS-Lab / Re: CSMIO-ENC Spindle Orientation
« on: September 02, 2018, 05:56:40 AM »
is your spindle step/dir driven or 0-10V?