Hello Guest it is March 28, 2024, 03:39:16 PM

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 - ravencnc3

Pages: 1 2 3 4 »
1
Mach4 General Discussion / Re: Switch one output with 2 different signals?
« on: December 04, 2019, 07:21:22 AM »
Yes, its a toggle button
My assumption was that this would enable the spindle as well.
Because this "spindle on" is linked to the spindle control relais and as a second output to the air seal relais.


I want to have a button to enable this second Physical port without activating the spindle.

2
Mach4 General Discussion / Switch one output with 2 different signals?
« on: December 04, 2019, 04:32:49 AM »
Hello,

Setup: Mach4 with ESS Smoothstepper.

I have a gas seal relais for my spindle.
This needs to be turned on, whenever the spindle run.
Easy to configure - I just put this output in the Spindle "Spindle on" row in outputs and working.

But I want also to have a manual Button to turn it on when the Spindle is not running.
So I add a button in the GUI to toggle "Output 4".
But now it is not possible to also set this physical output pin in "output 4" row.
My assumption is, that it is only possible to asign a physical output to one signal.

I also tried to assign the virtual "Output 4" to the "Spindle on", but this seems also not possible.

So my Question is:
How can I switch on a Physical output pin by a GUI button and also by Spindle on?

Something like "If Spindle on or Output4".
Does this need to be in the PLC Script loop or is there an easier way?

3
Found a solution - following script will save DRO and Tool offsets.

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

mc.mcProfileSave( 0 )
mc.mcToolSaveFile( 0 )
mc.mcFixtureSaveFile( 0 )

This also can be included to be called each time you zero an axis.
Then there can never be data loss, even after crash of mach for whatever reason.
If you save 1 Part in 10 Years with this, it was worth the effort :).

4
I can not agree.

For shure you are right to always fight the source of the trouble instead the sympthom if possible.
But for a robust system you never trust on one fix.
There will always a person who inure his foot, and he is then more than happy that there is an ambulance to call.
Try to remove all weapons (in the us   ::) ) or all other sharp objects which might hurt you. This will just not work to pack the world in cotton wool.


There is no real reason for storing stuff only in ram and loosing it on meteor income, flood, storm, water pipe break, fire, windows update,... If you find a way to prevent from 100% of all possible desasters you won the holy grail.

My other mills (bCNC) store when you set the WCO to zero and that is even a free software.
In mach this can also be automated, if such a script/button exist.
For example also save when you change something like WCO or test all minute if a change in settings happend then automatically save.


5
Thread is about a save button!

Think about a power outage once a month or any other imaginable "Mach dones not close graceful".
I dont want to lose parts on those accidents and the only think against this is currently take photos of the DRO after each set zero... -> Bad and annoying


Someone has a hint on this save button thing?
Toppic is only about this "save" all settings button and if it is possible to build one.

6
Yes, Its from Network. Of course wired with gigabit to NAS.
Maybe this happen when the Server HDDs are in energy save and need to spin up - take 1-2 seconds.
Using USB sticks for bringing a nc program from CAD to production is not really an option in the 21st century...
But again - not the deal of this topic even if this is not nice from Mach 4.


Found:
rc = mc.mcProfileSave( number mInst)
mcToolSaveFile(mInst);
mcFixtureSaveFile(mInst);

Any idea if it is possible to build this "Save" button with this?
Found no example how to use this and what is the correct instance number...

7
Mach4 General Discussion / Save button - Save WCO, TLO,... like on exit
« on: October 08, 2019, 09:57:17 AM »
Hi,

At least once a Week Mach 4 crashes.
Most of the time when I press "Load" it hangs and do not longer react so I have to end the task.
I never could find out why - but this is not the toppic here and only the background why Im asking...


The biggest problem with this is, that I loose the WCO, new set Tool lengths, and other settings because Mach 4 saves everything only on exit.
For that reason, I started to make a Picture of the WCO coordinates every time I mill a part with multiple files.
As you can imagine, this is irritating doing it 100 times per week for 1 Crash per week.

But a lot more convenient could be a "Save" button.
Just save everything - like on exit.

But I could not find out how to do this?
Seems not to be done in the wx4 screen unload script not in another place I can find.
Any tips if it is possible or how to do it a "Save all" button (script for a button)?


8
Thank you for your time supporting me here then :).
I will change it to my needs.

One last question:
"explicitly not compiled to serve as an example"
Is there a list where to see what serves as an example and what not?

9
Thank you for the Answer.
So I summarize - Touch GUI is not for probes...
This is not self explaining by viewing this button nor explained in the help texts.


But... The most used Button - Find X, Y and Z in one operation - is only in the "Touch" Menu.
The Probe menu does not have such an very convenient operation.
So it needs to be added by myself. Right?


And a second idea:
Even if the Touch GUI make use of TLO - it will still work for all without toolchangers...
So adding this single subtraction to the "Touch" would allow Probe and ATC users to use the cool Touch functions without breaking anything for non ATC users... right?
Another great feature of "Touch" is, it is not in a separate TAB and you can see the DRO's while using it.



10
Hi,

I do a touch move with a 3d Probe in Z- Direction.
Tool length offset for my Probe is 155,0763.


The Tab "Probing" and "Single Axis Move" correctly use the offset from the tool Table selected tool.
The Button "Touch" (mcTouchOff.lua) on the main screen does not use this and sets a complete different value.

Because the "Touch off Plate" is used in x, y and z direction as same offset, it is also not possible to use this to compensate with the correct length offset.

This is the code from mcTouchOff.lua:
Code: [Select]
function SetFixOffset(Axis, Direction)
if (Axis == 'X') then
Pos = mc.mcAxisGetProbePos(inst, mc.X_AXIS, 1)
OffsetVal = (((ToffPlate + ToffToolRadius) * Direction) + Pos)
elseif (Axis == 'Y') then
Pos = mc.mcAxisGetProbePos(inst, mc.Y_AXIS, 1)
OffsetVal = (((ToffPlate + ToffToolRadius) * Direction) + Pos)
elseif (Axis == 'Z') then
Pos = mc.mcAxisGetProbePos(inst, mc.Z_AXIS, 1)
OffsetVal = ((ToffPlate * Direction) + Pos)
end
...


Code from mcProbing.lua:
Code: [Select]
if (SetWork == 1) then
local HeightOffset = mc.mcToolGetData(inst, mc.MTOOL_MILL_HEIGHT, OffsetNum)
local HeightOffsetW = mc.mcToolGetData(inst, mc.MTOOL_MILL_HEIGHT_W, OffsetNum)
local NewWOVal = MeasPointMACH - HeightOffset - HeightOffsetW
Probing.SetFixOffset(nil, nil, NewWOVal)
end

So my assumption would have been, that two default Mach4 scripts should use the same Z Calculation in touching?
Or have i missed something how to use this correctly?


Pages: 1 2 3 4 »