Hello Guest it is April 26, 2024, 10:54:17 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.


Messages - leversole

Pages: « 1 2 3 4 5 6 7 8 9 10 11 »
11
VB and the development of wizards / Re: Visibility or color property
« on: January 10, 2017, 06:06:16 PM »
Struggling with the LED...

I am using MachScreen and testing on the Aqua screen set...

I created a *.png file 100 px wide with half transparent...when I try to create a new LED, when I choose the image path my file does not show up now matter where I put it, in Mach3\Bitmaps, or even Mach3\Bitmaps\Aqua...it's name is HomeIcon.png (I have attached the image)

If I try to change an existing button, to another *.png in teh same (Aqua) directory, I get an erro message that does not make sense (I amd pulling form the proper directory)...I have attached the error msg.

Any thoughts? I thought I read one time a set of instructions on how to use the two state image LED...cant put my hands on it...but I may be having other issues as noted above.


12
VB and the development of wizards / Re: Visibility or color property
« on: January 09, 2017, 07:49:59 AM »
Thanks...will test it out today...

13
VB and the development of wizards / Re: Visibility or color property
« on: January 09, 2017, 06:59:00 AM »
Thanks Gerry...I often wondered how those half and half buttons work! I guess I will figure it out...it would only appear to be "over" the DRO as the DRO area box background is the same color as the DRO background...

Thanks
Leslie

14
VB and the development of wizards / Visibility or color property
« on: January 08, 2017, 06:03:42 PM »
How can I set/change either the visibility or color of a screen object? I am designing some new screens, and just as an example, I would like to have an LED be invisible (or the background color) until I turn it "on"? Or, I would have a small icon (of a "home" for example), and it would not be visible until the axis is homed?


15
Mach Screens / Re: Key simulators
« on: December 30, 2016, 10:11:20 AM »
Trying to build a string and not working

When I press the first key (clears the msg)

msgtext="" ' clears the variable

msgtext-"G"
SetUserLabel(51, msgtext)

This works, but when I add to the string with the next keypress, it clears the string

Another key...

msgtext=msgtext & "5"  'add the 5 to the string
SetUserLabel(51, msgtext)

In my mind, msgtext should now be "G5", but after pressing both of these keys, I am only getting the 5. is "&" the proper concatenation operator?


Here is my simple keypad







16
Mach Screens / Key simulators
« on: December 30, 2016, 09:02:58 AM »
I think I like tweaking/enhancing my machine and controls as well as I like making parts! (wood signs mostly)...anyway...I am going back to the drawing board on a new screen set...may buy a touch screen, but that will be the general design...will probably emulate the new Haas stuff.
I do not want a full on keyboard, but on my manual operation page, I would like a few keys (G,T,M, etc) and a number pad...what I am looking for for is guidance on how to press one of the keys and place its value in the MDI. I could brute force it by building a string in a variable and maybe script it to make whatever I am doing happen, but it would be way cooler if I could press my buttons and fill out the MDI, then press enter to execute...as I am typing this I suppose I could fake the MDI and use a user label...hmmmm...if anyone has an elegant solution or point me in the right direction I would love to hear it...

Thanks
Leslie

17
VB and the development of wizards / Re: Secondary tool z zero
« on: December 23, 2016, 09:02:15 AM »
Figured out the runscript issue...I assumed that Mach3 knew where the script was based on the profile, but it assumes the root of Mach3...just added the path and it works great!

18
VB and the development of wizards / Re: Secondary tool z zero
« on: December 23, 2016, 12:57:36 AM »
Why wouldn't RunScript do what I wanted?

‘ Run script example
If RunScript(“MsgBoxScript”) < 0 then
 Msgbox “RunScript returned an error”
Else
 Msgbox “Script ran”
End If
Where the file MsgBoxScript.m1s contains
MsgBox “Message from script file”
Will result show a dialog box with the content “Message from script file”.
Followed by a dialog that says “Script Ran”

19
VB and the development of wizards / Re: Secondary tool z zero
« on: December 22, 2016, 07:20:56 PM »
I could really clean up the code and get rid of duplicates if there was a way to call scripts from other scripts can this be done? I can have a script for each of the Z touch off moves and call them when needed, even add the calls to the m6Start routing to make it more automated...

An thoughts? Can you call a script from another script?

Thanks
Leslie

20
VB and the development of wizards / Re: Secondary tool z zero
« on: December 22, 2016, 07:17:45 PM »
I think I have it worked out...simple really (If I am doing it correctly!) just have to grab the remote Z touch value after you set the first tool...then on the next tools, just go remote, probe till it stops, then write the value you got the on the first tool into the Z...I tried to get clever and use the gcode line number to automatically run the correct code...anyway I am posting it for review and comments...



' This routine checks if this is the first time tool change using the current GCode line number
' less than 20 means this is the first tool change
' then it does the correct Z touch off

lnum = GetOEMDro(816)           'Get the current line number in the code window
PlateOffset = GetUserDRO(1151)   'Get plate offset DRO
CurrentFeed = GetOemDRO(818)    'Get the current feedrate to return to later


If lnum < 20 Then ' must be the first one

  If GetOemLed (825) <> 0 Then    'Check to see if the probe is already grounded or faulty
    Code "(Z-Plate is grounded, check connection and try again)" 'this goes in the status bar
  Else
    Code "G4 P1"      'Pause 1 seconds to give time to position probe plate
    Code "F4"         'slow down feedrate to 4 ipm

    'Probe wherever we are
    ZNew = GetDro(2) - 2   'probe move to current z - 2 inches
    Code "G31Z" &ZNew
    While IsMoving()      'wait for probe move to finish
    Wend

    ZNew = GetVar(2002)    'read the touch point
    Code "G0 Z" &ZNew       'move back to hit point incase there was overshoot
    While IsMoving ()
    Wend

    If PlateOffset <> 0 Then
      Call SetDro (2, PlateOffset) 'set the Z axis DRO to  plate thickness
      Code "G4 P0.25"          'Pause for Dro to update.

      'now lets probe at the remote point to get the Z dro offset for subssequent tool changes
      Code "G53F200Z-.1" 'go to a safe Z
      While IsMoving()
      Wend
      CODE "G53F200X0.315Y4.125" 'go to where the remote touch off is
      While IsMoving()
      Wend
      CODE "G53F200Z-2.5"        'come down fast to get us close
      While IsMoving()
      Wend

      MsgBox "Move the touch plate to the remote location. Press okay to continue" ' let the op know
     
      CODE "G31F4Z-2"            'do the probe thing
      While IsMoving()
      Wend

      Code "G4 P1"               'hold on on second for the DRO to update
      tooloffset = GetDro(2)

      SetUserDRO(1205, tooloffset) 'set the Z DRO to the value we got when the initial Z touch was done

      Code "G53F200Z-.1"  'go to a safe Z height
      While IsMoving()
      Wend

      Code "G0X0Y0"       'go back to 0
      
    End If
    Code "F" &CurrentFeed 'Returns to prior feed rate
  End If
Else

  If GetOemLed (825) <> 0 Then       'Check to see if the probe is already grounded or faulty
    Code "(Z-Plate is grounded, check connection and try again)" 'this goes in the status bar if aplicable
  Else
    Code "G4 P1"         'Pause 1 seconds to give time to position probe plate
    PlateOffset = GetUserDRO(1151)   'Get plate offset DRO
    CurrentFeed = GetOemDRO(818)    'Get the current feedrate to return to later
    Code "F4"                  'slow down feedrate to 4 ipm

    Code "G53F200Z-.1"                  'go to a safe Z height
    While IsMoving()
    Wend
    CODE "G53F200X0.315Y4.125"          'go to where the remote touch off is
    While IsMoving()
    Wend
    CODE "G53F200Z-2.5"                 'get close on the Z at a fast rate
    While IsMoving()
    Wend

    MsgBox "Move the touch plate to the remote location. Press okay to continue" ' let the op know

    CODE "G31F4Z-1"         'now lets probe Z
    While IsMoving()
    Wend

    Code "G4 P1"         'give it s second to update
    toolOffset = GetUserDRO(1205)
    Call SetDro (2, toolOffset)      'set the Z DRO to the offsset value we got when we did the first tool

    Code "G53F200Z-.1"         'go to a safe Z height
    While IsMoving()
    Wend

    Code "F" &CurrentFeed       'Returns to prior feed rate

  End If
   
End If

Pages: « 1 2 3 4 5 6 7 8 9 10 11 »