Advanced Search

  For me I don't have enough experience with FreeCAD to tell yet if something is a quirk of the program
or if it's something I didn't do. As I have said before I have used Fusion 360 for years. I don't dare mess
with nightly builds because I don't know enough about coding and I would probably make things worse.
That said I look forward to the day when I can throw Windows out the window. LOL

As I don't have an automatic tool changer so adding more vices helps a lot when doing larges batches of parts as it reduces the amount of tool changes I have to do.

You simple setup the program to do the same operation with one tool on all of vices and then change tool and make the next operation on all vices and so on.

With three vices and I can usually hold 3 or 6 parts at the same time depending on the size of the parts.

The mill is fairly rigid and can take pretty heavy cuts as can be seen here:



However the limiting factor when milling the v-band chill/purge block is the long skinny tools I used and the slow spindle speed of this machine.

The long tool stickout leads to tool deflection which greatly reduces the width of cut that can be used.

Small tools require higher RPM and the spindle of this machine is only designed for a max rpm of 3000 which leads to very slow feed rates when using small tools. As you see in the image you attached it doesn't even have a feed rate listed for a spindle speed as low as 3000 rpm when milling aluminum.

timo wrote:

pp.s. ich bin stillschweigend davon ausgegangen, dass ein "Axis Bildschirm" (Software) verwendet wird.

 

Wenn ich von seiner auf Seite 1 geposteten INI ausgehe, benutzt er Probe_Basic als Screen
und soweit ich weiß, ist es nicht trivial den Screen zu ändern (Phyton).


Gruß
Olli

@ Zayoo: I have the same problem with the toolchain on the Pi5.

However, you can use the IDE on a Windows PC. Just copy the files from Gateware and open the project file with the IDE rio.gprj. 

By the way, I am wondering what the maximum SPI speed on the pin headers of the Raspberary looks like to ensure transfer without errors. These are not suitable for very high frequency. Hence, even if the hardware can run very high frequency, the pin headers are the limiting factor.

What is the required SPI frequency to run the Iceshield?

@ meister: Great. Thanks.

Hello,
i have a issue when i press the Estop button (when i turn on the maschine).
My progress is -->open LCNC, hit Estop to turn on the machine, Hit the machine ON button and after i have to home all axis.

So my issue is when i turn on the machine (all the positions are 0) and when i hit the Estop, the coordinates change always in different position.
I would be thankfull if someone could help me with that.




 

 The machine looks very good. Does more than one vise add a lot to a hobby machine?

I change setups a lot and sometimes clamp direct on the table or use a 3-jaw chuck.

How rigid is that optimum mill? I would have thought you can push it a little more:-). Chips will fly everywhere.... next up! "Full enclosure"

Table is from a carbide endmill catalougue.



Greetings

Ciao.

Meanwhile, congratulations on the good work.

I am also Italian and have been working with LinuxCnc and Raspberyy for a long time and I took care of its translation into Italian.

www.youtube.com/@cnclab-unipa939

In particular, I think you might be interested in these links

forum.linuxcnc.org/9-installing-linuxcnc...-io-pins-only#203365

forum.linuxcnc.org/9-installing-linuxcnc...-pi-5?start=0#285239

If you want I can give you other directions

MiniMonster's bigger meaner brother progress.

This machine already exists, but I need to modify it and repair some flood damaged parts. *finally* all the parts seem to have come my way to get it back going.

I am going to use the sanyo denki servo sets I originally bought for my brother machine. They run on either analogue or step and direction. I already have a mesa 7i77 for analogue use.

Does anyone have any opinions on whether I should stick with that, or move it to step and direction. There are a number of benifits to going with analogue, but my last experience tuning analogue servos on linuxcnc went poorly. These are very different drives this time though on a very different machine.

Drives are sanyo RS1, and the motors are sanyo P5 with 2000 line encoders.


 
 
 
 
 
 

I updated from LinuxCNC 2.9.2 to 2.9.3 along with latest version of Probe Basic yesterday.

Everything went smoothly and I decided to attach a camera to the mill so that I could record some milling.



Overall the macine works great but I really need to upgrade the BT40 spindle so I that can run at higher rpm's. It would significantly cut down the maching time if I could run 6000-10000 rpm instead of the ~3000 rpm I'm currently limited too.

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.