Hello Guest it is January 22, 2022, 07:35:51 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 - mbele

Pages: « 1 2 3 4 5 6 »
41
General Mach Discussion / Re: Button Reprogramming...
« on: April 03, 2014, 09:47:28 AM »
You're right, I've tested it, and it seems that it behaves weird. Anyhow, here's the script that works for me:
SetOEMDRO(800,0)
SetOEMDRO(801,0)
SetOEMDRO(802,0)
It will automaticaly regenerate toolpath.
I think that when DROs are defined as "standard" (codes 0,1,2) path will not be regenerated by default.
(jog follow must be turned on, i think)

42
General Mach Discussion / Re: Button Reprogramming...
« on: April 03, 2014, 08:16:29 AM »
:)
...or click exec code in property editor (in second column), click basic script, and put your code there:
DoOEMButton(1007)
DoOEMButton(160)

43
General Mach Discussion / Re: Button Reprogramming...
« on: April 03, 2014, 04:47:17 AM »
Probably there's no script attached to that button, and the button just executes one preprogramed function.
Check
http://www.kd-dietz.com/klausphp/pages/eng/machscreen/description/ms_description.html
Make backup of your mach instalation, and open screenset file with machscreen. When you select "origin" button, properties edit window will be populated with button properties. Note which function code it executes, then edit the script and execute same function via script, then add your custom code after that. Again that's the concept, but if your pendant is executing mach function, rather then emulating button press, it will not work. In that case, you'll have to find out how mach interprets pendant signals, and change the behavior(mach response) there - sorry, I know nothing about pendants.
Good luck

44
General Mach Discussion / Re: Button Reprogramming...
« on: April 02, 2014, 05:57:42 AM »
- edit button script from mach via menu, or modify screenset with machscreen app
- regen toolpath with:
DoOEMButton(160)
at the end of the button script (160 is OEM button code of regen toolpath button)
- if you need to wait for machine to stop moving, put this before regen toolpath:
while isMoving()
sleep(100)
wend

I haven't tested it, but that should be the concept. There is lot of useful info in
http://www.machsupport.com/wp-content/uploads/2013/02/Mach3_V3.x_Macro_Prog_Ref.pdf
if you're interested.



45
General Mach Discussion / Re: subroutine
« on: January 28, 2014, 04:09:54 AM »
(assuming that Z0.5 is safe for rapids along xy)
G00 Z.050 (go to safe Z level)

G00 A72 (next A position)
M98 P1 (call subroutine 1)

G00 A144 (next A position)
M98 P1 (call subroutine 1)

G00 A216 (next A position)
M98 P1 (call subroutine 1)

G00 A288 (next A position)
M98 P1 (call subroutine 1)

G00 A360 (next A position)
M98 P1 (call subroutine 1)

(exit move)
G00 Z.050 (go to safe Z level)

M30 (end program)

O1 (subroutine 1 start)
G00 X0 Y0 (assuming we're in safe Z, position xy for the start of the cut)
G01 Z-.050F5 (engage)
G01 X 1.25F25 (cut)
G00 Z.050 (go to safe Z level)
M99 (return from subroutine)



46
:)
Nice workaround, thanks Ian.

47
Hi,

I'm using Mach3 42.20 and it seems that in this version, the CV mode makes smooth transition from G1 to G0 move (eg. tool retract move). This may be less obvious on setups with high acceleration.
Example:
N1 G1 Z0 F100 (plunge)
N2 G1 X100 F4000 (cut)
N3 G0 Z100 (retract)
This may present a problem (especially when engraving) on line 2, because G1 move is not completed on Z axis/level. CV smoothes the transition between lines 2 and 3 and starts retracting the tool before the end of G1 move.
Workaround for this is to check "CV stop at angles" option in General settings (89 degrees worked for me in this particular example, but since this option is used for transitions on all axes, exact value depends on desired behavior on all axes and acceleration/feed settings).
Attached picture shows the example engraving with "CV stop on angles" option unchecked (left, notice 2 unfinished lines) and checked->89(right) done with 0.1g@4m/min. It also shows for 90 deg angles CV radius to be:
radius = (feed^2)/(2*acceleration)
distance between engraved lines is 2.5mm, calculated CV radius for 0.1g@4m/min is 2.2mm (with 0.3g, radius is 0.7mm - which is much less noticeable)

Regards,
Mihael

48
General Mach Discussion / Re: Is my PC too slow or...?
« on: April 23, 2013, 05:55:47 AM »
Thank you guys. Lot of issues got fixed since 042.020, I hope those will not prove to be serious :)

49
General Mach Discussion / Re: Is my PC too slow or...?
« on: April 22, 2013, 04:42:24 PM »
I think I was using 043.022 when I noticed the problem, and then upgraded to latest version. What I found weird, is that I couldn't find reference in the changelog for the version I was using prior to update....
During testing I turned off all CV related extra features, and I'll keep them that way until I find good scenario to use them :)

Guys thanks again for looking into it. Where can I download older stable builds ?

Cheers,
Mihael

50
General Mach Discussion / Re: Is my PC too slow or...?
« on: April 22, 2013, 08:32:02 AM »
I played with lookahead and kernel frequency, but with no results. Ian, would you please, if it's not too much trouble, post your settings xml file, so I can do the comparison ? BTW. your machine is quite impressive, handling theese feeds and accelerations with no vibrations (being built from alu extrusions, if I'm seing right) - do you have build/specs thread ?

I ran test one more time with 0.3G accel, and though I cannot see that machine slowsdown/stops, I can feel it if I touch the machine frame. So, my theory about low acceleration causing CV to fail is not correct. Also, I presume that PC is fast enough, since Ian is getting good results with slower PC.

Thanks,
Mihael

Pages: « 1 2 3 4 5 6 »