Hello Guest it is March 28, 2024, 04:17:56 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 - Greekart

Pages: « 1 2 3 4 5 6 7 8 »
21
I have mapped the output 0 on pokeys with the output OC1.
(see picture) and do the gcode with M62P1 but no activation of the OC1 output.

Hi, first to activate Output0 you need to do M62P0 and follow with movement, like:
M62P0
G1 X10 F300

I also saw that there are macro files in the M162 and M163 macros folder, what are they used for?
Don't know, i don't have those macros and every macro is used base the machine use.

Yes ok I saw for the mach4 output, I will try the config.
On the other hand on pokeys we find that the soft version:
  PoKeys v4.5.0 Configuration and PoBlocks (8.9.2021) .exe (53.41 Mb)
and PoKeys Mach4 plugin version 8.78.0.4342 + manuals.zip (7.5 Mb) with date of 09/2020
I don't see a plugin version of 10/2021.

I get from polabs support the latest, i don't know if i can share it here or is ok for you. I had problems with M62 too before i upgrade plugin/software, don't spend time figure it out without upgrade the versions. Ask polabs for newer or tell me to send it to you.

22
But I don't know if I am configuring M62Px correctly.
I associated Spindle on (therefore M3) with relay 1 and spindle forward with relay OC 1.
But how and where is it declared that M3 = spindle on and where is written that M62P1 + = *********X?
Following the tests M62 / M63Px does not work with the gcode (above), M3 activates relay 1 and relay OC but M63P1 does not cut OC.

No need to use spindleOn/spindle ffw for M62P*, just set pokeys oc to an Mach4 output (ex. Output2) and use M62P2/M63P3 with follow code of G0/G1, be sure that u have the latest upgrade of pokeys software/board. There is a plugin from 10/2021 and software vs is 8.85.

23
Mach4 General Discussion / Re: Z-axis +/- reversed
« on: November 18, 2021, 08:44:56 AM »
Thanks for the quck reply.
I did try that but no joy.
With what command you see it reversed? With keyboard, from g-code Z+/Z- or when you homing?

24
Mach4 General Discussion / Re: Z-axis +/- reversed
« on: November 17, 2021, 08:43:21 PM »
Hi All, I just installed Mach4 Hobby. My Taig Mill worked perfectly using Mach3 but after installation of Mach4, the Z-axis is reversed. Z+ now moves the head down and Z- the opposite. Has anyone had this problem? Equipment: Taig 5019DSLS mill, UC-100 motion controller, Mach4 Hobby. Thanks in advance.

Just reverse the motor from "motors" page. Sure must be many with that "problem" :) but the solution is super easy.

25
Hello,
If you use the machine state push and pop functions documented in the API it will solve this for you.

mcCntlMachineStatePush at the beginning of the macro.

Then before you leave the macro

mcCntlMachineStatePop

This will revert you back to all the previous modal states called before the macro :)
Best of luck!


Good to know, i find it and at the core manual. Thanks a lot, sure i will give it a try :)

26
Mach4 General Discussion / Re: Two (different) machines, same computer
« on: November 15, 2021, 07:34:24 AM »
I work 3 machines, one pc. I don't see why you wouldn't, every profile have different settings and stored in it's own folder so when you load a machine/profile the settings of this profile are loaded.

If your controller/plugin has something else, different that not let you do that i don't know!

27
Problem solved

I use inside the macro to change back the position mode G90 and all went smooth.
Code: [Select]
--To get the current position mode
local positionMode = mc.mcCntlGetPoundVar(inst,4003);

--To set back the position mode
mc.mcCntlGcodeExecuteWait(inst,"G"..positionMode);

28
By the look of it you enter the macro in G90 mode and exit in G91 mode.
You was/are right, because it not change to G90 as when it start does it. I was trying to solve other problems before and when that happened i get so frustrated and didn't see the obvious. Again thanks a lot. 

I try by adding it inside g-code after the macro and it works, i believe it will work from the macro too.

29
I see nothing in your macro that reads the current state of your machine e.g.
I am going to try and post back, thanks Graham.

By the look of it you enter the macro in G90 mode and exit in G91 mode.
That true too :)

30
Mach4 General Discussion / Run macro from g-code program makes erratic move
« on: November 13, 2021, 09:34:46 AM »
Hi guys, i hope everyone is well. I try to run a macro with probe movement to reference my Z axis, when i run the program without the macro it goes as expected but when i add the macro inside after the sequence ends (the script works as suppose) then next movement will go with acceleration that in not suppose to be (it will do a erratic move and threw driver error).

This the test program i use (a simple rectangle with lead in/lead out)
Code: [Select]
%
(Filename: Test.nc)
(Date: 13/11/2021)
G21 (Units: Metric)
G17 G90 G80 G40
G00 Z10
X0.5800 Y80.0200
m108 (if i remove this line all runs great)
G00 Z5
G01 F254.0
G03 X2.5000 Y78.1000 I1.9200 J0.0000 F2200.0
G01 X77.5000
G02 X78.1000 Y77.5000 I0.0000 J-0.6000
G01 Y2.5000
G02 X77.5000 Y1.9000 I-0.6000 J0.0000
G01 X2.5000
G02 X1.9000 Y2.5000 I0.0000 J0.6000
G01 Y77.5000
G03 X-0.0200 Y79.4200 I-1.9200 J0.0000
G00 Z10
M30
%

And this is the m script
Code: [Select]
function  m108()
local inst = mc.mcGetInstance('m108 script: ');

local probeCode = "G31"; --G code of the probe to use
local safeProbestart = -50;
local returnZ = 20;
local probeOffset = 0.1;
--define motors mapping
local zAxisNb = 2;
local ProbeSignal = mc.ISIG_PROBE
--Track original Z position
local orgZ = mc.mcAxisGetPos(inst,zAxisNb);

mc.mcCntlSetLastError(inst,"M108 – Processing Ohmic sensor touch!");

------------- Check Probe -------------
local hsig = mc.mcSignalGetHandle(inst, ProbeSignal)
local ProbeState = mc.mcSignalGetState(hsig)
if (ProbeState == 1) then
mc.mcCntlSetLastError(inst, "ERROR: Probe signal is ALREADY activated.")
mc.mcCntlEStop(inst);
return;
end

--Ensure we are homed on Z axis
local zHomed = mc.mcAxisIsHomed(inst,zAxisNb);

if (zHomed == 0) then
mc.mcCntlSetLastError(inst,"Z axis is not homed");
mc.mcCntlEStop(inst);
return;
end

--Move Z to safe start position
mc.mcCntlGcodeExecuteWait(inst, "G90 G53 G0 Z"..safeProbestart); -- Move to probing pos

mc.mcCntlGcodeExecuteWait(inst,"G91 "..probeCode.." Z-25 F200"); --Probe to a max of -40mm

mc.mcAxisSetPos(inst,2,probeOffset); -- Set Z to old tool probed Z

mc.mcCntlGcodeExecuteWait(inst,"G91 G0 Z"..returnZ); -- Move Z to org pos

 if (ProbeState == 1) then
wx.wxMessageBox("Probe is still activated!  Check to make sure probe is not damaged or still contacting strike plate.");
else
mc.mcCntlSetLastError(inst, "Z Axis now referenced.");
end

end

if (mc.mcInEditor() == 1) then
m108()
end

Has anyone had that kind of problem and know the solution?
Thanks a lot

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