Advanced Search

Hello,
i just try to complete the function in the attached file. My postgui.hal:

#[Startknopf]
loadrt or2
addf or2.0 servo-thread
net Start.ext.an <= gladevcp.Start => or2.0.in0
net Start.ext.an1 <= hm2_7i76e.0.7i76.0.0.input-04 => or2.0.in1
net Start.or <= or2.0.out => hm2_7i76e.0.7i76.0.0.output-05 => gladevcp.led_Startstopp => halui.machine.on

#net Start.or => gladevcp.Start-not => hm2_7i76e.0.7i76.0.0.output-06 => halui.machine.off
#net Start.ext.aus => gladevcp.Start-not => hm2_7i76e.0.7i76.0.0.output-06 => #halui.machine.off

I can´t get output-6 and halui.machine.off to work.
Please help

Thanks, that works

toyssss

 
 
 
 
 
 
 

The Linuxcnc-RIO\riocore has a max6675 plugin.

github.com/multigcs/riocore/blob/main/ri...ns/max6675/README.md

That doesn't always happen.
I used to distribute an ISO based on Mint 19.x & build packages for installation via apt.
Tommy has a later Mint based ISO, if memory serves me right.
There has been a couple of Raspi OS based images for the RPi platform as opposed to the Debian based image that forms the official image.

The code base used to build the current image is a fork from the linxcuc live-build repo.

In another thread I posted links to test images, based on my findings regarding the raspi-firmware issues, unfortunately no one, it would seem, downloaded and was able to test the images. It was clearly stated that they were test images only and not to be used for a production machine.

I did state in my initial thread that I wanted to open a dialogue with regards to building a new 2.9.x based ISO.

Machine Kit was a fork of Linuxcnc, worked well on a lowly powered BeagleBoneBlack (1Ghz & 512MB ram) and was able to use the in built micro controller for step & direction generation worked quite well on a 3 axis mill, unfortunately development on that project stalled.

@langdons "not some random offshoot side project fork" . Oh the irony.

For isolcpus:http://wiki.linuxcnc.org/cgi-bin/wiki.pl?The_Isolcpus_Boot_Parameter_And_GRUB2

For pinning the IRQ there is a script for testing here: 

 

to run, first download the script then:

chmod +x pinirq.txt

then

sudo ./pinirq.txt [ethernet_device_name]

 

Can you explain how to do it?

Now I just need to configure the INI to mm and the speeds. I'm getting errors from

hm2/hm2_7i965.0: stepgen.00.maxvel is too big for current step timings & position-scale, clipping to max possible

Another cheap option for reading thermistors is LM331, a voltage-to-frequency converter
www.ti.com/lit/ds/symlink/lm331.pdf?ts=1760588182451
Or an industrial solution by Mesa, the THCAD

anli wrote:

Hi,
I used Debian 12 LinuxCNC image to install LinuxCNC. Afterwards I updated to Debian 13 as shown here in the forum

                          
Holen:7 https://www.linuxcnc.org bookworm InRelease [31,1 kB]                
Fehl:7 https://www.linuxcnc.org bookworm InRelease

The "bookworm" there should be "trixie" You need to change the distro name in /etc/apt/sources.list.d/linuxcnc.list

To address the key length issue (which, oddly, didn't seem to effect my Trixie installation) I have created a new, longer key and signed the trixie repository with it (I _think)

The new key can be found at keyserver.ubuntu.com/pks/lookup?search=L...gerprint=on&op=index

But the best option is probably to use a new version of the LinuxCNC install script which will install the keys then install LinuxCNC.

www.linuxcnc.org/linuxcnc-trixie-install.sh

This can be downloaded (right-click and save-file-as), made executable ("chmod +x linuxcnc-trixie-install.sh") and then run ("./linuxcnc-trixie-install.sh")

I would very much appreciate it if folk could try this out before I properly announce / release it.[/code][/quote]

Normally the DKMS 8168 driver will fix the Ethernet latency issues

If it's not sufficient, one additional step to do is to  use isolcpus
to isolate the last processor and then pin the Ethernet IRQ to that
processor.
 

I have executed this in a terminal:
sudo cyclictest -l 10000 -m -p 80 -i 1000 -q -v

He has given me this:

0: 9996: 2
0: 9997: 2
0: 9998: 2
0: 9999: 2
T: 0 ( 2995) P:80 I:1000 C: 10000 Min: 2 Act: 2 Avg: 2 Max: 7

It seems that by switching to r8168, I am no longer getting the error.

I currently have 3 axes, but I will be installing 5 simultaneous axes. Is it advisable to change the network card?

So what is it due to?

Should I change the network card?

For this: www.amazon.es/Euqvos-Gigabit-Desktop-PCI...ef=asc_df_B09SXXYV4R ?

Thanks for the long reply. I've been doing this long enough to know that that a good bug hunter is worth their weight in gold.

> I am not sure when you'd actually want to use cutter comp, I've always just relied on the CAM to offset the paths for me

I don't fully understand what you mean there since in this scenario MetalHeadCAM is the CAM. Do you mean that you normally offset it in CAD? Or that you use G40/41/42 in gcode? FYI, support for LinuxCNC's native offsetting via G40/41/42 will probably come in the next release.

I added offsets for a few reasons. 1) visualize the actual cut path 2) possible future support for controllers that don't have G40/41/42 3) eventually support true arc and NURBS offset paths since LinuxCNC G40... only does lines.

> I am unsure what all of your goals are for the project, but if you need inspiration, SheetCAM is a pretty good software to try and emulate. I cant think of much I would want to do that it does not. It's nice to have free options for sure!

I currently use SheetCAM. It's great, but I don't love the interface. I also think that $279 is too much for most hobbyists. I'm also an open source maximalist so it will forever bother me that I have a closed program in my workflow.

The rest I'll reply to in order:

1. I'm going to add some sort of documentation to the landing page on this. You're not actually uploading anything. MetalHeadCAM runs as a Javascript app in your browser. There's literally no backend to upload to; it's just HTML and Javascript delivered via a CDN. At some point I'm going to make it available for download as a fat HTML page so that you can run the whole thing offline.

2. I've just deployed a new version that has first-class Imperial support. At first I wasn't sure if I should stop with the Norman conquest, or add cubits too. Go to the hamburger menu > Settings > Reset Application before trying it again because you'll need to wipe out the old metric-only state.

3. I need to scale zoom factor based on size. That's on the TODO list.

4. Edit and Prepare stages are gone now.

5. Tools are in hamburger menu > Tools. I need to get rid of the hamburger menu as that is really a mobile thing.

6. Rapid speed is in Simulation now.

7. There's now a Select All button.

8. Fit is gone. That was an experiment.

9. Should be fixed. Normals calculation needed improvement.

10. Should be fixed. There was a bug in spline tesselation.

11. This one is admittedly confusing. Default is Part because it implements "the kerf always be toward the scrap (or away from the part)?". Allowing the user to set Inside and Outside is just my way of avoiding making a hasty assumption.

12. Not sure what was up with that. I can't reproduce it.

13. Acknowledged.

The only reason I asked about the CPU frequency is that the tmax values are in CPU clocks
(on X86 hardware). Knowing the CPU frequency allows the times to be calculated.

I have installed: 8168 driver

When I enter this in the terminal:
cpufreq-info | grep "current policy"

I get this:
current policy: frequency should be within 800 MHz and 3.20 GHz.

I cannot change to a constant 3.20 GHz.