Advanced Search

So stuff seems to work.
Next up is probing.
I have a tool setter on the bed..and an edge finder for in the spindle.
The 2 macro's work (should have copied them so I could include them here).
I mount the probe and touch it off on the tool setter. Then I manually direct the spindle to the workpiece corner and do the probe.
The workpiece corner is about x450 y400 z-23
When I then do a
G54
G1 x20 y20 f150
The spindle moves towards the machine home zero. Instead of 20x20 relative to the workpiece corner.
In the tool table G54 has coords like X25.645 Y62.956 and Z at 3.457
How?

Hello Tommylight, 

here my BIOS Settings.
Any Idea what I should change?
 
 

I will download the iso and try
What is the difference to the standard iso?

Thanks 
Erwin 

Also my Results for a longer measure period 
 


 

Hallo PCW,

hier die Messung für 10 Minuten 
Der Max Ping scheint relativ hoch

 
Grüße Erwin 

Can you run this and report the results?

sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10

(will run for 1 minute)
 

Try this ISO.
drive.google.com/file/d/12adxkk6DU2fTYJb.../view?usp=drive_link

Last latency test shows excursions beyond visible area, so the BIOS stuff regarding power saving and hyperthreating seems not disabled. All those must be disabled.

I spent my career trying to write reasonably efficient and fast code in firmware, device drivers and system level utilities. I'm afraid I just couldn't stomach adding a polling loop on top of the polling loop (every .2 seconds) that I discovered at the core of halui.

So I've done an end-run around the problem, which works nicely.

My mill runs from a Raspberry Pi, connected via a Mesa ethernet card. It occurred to me that if HAL could twiddle an actual gpio pin, then I could easily read that, and hook it up to action.  And of course if there's one thing the RPi has, it's plenty of gpio.

So I loaded hal_gpio, and hooked up a couple of output pins:
Those pins were chosen because they were eacy immediately adjacent to another unused pin.  Gpio 16 is next to 19, and 20 is next to 26.  I jumpered those two pairs.

Then I wrote a short script using gpiomon to watch pins 19 and 26 for transitions.
This works perfectly.

While I'm pleased to have found this solution, it sure seems silly to have had to consume 4 gpio pins in order to do it.

Thanks for all your suggestions!
paul

My guess would be some Ethernet data <--> FPGA transfer issue.
Does the Ethernet chip interrupt pin (EINT) have a pullup?
Drive = 4 on ECLK (for series termination)?

The firmware version is not really important as the fixes are minor
(LED issues, Addition of netmask, addition of MAC mask)
 

i've been playing lately with ethernet in linuxcnc. came across an interesting reading from intel: eci.intel.com/docs/3.3/development/performance/tsnrefsw.html

i've got an i5 gen11 mobo with i226-V ethernet controllers on it and my home brewed zynq7010 board with PTP-capable gigabit PHYs. working on a bare metal in zynq i have pretty good control over latencies. so i am trying to find ways to tighten linuxcnc's network jitter as much as i can.

intel's product brief mentions that:
Commercial and server versions (LM/IT) support the TSN standards and features and have been designed and validated
accordingly, and maintained as part of its product lifecycle, including AVNU certification. Non-commercial version (V) does not
support TSN; although some low-level features may be partially exposed temporarily, its usage is strongly discouraged

anyways, i patched RTAPI  to use CLOCK_TAI, and tried SO_TXTIME thing with an ETF qdisc. without much luck, unfortunately - the TX unit promptly hangs.
TAPRIO qdisc looks much better. seems to be working ok on my i226-V: with trial and error in setting up gates and IRQ affinity tweaking i am now consistently getting around 100ns rx time jitter on zynq with a flood ping running in parallel..

haven't found a proper datasheet on i226, will probably try do buy a i226-LM chip from mouser and solder it in. also will check i210, but it does not support TAPRIO offload. but maybe ETF+SO_TXTIME is working
 

Hi all,

It’s been 18 days since I posted, and unfortunately, there’s still no proper solution.Is the LinuxCNC wiki no longer being maintained?
It’s quite disappointing that essential post processors—crucial for CAM integration—are still unavailable, and broken links remain without updates. Are there any admins or contributors who could look into this?

@Grotius – thank you for trying to help, but unfortunately, the link you shared doesn’t seem to work as expected.

I’ve been a long-time LinuxCNC user and have always appreciated the flexibility and performance it offers. Recently, I invested significantly into a CamWorks setup (SOLIDWORKS-integrated), expecting to pair it with LinuxCNC as my trusted controller. Sadly, I’ve hit a wall due to the lack of a working post processor, and it’s a frustrating place to be after committing both time and money.

If anyone has a working CamWorks post processor it would be a huge help not just to me, but to many others in the same situation. And ideally, it could be restored to the wiki for future reference.

Thanks in advance to anyone who can assist!

Hallo zusammen,

leider bekomme ich immer noch die Watchdog Fehlermeldung.
Vielleicht hat noch jemand eine Idee?
PC ThinkCentre M91P (SFF)
Die Mesa 7i96s ist direkt am Netzwerkport des Mainboards angeschlossen.
Neue Installation von Linux CNC 2.9.4 vom offiziellen Iso Image.
Der PC ist nicht im Internet 
Folgende Einstellungen habe ich vorgenommen (siehe Bilder im Anhang)
Grub Parameter (nach dem Beitrag von @PCW) 
Netzwerkeinstellungen 
Gmoccapy Maschine mit Minimaleinstellungen 

Die Latenz Werte aus der Messung sind an sich in Ordnung. 
Die Probleme kommen erst beim Start der Maschine (wenn das Netzwerk aktiv ist).


Leider hat der PC eine Art Whitelist im BIOS. Eine gekaufte Grafikkarte wurde nicht erkannt erst bei der Ursachensuche habe ich von der Whitelist erfahren. Dort ist definiert welche Produkte akzeptiert werden. 
Deshalb habe ich Zweifel ob eine separate Netzwerkkarte überhaupt erkannt wird.

Vielen Dank für eure Hilfe 
Erwin 
 

I am currently in the process of adding a little rpi gpio support,
I'm only building this in so that I can use the local gpio's in addition to the FPGA,
but you can also use it without the FPGA, I don't know if that really has an advantage over manual configuration.
At least the tool takes over the calculation of the out/exclude masks.



Branch: parport_test (btw, parport support will be added soon, it's just difficult to test at the moment)

Hello, yes your editing is very interesting, don't hesitate to share the videos and share, I didn't know this operating principle, thank you

Almost there, just having issues using mesaflash to upload a config.

Erasing goes ok, but hangs at random points when writing.
Loading drivers via halrun works as expected.

Have tried with just writing to internal FPGA config & using openFPGALoader to write to flash.

mesaflash --device 7i92 --addr 10.10.10.10 --fix-boot-block --write some_file.bit

Had no issues with the EPP board, load into fpga config then writing with mesaflash was no issue.
Is there a particular version of etherhm2 (16,17 or 18) that needs to be used ?
Due to pin allocatons I have to build my own bitfiles.

      Hello, I finally managed to get Linux CNC to start with the HomeComp, but the servos aren't switching to OP mode. I've already tried to find the problem myself, but to no avail. In the folder "Drehmaschine_backup" is my first configuration, with which the motors already worked, but without homing. In the folder "Drehmaschine" is the new configuration with Homecomp.

Hello, for my part, I will buy CREATITY RAPTOR X, the basic version is about 1000 euros, the processing software often evolves, it seems very effective. if you really want to exploit your scans in CAD, I recommend 2 software GEOMAGIC DESIGN X (18000 euros!) or QUICK SURFACE (about 4000 euros), the latter are very practical to convert clouds of points in step or even in native file (design x > solidworks- see you tube )