Messages

2841

General Mach Discussion / Re: New to CNC and built my own CNC but now come the questions

« on: March 22, 2019, 06:51:59 PM »

Hi,

I also must add an apology but from reading through many of your post on your forum that many do not like the China made components which I am guilty of purchasing.

I'm one of the most vocal of such critics. I'm not against all Chinese stuff, most of it is
pretty good value for money. I suspect that your kit is good EXCEPT for the rubbish USB controller.

If you bought a decent US or European controller to replace it then your kit would really
come alive. If memory serves correctly I think lumber60 may have had the same trouble
and I think he may have replaced the controller.

Craig

2842

Mach4 General Discussion / Re: wx lua error when lua newfangled solutions plugin is enabled

« on: March 22, 2019, 05:36:56 PM »

Hi Gary,
have you updated to a later Mach4 build recently?

The reason I ask is because the latest builds of Mach use Lua 5.3 (cf Lua 5.2 of earlier builds) and maybe that has thrown
a spanner in the works.

Craig

2843

Mach4 General Discussion / Re: Spindle warm

« on: March 22, 2019, 05:33:54 PM »

Hi,
I'm sorry I can't see anything wrong with that code.

I understand that just recently NFS has upgraded their Lua for 5.2 to 5.3. While 99% of it is identical there are a few
differences. I would guess that is whats happening here. Not that I can see it......

Craig

2844

Mach4 General Discussion / Re: input signals

« on: March 22, 2019, 05:08:25 PM »

Hi,
I can only guess then that you have made a mistake in the pin assignment, or may be the logogical
connection of the pin to mc.ISIG_MOTOR0_HOME

Craig

2845

Mach4 General Discussion / Re: input signals

« on: March 22, 2019, 03:54:14 PM »

Hi,
may I suggest holding the home switch closed, or even disconnect the wires to it and short them together
to see whether the code detects the signal if it is deliberately held in opposite state.

Craig

2846

Mach4 General Discussion / Re: input signals

« on: March 22, 2019, 03:46:58 PM »

Hi,

Trying to read as much on how signals word as I can I saw something about needing to put something in the screen load.

That is appropriate if you want to do something anytime a signal changes.  In your case all you want is to test a signal
when you run a macro.

Craig

2847

Video P*r*o*b*i*n*g / Re: 3d Probing on Granite slabs

« on: March 22, 2019, 01:47:39 PM »

Hi,
I imagine the tool would be flood cooled. Water cooling vastly extends the tool life, poly crystalline diamond tools
are expensive.

Craig

2848

Mach4 General Discussion / Re: input signals

« on: March 22, 2019, 01:21:03 PM »

Hi,
kool, now we can see the context.

Have you single stepped through it?

Craig

2849

Mach4 General Discussion / Re: Windows 10?

« on: March 21, 2019, 11:07:48 PM »

Hi,
to be honest Mach4 is a light weight application, it doesn't require a highly optimized PC.

I use a SmoothStepper and Warp's recommendation is to either disable or remove WFI. Other than that you can run
Windows as standard retail install. It is also recommended to turn off automatic Windows updates as they stop the
PC in its tracks........thanks to Microsofts vigilance! You will need to let Mach4 through the firewall and anti virus programs.

Craig

2850

Mach4 General Discussion / Re: input signals

« on: March 21, 2019, 10:51:40 PM »

Hi,
if its supposed to be in a macro then code it as such.

A macro must start with a line like;

Code: [Select]

function m120()
local inst=mc.mcGetInstance() etc etc.
....
....
....
end

And finish with these lines:

Code: [Select]

If (mc.mcInEditor()==1) then
       m120()
end

Without this last bunch of code you can't single step through the code in debug mode......tell me you do use the debugger
don't you??

The error code stuff is still so far above my head that I might see the fact that there is error code.

Tuff s*********t, its part of the business of coding, you need to get onto it because it makes your coding better and easier...
not harder.

Craig