Advanced Search

That is pretty awesome.

Damn so I cant use the Olimex iCE40HX8K-EVB ?

So I will have to get a new toy ?
Will the others get jealous ?

sys/io.h has the functions for ioport access on the x86 arch.

Can you use the debian arm64 packages ?

From what I've read the best way to do this is not to cross compile but to compile in an emulated environment via qemu.

I've done for the Rpi4 by copying theRPi4 file system to directory then chrooting into it.

Here's some info about the procedure
wiki.debian.org/QemuUserEmulation

If you have a link to a filesystem image i can have a look for you.

Since I use more and more the Servo42/57 drivers and play around with robots and many axes,
I thought I'd make a new board so that I don't have so much cable clutter
and everything is relatively compact.

 

ok, 8 axles is not really necessary, but my Parol6 has 6 axles + a servo gripper,
if I put a stepper gripper on it, I'm already at 7, so the 8th doesn't bother me any more

* 8 x opto inputs (5/24V can be installed in 2 groups)
* 8 x outputs (5/24V can be installed in 2 groups) / can also be used as PWM/RC servo output
* 8 x stepper axes
* 3 x encoder inputs with index pulse (3.3Volt level)
* 2 x I2C ports (3.3Volt level)
* 1 x modbus-rtu
* 1 x WLED output + one ws2812b onboard
* 1 x PMOD socket
* Current and voltage monitoring via ADC's
* Size: 100x100mm
* FPGA: eu.robotshop.com/de/products/devantech-icewerx-ice40-hx8k-fpga (plugged on)
* Ethernet: wt32-eth01 (plugged on)

I'm not quite finished yet, maybe you or I can think of something else that might be missing.

I chose the FPGA because it is fast and relatively cheap to get in Germany.
The Ethernet board is also cheap and extremely stable.

The board can also be used for milling machines and lathes,
Initially, I wanted to put a standard NEMA17 driver socket on it,
but that would have been too big.
Maybe I'll make an add-on board with space for the drivers.

For my next trick: O-1 tool steel (soft).



This is the first proper "sample part" I am going to video to market the new machine. Just waiting on my 4mm end mills to come today or tomorrow I hope.

I expect only one real issue with the fine surfacing on the steel and that is the lack of jerk control and stepper tuning. It will probably leave marks at transitions is my expectation.

All banned.

Customs will seize them if they find them and you can genuinely go to jail. There's no messing around here.

Also, for clarity these are machines I will sell to customers. So no used items for rando chinese inverters, even if it was legal.

Hey, everyone!
I am installing LinuxCNC on an ARM64 board (the core module is TI AM6254), and the board uses the premeet-rt kernel. I know I need to use cross-compilation, but I don't know how to proceed. My operation sequence is as follows:

./configure --prefix=~/Desktop/linuxcnc/linuxcnc-build/ --build=i686-pc-linux --host=arm-linux  --enable-static --with-realtime=uspace --enable-non-distributable=yes --with-libmodbus --with-libusb-1.0 ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu
make 
make installThe terminal prompts me that there is no. in rtapi/uspace_rtapi_app.cc
How can I should do? Looking for ur reply.
 

About VFD 1000Hz and more, delta series MS300 and MH300 are available up to 1500Hz. If it is possible to buy used Danfoss 2800 and 2900 series also up to 1000Hz. And so there are many chinese manufacturers, there saw up to 6000Hz.

Leadscrew ptich is required or the numbers mean nothing (or if belt drive belt pitch)

Technically an inch is actually defined as 25.4mm, this came about in the 1930 or so as different regions had different definitions. The development of slip gauges or "Joe Blocks" had a bit to do with this.
I still can't understand why some regions of the world will attempt to use anything to avoid using the metric system......Yes it's as big as 3 football fields and as deep as 4 school buses.

en.wikipedia.org/wiki/Inch

Tho it makes no reference to slip gauges.

with su you are required to have\know the root password.
sudo only requires you to know your root password.

Latency can be improved by adding isolcpus=2,3 to the kernel command line.The location of the file that needs to be edited is under different directories of /boot depending if you use a pre made Linuxcnc image or install on top of a Raspberry Pi Foundation image. With the RPi Foundation images I use rasp-config to switch from wayland to X11.

I'm not sure what the exact figures are for mesa hardware stepping are but they are way more then you would ever need/find a stepper driver that could use a pulse train that quick.

Be wary of the DIY projects, they are excellent, but sometimes assembling all the hardware required for voltage level translation, coping with differential signals for encoders can come close to Mesa hardware. If you have experience in this field it can be done, I've been down that track, adjusting Mesa source code to suit a dev board and then designing hardware to suit and getting PCBs made then patching Linuxcnc drivers to work with my DIY stuff.

With regards to the latency tests with hardware stepping the constraints aren't so tight, but there is an upper limit.

If I was to try software stepping my list of candidates would be(also some notes on usable interfaces for the RPi models):
1. An x86 system, 4 core if possible with a RT_PREEMPT kernel, for 2 cores maybe a RTAI kernel. (A PC and a parallel port card can be cheaper than an RPi)
2. A RPi5 as this is overall a faster product than the RPi4, but it wont support hardware stepping via SPI. TLDR; the Linuxcnc driver to access the SPI at the hardware level needs a rewrite. Ethernet hasn't been seen to be a problem.
4. A RPi4 (or even better because of a slightly faster clock an RP-400) but don't expect the the machine to excite the world. Spi interface is an option as is Ethernet is also fine for mesa boards.

Be aware that some DIY SPI based options require a servo & base thread, whereas the 7c81,7c80 & 7i90 do not.

2024/06/27
re raspberry pi and software stepping:

There are two ways to install LinuxCNC discussed in this thread.

The first is to use an ISO image mentioned in the official getting started guide.
Te second way is to the old a system as described by user aso_tm.

The iso solution users wayland and has no screen capture or synaptic
and makes installing synaptic difficult
Also most LinuxCNC apps appear several times in the menus.
All together, these features made me want to build the system.

The second method (ago_tm)
requires additional flags this true the apt install commands
to overcome not trusted sources errors.
Also, gebrated debs involve permission problems
for some me user who is neither me nor wrote.
Beware that the 'copy me' aid copies the $ prompt too.
Getting the build to complete requires several restarts
The first start will show you the error
and the second will hopefully will succeed after modification.
The changes will be to the last line of the copied multiline command.

But, the bottom line is...
neither solution will give you reasonable software stepping
due to huge latencies, between 3 and 7mS (yes mS)
Using latency-histogram --no-base
with 10 glxgears abd 1 youtube vid
OR one VLC vid. ( similar to ago_tm's testing)

So the raspberry pi( my version for) he's not suited to software stepping
and the contributors to this thread suggest using a hardware step generator.

I ask:
1) iI a hardware step generator is used
are latency test meaningless?
Do those tests identify no constraints on the control system?

2) What steps per second can be acgieved?
( my case would be for an rpi4B 4G)

Thanks tjtr33 / tomp

written with nerd-dictation
huh

Anndd... some 4140HT.
I should have set up the camera, but honestly I thought it would fail.

Anyone making a small machine regardless if its for wood or metal: A quality spindle changes the machine entirely haha. Do not skimp on the spindle.

 

Hi daveyr,
Sorry for reviving this thread but I am working on setting up my mill to use the same smartmer/2 probe guard that you used. Is it still working ok for you with how you integrated it into your probing routines? Also, would you mind sharing your default.ini file? Also, can you share how you hooked up the smartmer/2 to your controller? The probe works great but the documentation is not the gratest with regards to how the guard function works.  Thank you for sharing.

-Sean
 

LINUXCNC - 2.9.2
Machine configuration directory is '/home/linuxcnc/linuxcnc/configs/linuxcnc-cia402-main/.'
Machine configuration file is 'cia402.ini'
Starting LinuxCNC...
emc/iotask/ioControl_v2.cc 888: iov2: can't load tool table.
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(REL): ./cia402.hal
lcec_conf: ERROR: Parse error at line 4: not well-formed (invalid token)
./cia402.hal:9: waitpid failed lcec_conf lcec_conf
./cia402.hal:9: lcec_conf exited without becoming ready
Shutting down and cleaning up LinuxCNC...
iov2: exiting
Note: Using POSIX realtime
LinuxCNC terminated with an error. You can find more information in the log:
/home/linuxcnc/linuxcnc_debug.txt
and
/home/linuxcnc/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal

Hey Guys. I am new to this forum, but I've been a longtime lurker. I just finished documenting my repair of a 1990s Millport CNC vertical mill from a non-functioning brick to a floppy-wielding chip thrower. Even though this is a Bridgeport clone machine, it is surprisingly stout and has all Anilam controls with Baldor servos. I detailed the entire troubleshooting process and PCB level repairs needed to make this DOS based servo-drive CNC shift some 1s and 0s and throw chips again:

salvagedcircuitry.com/90s-cnc-revival.html

I thought you guys might get a kick out of this repair even though I decided to repair the controller and not switch to LinuxCNC. I was seriously considering it for a while, but I wanted to give the stock electronics a fare shake before I decided to jump headfirst into a retrofit. This is an early 1990s intel 486 computer based CNC, and while it's old, it's still capable. I included some video of it working toward the end of the writeup.

Let me know what you think!