Advanced Search

Did you have a look at this?

linuxcnc.org/docs/html/examples/mpg.html

This gave me the basic idea, and then I could change the *.hal according to the requirements.
To me it looks that this wireless thing just connects to the machine like a normal wired device.

I am not using an "official encoder input" for the MPG just normal inputs were doing the job, So I did not change the bitfile on Mesa card plug and go kit.

on my system, the gowin makefile works fine, are you sure gowin is running on arm64 cpu's ?

Ist das das gleiche Problem. Die X-Achse ist die lange Seite von dem Router, und die y-Achse die kurze Seite. Aber du schaust beim Arbeiten von vorne auf die kuzre Seite?

Gute Nachricht: es geht irgendwie
Schlechte: ich weiß nicht wie
Die Beschreibung ist wohl in Englisch. (das bekommen wir sicher irgendwie hin)

forum.linuxcnc.org/21-axis/14675-keyboar...-key-binding?start=0

p.s. das scheint nicht dramatisch schwierig, aber bevor ich da was verkünde probier ich das nochmal aus.
pp.s. ich bin stillschweigend davon ausgegangen, dass ein "Axis Bildschirm" (Software) verwendet wird.

Dieser hier!

I've been using the weekly builds for some time. TNP is not entirely solved, but I've slowly learned (after making some models for the third time) to be better at constructing models to avoid TNP issues. Worth the effort to reference things as far up the tree as possible, build reference planes, use parameter sets, etc. Overall I think the CAD is pretty good, once you get used to it. The last couple months leading up to the 1.0 release saw a huge improvement in stability, which is really nice. FAR fewer crashes. My only other real mechanical CAD experience is Rhino, so I can't really compare on that front- just being parametric is such a huge step up.

The CAM workbench in FreeCAD is both amazing and frustrating. It's awesome that it has (eg) adaptive toolpaths that you seemingly can't get in any CAM package under ~$3k USD. The new path/stock simulator is WAY faster/better than it was in older version. Plus, Linux native is great.

A lot of other things are maddeningly close to working well, but need some very specific workarounds to make work. Profiling open contours very notably falls in this category. You can make it work, but have to build a bunch of extra geometry to do so in my experience. It's on my to-look-at-fixing list...

On the up side, my experience fixing things (adaptive toolpaths not using the stock model you provide- pull request pending due to freeze prior to 1.0 release) was that it's shockingly easy. That fix took... a few hours, going into it mostly cold? So if you know Python and/or C++, and see something that seems dumb and annoys you, it might be worth looking into just fixing it.

 

I changed things up a bit from the cad model to work better with the materials I have laying around the shop. Hoping to have the mechanical side of things completed to run the table by the end of the month.