Hello Guest it is March 29, 2024, 04:41:20 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 - Ya-Nvr-No

241
Mach4 General Discussion / Re: Screen Set Ideas
« on: October 04, 2014, 03:07:32 PM »
With Arts fine Darwin upgrades I now have the ability to have up to three MPG encoders to either control separate axis's with each or map one per dial.

Using the slider I can assign an encoder/MPG to an axis, so encoder 1 = Y encoder 2 = Z and encoder 3 = B

or using the buttons below Each MPG will be mapped to each axis selected

Max selection is three and that seems like enough to keep track of ;D

My intentions is to be able to replace the hand dials on one of my mills with mpg dials

242
Mach4 General Discussion / Re: Read write to a DRO ??
« on: September 23, 2014, 02:22:20 PM »
looks like your not one to read all the fine details I and others have posted, lol

http://www.machsupport.com/forum/index.php/topic,27162.msg191822.html#msg191822


but you might also try a adding a     -e   to the end of the autoload  it goes into the edit mode first.

C:\Mach4Hobby1953\Mach4GUI.exe /p Mach4Mill -e

243
Mach4 General Discussion / Re: Mach 4 Feature Request
« on: September 22, 2014, 05:16:09 PM »
Its been over a week and I have been very surprised that this was the first IMTS has been mentioned.

I did not want to be the first, as wasn't sure it was my place. But have to agree with Steve. Machmotion had a strong presence  and some impressive setups and showings. I would advise if anyone is looking at upgrading to Mach4 and also a control upgrade to look seriously at Machmotion as their connection with Artsoft is very strong and you should have a good, to great transition.  Very professional and willing to help in any way.

Their screenset was very impressive (thou, at the time lacked a 4th axis). I'm sure by the first of the next year they will have a sweet system available.

 :D and no I'm not their spokesmen, just an outside observer.

244
Mach4 General Discussion / Re: Screen Set Ideas
« on: September 21, 2014, 03:46:00 PM »
Finally found some time to get the Tool pocket tracking routine working.  ;D
Note: then I found I did not like it and changed it.


245
Mach4 General Discussion / Re: Screen Set Ideas
« on: September 18, 2014, 08:43:15 PM »
pull the Key/Name from the GetProfile calls, then set the name to a text control on your screen.

Sorry but, that was Clear as mud!

I had this posted somewhere but can't seem to find it

I'd created a text label, and put this in my plc script

ScrName = mc.mcProfileGetString(inst,'Preferences','Screen',ScreenName);  --gets the Screenset name from the machine.ini file Preferences section.
scr.SetProperty('lblScreenName', 'Label', ScrName); -- then put the ScrName in the text label called lblScreenName

246
Share Your GCode / Re: need help please...
« on: September 13, 2014, 07:53:02 PM »
based on your web page I see your a programmer.
All you have to do is compute the tangent points of contact at the radius and depth of position. Then circular interpolate the profile.
Figure out your chip load based on material and speeds then you should be able to create a spread sheet to pump out the code.
It's just math, not hard, just tedious.
just have to make sure the cutter you choose will reach the full diameter without the shank hitting and long enough to get to the bottom.

That hole will need to be flushed out during the cut as it will pack up fast. And several roughing passes would be advised as those cutters are not made for heavy loads. Might be better to use the center of the sphere as a separate offset so you can call it 0,0,0 then you can use the scaling features of mach3 and using the finish routine just scale it down for the roughing passes. So reference all dimensions from the center of the sphere

I advise, go slow and a use a good rigid setup, have fun

the blue lines are the tangent angle back to the center of the cutter ball.


247
Mach4 General Discussion / Re: Screen Set Ideas
« on: September 07, 2014, 07:38:06 PM »
Managed to get the tool use timers working, works by adding only feed move times for the current tool number. Then stores the time to a pound variable and also compares it to the used up time variable. Watches the incycle for starting the timers and looks at either no feed move or an out of cycle condition.

Update: Made a few revisions, changed the saved times to minutes and formatted.

248
Mach4 General Discussion / Re: Screen Set Ideas
« on: September 05, 2014, 05:22:28 PM »
I was playing around with adding timers to my tool sheet, and created a little script that I put in the plc script (at the end) to show me the what current modes I am in.
I needed to find a way to make sure the Tool timer only tracked cut/feed times. So during a run cycle the history gets updated with the current G codes. Helped me in seeing how gcodes are tracked and used.

Code: [Select]
local inst = mc.mcGetInstance();

if (inCycle == 1) then 
    mode1 = mc.mcCtrlGetModalGroup(inst,1,'0')
    mc.mcCntlSetLastError(inst, "mode1 = G" .. tostring(mode1));
    mode2 = mc.mcCtrlGetModalGroup(inst,2,'0')
    mc.mcCntlSetLastError(inst, "mode2 = G" .. tostring(mode2));
    mode3 = mc.mcCtrlGetModalGroup(inst,3,'0')
    mc.mcCntlSetLastError(inst, "mode3 = G" .. tostring(mode3));
    mode4 = mc.mcCtrlGetModalGroup(inst,4,'0')
    mc.mcCntlSetLastError(inst, "mode4 = G" .. tostring(mode4));
    mode5 = mc.mcCtrlGetModalGroup(inst,5,'0')
    mc.mcCntlSetLastError(inst, "mode5 = G" .. tostring(mode5));
    mode6 = mc.mcCtrlGetModalGroup(inst,6,'0')
    mc.mcCntlSetLastError(inst, "mode6 = G" .. tostring(mode6));
    mode7 = mc.mcCtrlGetModalGroup(inst,7,'0')
    mc.mcCntlSetLastError(inst, "mode7 = G" .. tostring(mode7));
    mode8 = mc.mcCtrlGetModalGroup(inst,8,'0')
    mc.mcCntlSetLastError(inst, "mode8 = G" .. tostring(mode8));
    mode9 = mc.mcCtrlGetModalGroup(inst,9,'0')
    mc.mcCntlSetLastError(inst, "mode9 = G" .. tostring(mode9));
    mode10 = mc.mcCtrlGetModalGroup(inst,10,'0')
    mc.mcCntlSetLastError(inst, "mode10 = G" .. tostring(mode10));
    mode11 = mc.mcCtrlGetModalGroup(inst,11,'0')
    mc.mcCntlSetLastError(inst, "mode11 = G" .. tostring(mode11));
    mode12 = mc.mcCtrlGetModalGroup(inst,12,'0')
    mc.mcCntlSetLastError(inst, "mode12 = G" .. tostring(mode12));
    mode13 = mc.mcCtrlGetModalGroup(inst,13,'0')
    mc.mcCntlSetLastError(inst, "mode13 = G" .. tostring(mode13));
    mode14 = mc.mcCtrlGetModalGroup(inst,14,'0')
    mc.mcCntlSetLastError(inst, "mode14 = G" .. tostring(mode14));
    mode15 = mc.mcCtrlGetModalGroup(inst,15,'0')
    mc.mcCntlSetLastError(inst, "mode15 = G" .. tostring(mode15));
end

249
Mach4 General Discussion / Re: Screen Set Ideas
« on: September 04, 2014, 12:17:29 PM »
Had some luck with Freeman's Panel Scripting Code and Scott's Cool additions but had to make a couple of changes to get it to Scale and Stretch correctly for me.
works pretty good right to left but top to bottom its off a bit in stand alone mode,
but when embedded it needed tweaking to get it to work right. (framing was taking over I believe)

Sorry I'm not much on those message boxes, seem to be a distraction to me. (Maybe a timer to close would make it more functional and make me happier?)  ;D



250
Mach4 General Discussion / Re: Screen Set Ideas
« on: September 03, 2014, 07:44:38 PM »
I do like the square better