Hello Guest it is March 19, 2024, 07:22:15 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 - jevs

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 »
41
I cannot figure out what this is doing. I don't know what that 16 is on the end and I cannot find documentation for it.

This pops up a message box with a selection of "Ok" and "Cancel"

local MyChoice = wx.wxMessageBox("Click Ok to Begin Probing the New Tool","Click OK to continue" , 16)

The problem is if you pick "Cancel" it does the same thing as "Ok" and continues on with the code below it. I need cancel to end the operation. Without any info
I cannot decipher what is going on here without knowing what that 16 does. I assume it is a choice of what to do from some list that I have no idea of.....

42
So, this is interesting.
Before I had my Overshoot amount set to .005" (for no other reason than it sounded reasonable and wouldn't hurt the probe).

After I would run the calibration I would always get something like this:
"Auto tool setting complete, Offset = 1.0019"

The 1" seems to be programmed in as a default (which makes no sense to me), but I was never sure why I was getting some number just higher than 1"

I set my probe overshoot to 0.000 and ran it again.
Now I get "Auto tool setting complete, Offset = 1.0000"

Is this what I should be getting and possibly that zero calculation above was correct?

Slightly off topic, but related, why is my TLO for Tool 1 (the probe) set to 1" anyway??


43
Oh, to throw another wrench in this. My Z axis has a brake on it that is controlled by the servo drive.
How do you account for that? The X and Y do not have a brake, but the bed mill is heavy. Will handle a 300 lb work piece according to the old manual.

44
How would anyone know they are supposed to calculate all of this out with the given documentation?
My machine runs in inches, so this is not really working out for me.

My Acceleration Units/(Sec^2) is 50.00 (from the motors setup screen).

so,
d=1/2*a*t^2
d=1/2*50*t^2

My "Slow measure feedrate" is 5.0 and I am not positive what units these are?? inches per minute? inches/Sec^2 ??
So,
t=5/50
t=0.1

So,
d=1/2*50*.1^2
d=0.25

This cannot be right? Quarter inch of over travel would break my probe likely.

This all makes no sense to me. Something is not converting correctly for me here. Mismatch in units or something. 

I understand why this is Mach4 hobby. Your entire hobby becomes figuring out how to work it instead of using your machine :(

If I convert my "Slow measure feedrate" of 5.0 and assume it is inches/minute to inches/second (0.0833333), the math comes out like this...

t=0.0833333/50
t=0.0016666

d=1/2*50*0.0016666^2
d=0.000069438889

This is basically setting my overshoot to zero.....does this sound correct??


 

 

45
How do you know what probe "Overshoot amount" should be?

I cannot find anything to tell me what this should be or what it actually does. Is it used in any of the hidden probe calibrations or calculations? Or, is it just saying to travel this much further after the signal is tripped? Why would you need to travel past the point of the probe tripping? Why is this not set to 0?


46
Mach4 General Discussion / Re: Recommendation for VFD Alarm functionality?
« on: September 10, 2019, 10:11:12 PM »
This one is not that smart.

47
Mach4 General Discussion / Re: Recommendation for VFD Alarm functionality?
« on: September 10, 2019, 09:55:34 PM »
Well that was not as simple as I thought it was going to be, but still not bad.
Doing the code above will disable it, however if you hit the enable button it will start working again regardless of the VFD error input condition.
This will not allow allow the machine to be enabled as long as the VFD Alarm relay is open and gives a message so you know why.
Code: [Select]
SigLib = {
[mc.OSIG_MACHINE_ENABLED] = function (state)

-- Check to make sure there is not a VFD error occurring
if (state == 1) then
VFDErrCheck()
end

machEnabled = state;
    ButtonEnable()
end,
Code: [Select]
-- Add VFD Alarm Input
[mc.ISIG_INPUT0] = function (state) -- VFD ALarm N.C. Relay Contacts
VFDErrCheck() --runs this if Input 0 state ever changes (no "if")
end,
Code: [Select]
-- Check if VFD Error is occurring before allowing Enable
function VFDErrCheck()
local hSig, rc = mc.mcSignalGetHandle(inst, mc.ISIG_INPUT0)
local sigState, rc = mc.mcSignalGetState(hSig)

if (sigState == 1) then
rc = mc.mcCntlEStop(inst)
rc = mc.mcCntlSetLastError(inst, "VFD Error - Machine Disabled")
end
end


48
Mach4 General Discussion / Re: Recommendation for VFD Alarm functionality?
« on: September 10, 2019, 02:35:44 PM »
Thanks. That is what I will do. However, now you offer up a couple other options with the cycle stop, feed hold, or e-stop. Is there one that is more preferred than others or a general way most oem non Mach controlled machines handle a VFD alarm?

49
Mach4 General Discussion / Recommendation for VFD Alarm functionality?
« on: September 10, 2019, 11:48:50 AM »
I am not finding much info on utilizing a VFD alarm with Mach4.

Is it "standard" to just have this hooked to an input and program it to create an E-Stop and pop up a message if one occurs, or is there a better way to utilize this?

Anyone have some examples or experience using a VFD alarm with Mach4? I forget exactly what this did with my Mach3 setup (used Machmotion plugin). I know it put up an error message, but I cannot remember what occurred along with the error exactly.

50
So I discovered another little issue that also improved this issue a bit more as well......

Now I only this get at boot up.
-----ESS: Limit Switch triggered on
E-Stop condition!
E-Stop cleared!

You can read about it here:
https://www.machsupport.com/forum/index.php?topic=41757.msg272906#msg272906


Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 »