Advanced Search

the repo in the github configured like this:

you get:
4 step-generator
1 encoder-counter
gpio input pins (10, 11, 22, 26, 27, 28)
gpio output pins (12, 13, 15)
1 pwm channell (gp14)

so you can use it with a cheap printerpot breakout board. i currently working on a breakout board mixed with the io-samurai project to add +8 digital output and 16 digital inputs to this ().

but you can configure other ways if you want, more encoders for less inputs or no ecoder for extra 2 input or output. the hal driver uses the same configuration file so only 1 place change is need to change the configuration.

The configuration file is in the repo (firmware/w5100s-evb-pico/inc/config.h)

or if you want much more inputs and outputs use my io-samurai project, open source with the PCB production files. (only works with the W5100S-EVB-PICO or equivalent pico + w5100s breakout board)

if you want faster response please use the discord link in the repo.

 

 

Yes, that could definitely be the case. It's a very old machine—27 years old—but I decided I want to give her a new life. The structure is really solid, plus it has vacuum and lubrication for aluminum, which is great.
So, I want to do this retrofit, and I think the setup I posted here should get the job done. The only thing I have to do is adapt the old motor frames (they have a small gearbox), because the old motor is 89x89mm and the Leadshine is 80x80mm. I hope it won’t be too difficult.
Once the machine is up and running and I’ve done some work with it, I can swap the spindle and install an automatic tool changer. That would be so cool!

Do you have any general advice? Does the setup look good to you guys?
By the way, I’ve installed the LinuxCNC ISO on an old PC with an Intel i5. Now I’m just waiting to buy the Mesa board and start configuring everything.

Thanks for the replies, but some misunderstanding here.
The system is fine, up and running LinuxCNC 2.9.3, configured for the X-axis with joint0 and joint1 as it should be (cutting a big slab of 5 mm Alu while I am typing this). The only thing I am adding is a racking detector (for which I use encoder_ratio looking for a mismatch on encoder disks on both X axis).

While browsing through the HAL functions I ran into Matrixkins, and I wondered if this is not an easier way than changing some HAL values to square the axes. Since it does not apply to a tandem axis, I'll drop the issue.
But thanks for the replies anyway.

Robert

I was thinking 2 motors that move opposite to one another and increase the effective distance (one moves left 5CM, the other moves 10cm right; total displacement is 15cm)

Yes.
When mounted inside, the encoder wires have to go inside, and those are the ones most susceptible to interference.

No need, since 2.8 the joint/axis is implemented in LinuxCNC, so just choose "tandem joint/axis" in the wizard.

?? It is a usual setup, each X-ballscrew having its own stepper and home. For small corrections I could of course use HAL and change the HOME location a bit. The whole X bridge is very solid though (has 20 mm linear rail and two linear bearings on each side, and a profile of 160 x 95 mm aluminium), and pushing manually I cannot rack it more than about 2 mm. I have not measured yet if it is out of line more than that, so I'll do that first, might work. I found the matrixkins source, no mention of dual axis there. Looks modifiable though.
Robert

What about just connecting the 2 X-axes together, possibly with one of the DIR inputs inverted?

Hello,
i have a b - axis and i want to home the axis at the same time as the rotorhoming seqence is running (bldc component) 

I run a etel ddm with a 8i20 and a siko encoder with index

Any ideas?

Thanks

That ECP5/i5 board is VERY cool.

On your Git page you mention the network interfaces are not supported, do you mean we can't use a Wiznet module or are you referring to the 30pin ethernet connector on the dev board ?

Having over 100 IO pins available is definitely the dream, is programming as easy as the tang nano? Will it program via the USB-C connector within Riocore like the Tang?

Would there be any advantage in getting the i9 module over the i5 for our purposes ? It works out more expensive but not too much.

Cheers.
Russell.
 

Is it still recommended to mount the THCAD on the outside of the plasma power unit when the power unit has a voltage divider? I was thinking it wouldn't make much difference since the start and ok to move are coming directly into the electronics box.

Hello dear forum, (Translation GER-ENG Google)

Short introduction:
I've been a fan of LinuxCNC for over 15 years, and unfortunately due to a lack of time (I'm sure many of us have) I've neglected my hobby a bit in recent years. I'm a bit out of programming in HAL and am looking for some food for thought or a solution to the following problem: 

Compensation between B and C axis required. 
I built a rotary/tilt table for my milling machine. Since my installation space is very limited, the whole thing had to be relatively small.
Harmonic drives were used for this purpose, the shaft runs through the HDrive of the B axis to rotate the HDrive of the C axis. The whole thing is solved via belt drives. Since the motor of the C axis does not pivot, it rotates when the B axis rotates. Now I need a compensation that compensates for the position of C every time the B axis moves. For one revolution of the B axis I need about 1/51th of compensation at C. My idea is to compensate for the whole thing using moveoff. 

Are there already solutions that might be better, or has anyone done something similar?
I would appreciate any help and tips.
Kai

my hardware:
Mesa7i92, 2xMesa7i76, Mesa7i84, Mesa7i73
Homemade SK15 ATC spindle, Lenze FU
Homemade 3 axle + BC,



Hallo liebes Forum,

Kurzvorstellung:
Ich bin sein über 15 Jahren Fan von LinuxCNC, und habe leider durch Zeitmangel (haben sicher viele von uns) mein Hobby die letzten Jahre etwas vernachlässigt. Ich bin etwas raus aus der Programmierung in HAL und suche einen Denkanstoß bzw. eine Lösung für folgendes Problem: 

Ausgleich zwischen B und C Achse benötigt. 
Ich habe für meine Fräse einen Dreh/Kipptisch gebaut. Da mein Bauraum sehr begrenzt ist musste das ganze auch relativ klein werden.
Dazu wurden Harmonic Drives verwendet, durch das HDrive der B Achse läuft die Welle um das HDrive der C Achse zu drehen. Das ganze ist über Riementriebe gelöst. Da der Motor der C Achse nicht mit schwenkt, rotiert dieser wenn sich die B Achse dreht. Nun Brauche ich einen Ausgleich der bei jeder Bewegung der B Achse die Position von C Ausgleicht. Bei einer Umdrehung der B Achse benötige ich an C ca.1/51tel an Ausgleich. Meine Überlegung ist das ganze über moveoff zu kompensieren. 

Gibt es dazu bereits Lösungen, die evtl. besser sind, oder hat jemand ähnliches gemacht?
Ich würde mich über jede Hilfe und Tipp freuen.
Kai

meine Hardware:
Mesa7i92, 2xMesa7i76, Mesa7i84, Mesa7i73
Eigenbau SK15 ATC Spindel, Lenze FU
Eigenbau 3 Achs + BC, 

Having completed a new CNC build, I am fine tuning it. It is a dual X-axis machine (XXYZ), and I was looking at using matrixkins to square the X and Y axis. The document man9/matrixkins does not reference dual-axis. However I found a note (written in 2022): 
"Dual-axis gantry machine support might be worth adding, but I don't have such a machine myself."

Was there an update related to dual-axis use? Where can I find the source?

Thanks,
Robert
 

No one has asked for a specific facility for manual tool setting, which would start with specific procedure. There are a few common tool length strategies.

'Touch Z' usually implies _coordinate_ touch off which QtDragon has buttons for (REF and ZERO).
For tool setting, you can of course manually change the offsets in the tool offset page but also when you are on the tool offset page, the 'HOME' buttons change to 'TOOL' buttons.
Pressing that button will give you several options for setting the tool offset.

If you have errors with a base period (not frequency) of 100000 reducing it will not fix it, it will only make the issue worse.

What you will need to do is run a latency test and see how things are going.
The first error that shows in your picture is a latency error, that need addressing first, you will need to set a very high base period and slowly work backwards.

A base period of 500 would yield a base frequency of about 2Mhz, a 250000 base period would yield a base frequency of 40kHz. The larger the base period the slower the base frequency.

If you were getting errors at at base period of 100000 i would double this to see how things are, you may reach a stage where the base period is so high that the machine may not be usable with the hardware\OS combo.

At some stage you may have to get access to the BIOS.

Be aware that when timings are talked about they are in nano seconds, it does make things easier if that convention is kept.