Messages

551

Mach4 General Discussion / Re: TouchOff UI

« on: January 12, 2017, 07:15:04 AM »

Hello Larsaf,

Assuming you installed Mach4 and all of its components in the default location and you are using one of the default (unedited) screens, it should just work.

552

General Mach Discussion / Re: Big trouble

« on: January 07, 2017, 12:42:15 PM »

Sounds like one of two things to me. You have a pirated copy of Mach or an electrical noise issue.

553

Mach4 General Discussion / Re: Lua

« on: January 06, 2017, 09:07:58 AM »

This is an example that is in the default screens. Most of it is commented out and it doesn't have as many comments but what it does is sets up input one to do two things. Cycle start and feed hold. It acts like a dead man if used with a momentary switch.

You push the switch in, input one changes states from 0 (off) to 1 (on), the function runs which checks the state of the switch and if == 1 it runs the CycleStart function (found further down in the screen load script).

When you release the button the state of input one changes again and it now == 0 (off). So, since the state changed from 1 to 0 the function runs again which checks the state and if anything other than 1 run the  mc.mcCntlFeedHold API call.

Code: [Select]

[mc.ISIG_INPUT1] = function (state) --Add input one to the signal table so this function runs each time input one changes states.
    if (state == 1) then --If the state of input one equals 1 (on) run the CycleStart function.
        CycleStart()
    else --The state of input one does not equal 1
        mc.mcCntlFeedHold (0) --Feed hold instance 0 of Mach4
    end

end,

554

Mach4 General Discussion / Re: Can i edit or add to a Predefined Macro?

« on: January 04, 2017, 09:20:28 AM »

Thank You So it is as easy as writing a M6 Macro

Yup, maybe even easier. 

Remember, the macro file name and functions inside the macro should all use a lower case m.......... m30 not M30

555

Mach4 General Discussion / Re: Toggle Coolant on/off in SigLib

« on: January 03, 2017, 10:21:50 AM »

No problem, hope it helps.

I have attached an example wiring diagram.

556

Mach4 General Discussion / Re: Stupid little question

« on: December 30, 2016, 10:07:57 AM »

Another thing to note about the router screen Vs. mill screen.

Some of the supporting macros and output descriptions are only in the default router profile.

For example: one of the buttons on the router screen is for Dust Hood Up/Down (M114/M115). In the outputs list of the router profile you will find an output named M114/M115. In a mill profile that output is named Output #52. Also, the router profile has the m114 and m115 macros already so the output for the dust hood can be turned on and off from Gcode.

Not that any of this can't be done in a Mill profile, all of it certainly could be. But none of it will be in the default Mill profiles. To use them in a mill profile (or any profile for that matter) you would need to do some customizing. The default router profile (which uses the default router screen) includes tested and working examples.

557

Mach4 General Discussion / Re: Mach4 Random Crash

« on: December 28, 2016, 07:21:07 PM »

Just some random thoughts.
Sometimes when I hit the estop (to remove servo power), the monitor goes dark then returns in a few seconds.  I have not figured out how this is possible since there is no direct connection.  No reason the monitor would lose power.  Could interference cause this?  My pc motherboard is in the same cabinet as the servo drives with no shielding.
Or maybe removing power from the servo drives is causing power surge/drop to the pc?  Could this cause windows to crash in this manner?

Absolutely and I suspect this is exactly what your dealing with. If you have a case you can stuff your PC parts in and test I think I would. Noise can be a real pain to eliminate. 

558

Mach4 General Discussion / Re: CV G64 and Exact Stop G61

« on: December 28, 2016, 05:51:37 PM »

The settings are saved in the profile.

Code: [Select]

If the settings are Zero does that mean a complete stop at the end of an angle?
Yup, if all the settings are set to 0 and CV feed rate is turned on and your running in CV mode it should run essentially the same as it would if running in exact stop mode.

559

Mach4 General Discussion / Re: CV G64 and Exact Stop G61

« on: December 28, 2016, 02:44:29 PM »

What are your steps per set to for each axis? This will make a difference even if only in simulation mode.

Post up a picture of your whole Mach4 screen when it does not follow the path and a close up of a section that is off. Show us what your seeing.

560

Mach4 General Discussion / Re: Toggle Coolant on/off in SigLib

« on: December 28, 2016, 12:19:32 PM »

OK, that makes sense. Yes, if using external switches using the signal script is the way to go.

Some motion devices have inputs for drive faults I think. But, if the motion device and its plugin do not have a way to handle drive faults you could just map them to any generic input in Mach and then use the signal script to do whatever is needed. One thing you might want to consider is using the fault output from the drives in your estop loop. I have used an output as an enable signal to one drive and that drives ready signal is the enable input to the next........ daisy chain them together like that. Can even put that daisy chain in the estop loop. That has worked good for me. All depends on your drives and how you need it to work. The machines I have done that on are not huge so having a dedicated input and/or message for each drives fault was not necessary. The operator can glance at the machine and see whats out of place. If it were so big they could not see all axis at once I would do it different.