Advanced Search

Aciera wrote:

Thanks Rod, I find it rather unfortunate that somebody like you does not seem be offered write access to the 'official' install documentation. The pull request process is so sluggish that by the time new install docs might actually make it through they're already outdated.

I have tried to keep my doc current but I have not installed on a problem PC for quite a while. It has been suggested the install ISO should install the R8168 driver as it should not get in the road. Not sure on that. (I built the ISO and the Pi images for Linuxcnc).

At one stage I was asked to edit the getting Linuxcnc docs and it included most of my documentation notes you refer to. This was accepted and was published in the 2.9 docs. However, when 2.9.1 was released, this was all blown away and replaced with content based on 2.8 docs.

I think there should be a new document added that might be called something like "System Optimisation for Linuxcnc", perhaps a seperate doc for the raspberry Pi it links to. If somebody was to have a go at that from my material, I would not have a problem. Asciidoc and I are not good friends.
I almost know enough about git to be trusted with write access... but time is an issue

For a gantry machine you must have homing sensors on both sides of the gantry.
for an XYYZ machine, start with a HOME_SEQUENCE of 0, -1, -1, 2  for each joint in order
Ref: linuxcnc.org/docs/stable/html/config/ini...l#sec:homing-section

Hey!

I am currently trying to get my machine running. My current issue is that I can not get the connection between my spindle (A BD600 via VFDmod over RS485) working in ProbeBasic. I can change the speed of the spindle using GCODE, so I can confirm that it works. However, I can not see the speed in BasicProbe nor can set the Speed. I think I am missing any HAL connection. My machine hal (iHSV57.hal) is currently a mess but I attached it as well.

My BD600.hal looks as following:
Does anyone know the correct connection? Is there any documentation available?

Hey there, sorry for the late response.
I wanted to get back whenever the machine and the servos are in their places and actually drive something.
Thanks again for your help and explanations. Understanding the historical context can be very helpful especially when looking for example configuration that may be 2.7 and earlier.

In any case, while I tested all axis back then without problems I think I never tested driving two joints (servos) on the same axis. I use TRIVKINS X Y Y Z. Where

Now with everything on the machine I can drive joint 1 (first Y servo) just fine. Joint two doesn't do a thing. Looking at the HAL output I can see that Joint2 (doesn't get any commands. I briefly wired that servo the Z-Axis just to test the wiring and it's moving without a problem. Is there something I should be checking beyond the TRIVKINS portion?

pastebin.com/3gND7BUk

Is what I have now.


Also if we're at it, would such a setup benefit from two homing sensors on the Y axis? The gantry is rigid.


Thanks again,
Alessandro

Using the following

uname -a
Linux debcnc 6.1.0-23-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux


From the url to install and setup mesact
github.com/jethornton/mesact

To run from a terminal you need to install some depenencies:
sudo apt install python3-pyqt5
sudo apt install python3-distro
sudo apt install zip

When I run..

 sudo apt install python3-distro
 
I get the following error message.

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package python3-distro is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'python3-distro' has no installation candidate


Does anyone know how to fix? Thanks
Thanks

Found the relevant commit, looks like the change would need to be done here (also)
'src/emc/rs274ngc/rs274ngc_interp.hh':

github.com/LinuxCNC/linuxcnc/commit/d731...f8b87d773bc7868288b2

I'll try tomorrow.

[edit]

- Seems this section of the code has been moved to the one in interp_remap.cc I posted above
- And yes this seems to work just fine, although it does not allow a call to the built in M code as for the other built in Mcode remaps.

phillc54 publicación=312436 id de usuario=6129Debe configurar el repositorio en Synaptic para

deb http://buildbot2.highlab.com/debian/ bookworm master-uspace plus you need to copy the key as shown for the new style. This is all shown here:
http://buildbot2.highlab.com/
 

Thank you but I am not able to put the keys in. I don't know which file to save them in.
I do sudo nano /etc/apt/trusted.gpg.d. A terminal opens and I paste buildbot-archive-key.gpg but when I try to save it it tells me which file I want to write it in and I don't know which one I should do it in.

Nor should M61 .. M68 be remap-able
linuxcnc.org/docs/devel/html/remap/remap...ng_codes_s_m0_m1_m60

I cannot test this right now but looking at this makes me wonder if it could actually be this easy to add 'M7' and 'M8' to the list of remap-able Mcodes (considering that according to the documentation 'M9' should not be a remap-able Mcode somebody already seems to have done or at least tried to do something like this)  :

 

thanks for the detailed step by step post, how to add an Ethercat AC Servo and test if it moves

thanks

I hope what aciera suggested worked for you. Did you select to install Linuxcnc 2.9 or master 2.10. Because I only used this procedure to install Linuxcnc 2.9
Master might require additional/different dependencies

Lass doch mal das G64 weg und schau wie es dann läuft.
Das war ja nur ein Beispiel, wie du es im anderen Thema nachgefragt hast.
Ich benötige das G64, sondern werden meine "außen" Ecken alle Rund.

Something important I forgot to mention in my previous message regarding converting block diagram to hal netlist.
 
Let'e take toggle2nist component, the way you extract the information from the symbol is as follows.

From bottom left is the name of the component toggl2nist.0 and you add the pin name in, we end up with toggl2nist.0.in same for the rest of the pins of this component ie toggl2nist.0.is-on toggl2nist.0.on toggl2nist.0.off

For the complete hal file we end up with this:
 

 

I've uploaded the kernel with some extra drivers.
I cannot do more about it, here it boots from my OPI5 and OPI5-plus, nvme and sata.

At some point the problem is going to be so annoying someone's going to do it, mostly looks like a lot of boiler plate.

I'm thinking using the m7 Pxxxxx format makes the most sense. I'll look into all the options and see if i can resolve on of them