Hello Guest it is September 17, 2019, 07:39:24 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 - howling60

Pages: 1 2 3 »
1
General Mach Discussion / Re: Pause LED does not work...
« on: May 24, 2007, 12:39:37 PM »
i'm glad i'm not the only one that has run into that... i thought i was just unable to find the data anywhere!

My solution, was to put some script in the "feedhold" button, that activated a user LED, an output for external indicators, and then it "presses" the feedhold button...

I haven't actually run this on my machine yet, as i have other priorities right now, but... might be a thought for you!

*edit*  The manual for M3, is MOSTLY the M2 manual, but refer to the customization wiki from the artsoft main page for your current LED's, Buttons, OEMcodes/etc.. they (and some of the functions that work with them) have been changed in the mach versions, and even within the M3 versions...

-Nate

2
General Mach Discussion / Re: feedrate override & "jerky" motion??
« on: May 22, 2007, 08:25:50 AM »
aHA!   i thought i had read something about that earlier..  but after sifting through so many posts...  i just couldn't remember anymroe..

I'll give it a go!  Thanks!

3
General Mach Discussion / feedrate override & "jerky" motion??
« on: May 21, 2007, 02:46:19 PM »
so, here is my situation..  running a 3-axis gantry (with X & A axis slaved for the gantry) router...   I have rapids set at 6_ _ IPM on my Y-axis, and about 300 in my Z-axis.

I am cutting a convex contour in the Y-Z axis, and then an 1/8 stepover in the X... in foam (think blue house insulation panels).. many many many short little segments blended together...

I am using an AD DL06 PLC with an analog card to control my feed/speed over-rides.

If I set my feedrates at 500 IPM in the GCode file, I end up with some rather nasty, jerky motion... Ok.. so turn the feedrates down cause we're obviously pushing the envelope for the speeds the machine can be happy at.... So, I turn my feedrate down to 200 IPM using the feedrate over-ride... motion is still jerky... hmmm

I go in my GCode file, and set my feedrate at 200 IPM...  this time when running, the machine has got really smooth motion...  even @ 100% feedrate override..   i turn it down to 100 IPM using the feedrate over-ride, and motion is still smooth (which would make sense.. if it's smooth @ 200,  it's probly gonna be smooth @ 100)...

So, My question is this..  why is the machine behaving any differently when i set my feed @ 200 Vs 500??  the end result is still 200 IPM when the feedrate override is put in.... It's not really a HUGE issue, as i can take care of it by changing my hardcoded feeds.. i'm just curious as to why it's doing this...

any input would be great!

BTW.. eagerly anticipating Quantum on this machine.. it would be the bomb diggity for what we're doing :) :)

4
My problem is such.. Used the VB editor within Mach to edit... which is frustrating enough, as it is not saving reliably.... ugh..
using the "play" button in the editor, checks out fine.. works fine..  everything SEEMED to work fine yesterday when i wrote all this, but now i'm getting an error "error on line 84--internal error <homeit>"
This corresponds to the "getoemled(800)" line within the "homeit" sub...

also getting an error on Line 88... corresponds to "msgbox........" line

this code is contained within the "reset" button, and I'm using it to do maintenance prompts, and a "must home before running" lockout...
anybody have any thoughts/suggestions?
Thanks in advance!!

*edit* running mach Version R2.0.061  on the laptop being used for testing anyway.

'*************************************************************
'*************************************************************
'Purpose:
'Every Monday, when the Machine is brought out of a "reset" state, a prompt is initiated to grease
'the machine.  A Maintenance Log is created/appended with a time/date stamp, and an Operators Name.
'If the Date Stamp is the same as the last stamp in the maintenance file, the maintenance request is ignored.
'
'The state of the machine is checked upon coming out of The reset, and in conjunction with the "ref home" and "cycle start"
'buttons, a "HOME" action is forced prior to running ANY GCode Files.
'*************************************************************
'*************************************************************
Sub Main()

   Call Maintreminder()   'determine if maintenance is required & take care of process if necessary



   Call Homeit()      'Warn about homing after reset & prevent Gcode runs



End Sub

'**************************************************************
'**************************************************************
'* Subroutine: Maintreminder
'* Purpose: create a maintenance reminder prompt every Monday upon Resetting the machine
'* Programmer: Nathan Haskell
'* Date: 5-17-07
'***************************************************************

Sub Maintreminder()
Today = Date ()                  'Obtain Current Date
   DOW = Weekday (Today)               'Calculate Day Of Week (1-7)
   Clk = Time()                'Obtain Time Of Day
   
   Open "Maintenance.txt" For Input As #1         'Search Maintenance Log for last
   Do While Not EOF (1)               'Maintenance Occurance
   Line Input #1, Lastline
   Loop
   Close #1
   
   LastMaint = DateValue(Lastline)
   
   If DOW = 2 Then               'Check to see if Today is Monday
      If Today = LastMaint Then         'And compare against the last Maintenance Log
      Exit Sub               'If the last Maintenance Log was from Today, ignore
      Else
                        'Otherwise, Perform Maintenance Routine!
      Begin Dialog Maintdlg1 60,60, 200,70, "Maintenance Required!"
      TEXT 60,10,90, 12, "Machine Must Be Greased"
      TEXT 10,24, 50,12, "Operator Name"
      TEXTBOX 60, 22, 108, 12,.nameStr
      OKBUTTON 80, 54, 40, 12,.okbtn
      End Dialog
   
           '* display the dialogbox for operator name input until a valid name (aka, anything starting with A or greater) is displayed... 
           '* Also continue to display until the "OK" button is pressed, to eliminate just clicking out of it... 
           
      Dim Maintbox As Maintdlg1                 
      Do
         Do
         Dialog Maintbox
         Loop Until Maintbox.nameStr >="A"
      Loop Until Maintbox.okbtn=-1

      MsgBox "Thank you " & Maintbox.nameStr & "!"
   
      Open "Maintenance.txt" For Append As #1
      Print #1, " "
      Print #1, "Greased at "  & Clk & " By " & Maintbox.nameStr
      Print #1, Today
      Close #1
      End If
   End If

End Sub

'******************************************************
'******************************************************
Sub Homeit()
   If GetOEMLED (800) = false Then               'If Placing into a Reset, then just reset
   DoOEMButton (1021)
   Exit Sub
   Else                        'Otherwise, Call the message box, then reset
   MsgBox "Machine Must Be Homed After Startup Or A Reset"
   DoOEMButton (1021)
   End If
End Sub
 


5
General Mach Discussion / Re: Homing indicators
« on: May 17, 2007, 10:39:10 AM »
haha.. i do I do..

you are aware you're speaking to one of the original "but if i can accomplish it with less work... why do extra?" people, right? :)

6
General Mach Discussion / Re: Homing indicators
« on: May 17, 2007, 10:27:00 AM »
thanks brian,

wasn't looking for full code, just wondering what the mental path had been on why the Y-axis was the only one that was checked.

either way,

Thanks!

-nate

7
General Mach Discussion / Homing indicators
« on: May 17, 2007, 09:48:08 AM »
I have been reading through the various "how to make sure my machine is homed after startup" threads,
and have a question... why is it that in each code example that has been posted, LED 808 (Y axis ref) is checked to make sure the machine has been homed?  As opposed to checking all the valid axis in the machine anyway...

Just trying to understand the mental paths behind the code that is being put up for use/examples.

Thank you all!

-Nate

8
General Mach Discussion / Re: homing not zeroing axis?
« on: May 17, 2007, 08:29:44 AM »
we can most likely do that!

speaking of what we're making..  started on those *other* foam cores yesterday.. talk about entrancing to watch!  found myself leaning closer and closer with some drool hanging out of the corner of my mouth  :P

-nate

9
General Mach Discussion / Re: homing not zeroing axis?
« on: May 16, 2007, 03:31:25 PM »
Please check that the machine coordinates are set to zero. It will not zero the fixture offset on homing.
Thanks
Brian
 

it was in machine coordinates, and i did double-check with the "machine coordinates" button below the DRO's...   I will have to check the "auto zero" in the homing screen...  i don't know how/when that might have gotten changed, but it is very possible...

btw, thanks for the assistance on the machine yesterday Brian.. much appreciated...  it's been up & running the better part of the day, making dust outta foam :)

-nate

10
General Mach Discussion / Re: homing not zeroing axis?
« on: May 16, 2007, 03:29:28 PM »
you know, i didn't.. but i will!

Hello Nate

Did you check the home/limit page for the auto zero?

Rick

Pages: 1 2 3 »