Advanced Search

Just had this happen today. Running along just fine, 2 hours into the job and then the End Mill snaps with about 5 minutes to go. What I would like to do it is:
 
1.Pause
2.Stop the spindle
3. Jog to a place where I can change the end mill
4.Touch off again to set my Z
5. Resume the job where it left off (or even better back up a few line of G Code)

Is this possible?
Thanks,
HH

Note that there is a re-write of Halshow under development, it might be worth seeing if there is scope for adding your ideas there?

github.com/LinuxCNC/linuxcnc/pull/4231

All those "affordable" 5-axis machines marketed seem to be kind of a scam. Machining extension for the mentioned CAM program costs (AI info unverified) 3200$ per year.
Rarely a real 5 axis machining is shown. My suspicion is that most of the few examples are show pieces which took a lot of effort to prepare.
For the Statue due to lack of CAM I would probably do some 2.5D setups and use the rotary axis as positioner rather than as a fourth axis.

I'm trying to use LinuxCNC_ArduinoConnector V2, but it's not very clear how to install this new version. I initially used install.sh, then loadusr arduino-connector, but an error appears. I included the instructions in the hal and ini files, but nothing happens when I run linuxcnc.

At some point, we will see true simultaneous 4th (and 5th?) axis CAM that is affordable for amateur use. I use Fusion myself and it supports "3.5 axis" toolpaths ie indexed or wrapped 4th axis, not true simultaneous 4 axis. Fusion does actually support simultaneous 4th but for access you have to cough up for the ludicrously expensive "extensions".

I've seen a few of these 4 and even 5 axis desktop machines being marketed (Pocket NC, Infimaker, Makera etc), yet I've no idea how you would be expected to create toolpaths of your own. Does anyone know?

Looks as if Freecad is in the early stages of developing 4th axis. That may be our best hope in the medium term.

1. fix bug in last side tilt angle  2. punch a ridiculous number of holes around the edges of the figures in the collection using an external subroutine. (makeholehere.ngc, included in the zip)

1. Mesaflash source was at one time compile-able on an old windows version I doubt that that is still the case
especially for flashing over a serial port. I can dig up mesaflash.exe but I doubt it will run on current windows.

I suspect the easiest way to flash the 7I90HD would be to leave one configuration as EPP or SPI.
(the 7I90HD has dual flash chips) Then set the flash jumper to select this configuration, power cycle
the card and then without removing power, move the flash select jumper to select the serial configuration
before reprogramming the new serial configuration over Either EPP/SPI with Mesaflash/Linux.

2. The UART module is a standard UART on the serial side (but quite different on the interface side
as it has a 32 bit data interface)

3. You can determine the pinout from the source file PIN_SVUA8_8_72.vhd

4. The regmap file has all this information, its a plain text file. Maybe renaming it to regmap.txt will help for windows.

There have been changes to the driver in the Master branch, one of which was to remove that "assert" and thus handle an error more elegantly.

github.com/LinuxCNC/linuxcnc/commit/6024...7aa599ef908L465-L542

Not directly helpful, but does seem to suggest you may not be the only one who had that problem.

If you are able to build from source, you could make that change and recompile? (Or start running 2.10)

linuxcnc.org/docs/stable/html/config/ini-config.html

Suggests that it goes in the [DISPLAY] too.
I think that the version there sets the slider position in the GUI, but it probably also sets the keyboard jog rate (as keyboard jogging is GUI feature)

I think that the [TRAJ] value might only set the jog rate for hardware buttons via halui.axis.L.minus / halui.axis.L.plus

UART and Smart-Serial are different. If it says "ua" rather than "ss" in the filename then they are standard UARTS.

try again, found a bug

and now you can try to set the Error_Values to
6 0 112 0 0

this should switch all outputs to off on connection errors (PC<->FPGA)

doh.. yeah, that can happen...

I just pushed some changes that allow sequential loading correctly that captures hal loading for all ui's at startup for registration. this should allow the use of hal widgets in all user ui files. should be up and live by 8am EST.

ok, i have order one, than i can fix and test it the right way
maybe next monday

@meister I tested your last dev commit, and the N4D3E16 template only works with the outputs; the inputs don't work.
Thank you so much for your work!

Billy wrote:

The issue is that my ESTOP-out is no-longer tracking either the GUI ESTOP or the hardware ESTOP-in.  It just stays asserted all the time with no change of state.
 

I don't have a 7i96s, but out of curiosity I checked it on my 7i92...

You can make two types of mistakes:
1. Electric.
2. Logical.
It looks like you did both.
First, about the electric one. It is true that there are inputs that detect all possible states (high, low and high impedance), but I have only seen such inputs in logic states analyzers. Typically, the input detects only one state or no this state. For example, shorting the input to ground causes the output to change to the opposite state, but it does not matter whether we short the input to Vcc or leave it unconnected anywhere. In this case, if the output of the previous gate is high, closing or opening the serial switch does not change anything because the high state and the high impedance state are interpreted the same.
Now about the logical one. By pressing the serial switch we do not change the input state, we only cut off the signal. And this is not the same as what I explained above.

Your configuration either doesn't work at all, or works in such a way that it cuts off the iocontrol.0.user-enable-out signal. This means that the serial switch does not turn off the machine, it only prevents it from being turned on/off via an icon in the GUI, which is definitely not what you wanted.

Can this be fixed?
Probably yes, but it makes no sense because you have a ready-made and 100% reliable solution - the estop-latch component. A switch between the input and ground is connected there, so that each time it is switched, the input status changes.

This is from my config:
And now a few words about the emergency stop switch. As the name suggests, it is used in an emergency situation when we want to stop the machine immediately to prevent it from causing damage.
Sometimes the emergency switch must also disconnect or enable something (for example, turn off the motors and apply the brakes), so simply connecting it to the control program may be insufficient or unreliable (the program may hang or respond with a delay).
You have to remember this, and the bigger the machine, the more seriously that should be treated...