Advanced Search

das Signal in der Halshow bekomme ich bei "coolant-flood"

ich kann es mit M8 und M9 ein- bzw. ausschalten.

in der AXIS Oberfläche ist das "Kühlnebel" Kästchen zum anhäkeln verschwunden

   

i use gitkraken, it msakes things very easy and visual which works best for me, i get confused using git from terminal, too much to remember when making so many changes so i have forgotten how to do it manually. but if youre wanting to dev, i would say install gitkraken and just add the folders in the dev for probe basic and qtpyvcp then you can preview all the latest and locked sown branches and have your own running branch.

 

if you are going to use the user_tab sidebar_tab and new user_buttons to adjust your use case than i would strongly advise just installing via apt.

then in terminal run:

and use the dialog to select the ui files in the configs/(your_config)/user_**** folders, edit save and those will then be stored and kept even through updates. they follow your config folder and are loaded from at program start.

I just added the user_buttons in the latest develop apt distribution so its there for you editing pleasure and tested. saving to the config folder is not an issue as it requires no special root priviledges.

the following buttons are contained in a widget and you can now be change which buttons functions you would like add more buttons (although sizing will become a constraint) pretty much do what you want with this area which remains on the main screen always, it was a feature request for those with routers who would like flood/mist changed to something else such as dust collection, vaccum table etc. so should be a welcomed feature update!



 

probier mal:

[edit]
Grundsätzlich ist es immer eine gute Idee die aktuelle hal und ini Datei anzuhängen.

i uninstalled all apt/deb while using the dev enviroment for testing new functions..

What would be the correct way to change between branches while using dev ? Is it correct to define the git tag ?

Ok, installing 'libeigen3-dev' solved that error.

So this next error would come from not having compiled/installed the 'clothoids-1'?
 

Hallo
Da ich nicht weiterkomme werde ich mich von Linuxcnc verabschieden. Danke all die mir geholfen haben.
Bin ein Älterer mensch (76) und nicht mehr so aufnahme fähig, daher werde ich die Mesa Karte wieder ausbauen und durch eine andre ersetzen.
Werde wieder mein bekannte Software Installieren.
Gruß Hans

ok, das mit dem 1K 1W Widerstand funktioniert nun.
Der Werkzeug Längenmesstaster funktioniert für die dynamische Werkzeug Längen Ausmessung.

Wie sieht es nun mit den übrigen Themen aus?

In der Halshow bekomme ich ein High und Low Signal für den 3D Messtaster. Das funktioniert wenigstens.
Die Einbindung in HAL und INI fällt mir schwer. Gibt es da gute Videos?

Dasselbe gilt für die Mindermengenschmierung (Mist)?

herzlichen Dank für die Hilfe
Claude

3D Messtaster (Schnittstelle)
Mindermengenschmierung

dev and apt/deb should not be installed on the same pc, that is not the intended use case, the script installed dev install is meant for doing development work for the software and apt/deb is designed for machine use on a stand alone system.

the confusion i think is between stable and develop version which is simply which branch the update pulls from. stable being a locked down version and develop being the version currently getting updates and changing.

the dev install is seperate altogether and is meant to be able to switch between branches, add branches for new features and testing and merge into the devlop "main" branch, which then gets distributed via the apt update on machine pc's.

it is an error to have apt/deb installed on the same pc as the script installed dev installation, it will cause conflicts. you would then have two files sytems, one installed at root level and one installed at user level which is run in a venv.

it is terribly confusing and frustration even for us, we previously were noot forced to use the venv on pip installs which allowed for all of the dependencies and the required software to be installed at a root with the src folders readily available for editing at the user level, but this changed in debian 12 unfortunately orcing us to create the venv for those who would be setting up dev and using git to pull/push branches for work on the project.

Hi arabel1a, 

Very interesting. I have some Sercos II drives myself.

I'm thinking the STM32 came with the Sercos software stack, saving a lot of work. Do you have a link to the device you used?

Any thoughts on driving the FC7501 card directly? It has a well documented PLX 9052 PCI interface on one side, and the mysterious SERCOS ASIC on the other side.

Did you ever find any docs for the Sercos ASIC? The datasheet is available, but references a programming manual which I can't find.

I wrote a quick PCI driver for QEMU which presents itself as a fake 7501 card. Windows seems happy with this and auto loads the driver. My thought was, this fake driver could be tied to a second driver on the Linux side attached to a real 7501, allowing the command stream across the PCI bus to be captured. 

Although without the manual, it's probably more trouble than it's worth. Looking forward to hearing more about the STM32 you used.

Hello,
Perhaps this will be useful for you:
linuxcnc.org/docs/stable/html/user/user-...chine-configurations

It shows the typical axis layout.
When I started out with CNC machining I also ran a small gantry style machine, and for some reason i had the table as Z0. When I changed to Z0 being the top most position (and also used Z0 as 'home' for the z-axis as in the diagram above) a lot more things made sense.

/Peter

yes the tool length sensor trigger point is used in conjunction with the G53 Z0.000 machine coordnate system to calculate the tool length offset. This requires Z0.000 be at the top of travel for the z axis.

G54-G59.3 woork coordinate system offsets are used to define the zero point for the work or program. these are set independent of machine coordinates but are offset and stored in relation to the machine coordinate system.

you need to adjust your machine configuration so that Z0 is at the top of travel.

Yes, I fully agree with you that Z goes into negative direction when going down. However, as I understood (correct me if I am wrong), the probing tool requires you to have Z= 0 at the highest Z-Gantry Position. However, my current approach is that X=Y=Z=0 is in the lower left corner on the Bed. AS I understood Probe Basic requires that you config your machine that (as I did now) X=Y=Z=0 is in the lower left corner but 220mm (for me) up in the air.

Cheers

Patrick

I have a hbs86 stepper driver. I try to figure out the timing. From the manual I get this timing diagram.
 



Am I correct that my values should be ?
Step time 2500ns
Space time 2500ns
Dir Setup 6000ns
Dir hold?
 

Hmm, ok.
Do you have the Eigen lib? : sudo apt-get install libeigen3-dev

In the next upload, there will be a check in the cmakelists for that.

So installing the clothoids-1 is for now a manual task. So it's annoying i know. I feel with you.
You can build the clothoids-1 in their own dir using a build dir. Then you can do a system wide: sudo make install.
Or copy the files over into the rtlib. Preferr to build the clothoids before the motion and planner.
I know this has to be changed soon.

Good luck. When spot install problems, let me know.

In the mean time i did some tests.
This are situations where the G64 P20 Q0 is used. Extreme situations to verify the blend algoritme for robustness.
Will show now a few pictures sets. Each set is before blending, and after blending with radius 20mm.
This are files using low dimensions so 20mm is just a incredible high value.

before:
 
after:
 

Here you can see the interpreter has given around 20.000 gcode lines. Not the entire file.
Therefore you see the buffered output is filletized as a result. When this then is machined, the next
load will occur.

before:
 
after:
 

before:
 
after: