Advanced Search

RDA wrote:

Was the topological naming issue solved.

Yes, to a certain point, but mostly better workaround than commercial solutions, from a quick glance.

I'm also on the stable version and I'm also seeing this message.

I assume it applies to all users since the latest versions introduced some new settings that did not exist before and therefore and may require the config files to be updated.

Hello,
I'm on stable, but i still get the message.
 

How can i change it?
Many thanks for the great work!
Best regards
Anton

Was the topological naming issue solved. That was the reason I stopped using freecad some years back.
apart from that it was quite nice to work with.

I guess a quick google would tell me this but I prefer answers from actual users.

I've played with FreeCAD a little bit, but not much with the new 1.0 ver.
forum.linuxcnc.org/38-general-linuxcnc-q...-clearing-hsm#141098

I've not used the new version enough to say how much it is much improved over the old in usability. But I is noticably less buggy, and naming of some of the tools makes more sense.

That said, while very capable, usability is still far from simple with a steap learning curve. You can still run into a lot of "can't get there from here" situations.

I opened a develop-branch for a updated version of my subroutine.
Version 5.0.0 will be for Probe Basic 0.6.0 (and hobefully higher) and can also be used with every other GUI.

Using M600 Tx(tool change and measurement) and M601(only measurement) the subroutine can be controlled from any GUI.

You can find all files here:
github.com/TooTall18T/tool_length_probe/tree/develop
It is now a release version:
github.com/TooTall18T/tool_length_probe/releases/tag/5.0.1

Hi David,

Yes, I read about it in Mark's thread. Having a fully functional machine from the start is indeed quite lucky. It's good to know that electrolytic capacitors are often the issue; I'll keep that in mind when we look at the next old machine to buy and restore.

I did consider keeping the machine in its original state, but in the end, I decided the advanced capabilities and modern control options of LinuxCNC were too appealing to pass up. Call me a masochist, but tackling the challenges was also kind of fun!

I believe our hydraulic setups are quite similar. In our case, the pump is connected to a three-phase 380V power supply via 3Q1, followed by the pressure switch. We also have 5K1 (controlled by the CNC), which then operates 3K1 to turn on the hydraulic pump—only if the spindle is off (1K7 - Hauptantrieb Stop).

For the lubrication system, the computer manages 4K1, which appears to operate the pump at 110V. I am thankfull that the lubricator has not been acting up.
Do you have pictures from your machine?

Cheers,

Sebastian

I have a XYZB Machine...

I had planned to use a pot for feed and spindle speed overrides, but on commercial machines I have operated, these dials are often detented and incremented, like maybe 2% or 5%. I am happy to use a rotary encoder instead of a pot, but I have to learn how to implement that in LinuxCNC. Looking forward to it!

My point was that I already have the analog stuff that I want to learn how to implement, and I can and will use binary controls after I have sorted out LinuxCNC at the most basic level - I am not there yet! I figured that if I could just wire up an MPG and axis and resolution dials, I could at least jog the machine. That is my objective, right now.

With mux, there just aren't enough data points available to to jump in yet. For example, what value of diode should I use on a rotary switch? What happens if I mistype a value in the HAL configuration as I set this up? I don't know what I don't know.

fully_defined wrote:

This seems like a good suggestion.

I suppose by "binary" you mean digital (is that the Australian way of saying digital?) as opposed to analog. Are you saying I don't need analog pins at all for this? I still want to know how to do this kind of thing with analog pins, even if it's just for a learning experience. I am literally starting from scratch here, and I already have the switches and 1k resistors.

Also, seems like mux4 has a limit to the number of selections on a switch. What if I have a switch with 7 selections I want to make? Or 9? I don't know any more know now than I did before about the physical wiring.
 

Binary in this case means both digital and encoded (in binary)

In addition to mux4 there are mux2,mux8,mux16 and mux_generic
(mux_generic supports up to 1024 inputs!)

You can certainly do this in analog but the hal support will be more
complex, since you likely want accurate increments and that means
using a mux component anyway.

To display the axis configuration add a entry in the ini under display section. There are currently the following preconfigured screen adaptations: 
xyz
xyza
xyzab
xyzac

GEOMETRY = (enter one of the above here)

For example the probe basic sim has the following:

GEOMETRY = xyzac

 

If you configuration isnt on that list you would need to do dev install and edit/add a a tab with the appropriate display for your machine.

I never said it was better, but easier and more control while simpler to wire in.
I use pots for feed rate, but if it seems better to use a switch, please do, they do the same job and both work fine.

Hallo
Danke für die Antword
Ich möchte die Anordnung am Bildschirm ändern (Jog Butten), Das die X Tasten Vertikal angeordnet sind X + ist unten und X - ist oben.
Ich hoffe das das nicht viel Arbeit macht.( Bei Mach3 wird das von der Tastur gemacht).
Gruß Hans

I struggle to understand how that would be better than a switch.

Thanks! I was able to get it to work by connecting my components pause-program output to the qtplasmac.ext_pause (I haven't updated yet to try to the ext_pause_only). It appears there was timing issues when I was trying to trigger this by throwing the ohmic signal high.

Side note, I believe when I was first working on this I was occasionally using sudo with halcompile (I'm on a RIP install) so the changes to the comp weren't actually happening.... lessons learned!

Reverse run seems to be working without fault now, but I do have another question on why it can't go back further than the last M03 (or any M-code)? I have some M64/65 set periodically in gcode and it will not reverse past these points. I took a look at the tcq.c file which is where the 200 line limit is set, but cannot find any reference.