Advanced Search

After 15 years of google drive, and running a Synology NAS, I have moved to on site (at home) for all my emails and web sites. But I started using cloudflare for dns. Should I do that?

I am getting this right, the W5500 acts as an Ethernet bridge ?

So this should also work with the 7I90HD in spi mode ?

Or any Mesa SPI firmware (custom) like something I've put together ?

Lcvette wrote:

The standard qtpyvcp is not pi5 compatible, it requires a special build, this is likely why you're having issues. I don't use pi so I'm not the best source of help, I think rodw has a deb file build available, maybe he will chime in.

No can't help. QTPYVCP would need to support the Pi5 in its repository. Installing Debian 13 on the Pi might now be a solution but they don't seem to offer a img for the pi5. 

Great job. It just looks like a drawing .
How much did it cost to make that blue part?

I've decided to immediately apply a 1:3 reduction ratio, which translates to 25mm (15T) or 20mm (12T) of displacement per revolution.

I want to listen to the advice of  rodw and  tommylight

This will change the design somewhat. I think I'll place the linear guide directly on the underside of the tubes to reduce contamination.

Slowly, all the parts are arriving, and I've started welding the table. Unfortunately, I have limited time

– ETHERCAT DIGITAL & ANALOG IO BOARD
– 12x ISOLATED DIGITAL OUTPUT
– 12x ISOLATED DIGITAL INPUT
– 4x ISOLATED 0-10V ANALOG OUTPUT
– 4x ISOLATED 0-10V ANALOG INPUT
– 24VDC SUPPLY
www.egerobotics.com/ethercat-digital-analog-io-board

– ETHERCAT ENCODER INTERFACE
– 2x ENCODER CAN BE CONNECTED SAME TIME
– 1 DIFFERENTIAL LINE DRIVER ENCODER INPUT(5V)
– 1 TOTEM POLE ENCODER INPUT (5-24V)
– 24VDC SUPPLY www.egerobotics.com/ethercat-encoder-interface

There is now support for a Mesa board: eusurplus.com/index.php?route=product/product&product_id=131
It can be used via RPI over SPI and over Ethernet via W5500



There are also developments in the new configuration front end, but it is still far from complete.

PS: Many thanks to EUSurplus for their support!

Best regards, Olli

Tommy,

Oh ok... I still have my working 2.7 install... yeah lean't long ago to always keeps what is working.

I'll do the 2.7 install on the new computer and see if that works and it runs smooth.

UPDATE:

2.7 hates my Z420 Workstation... installs but runs slow and when I setup and Launch Linuxcnc program the window is blank with "no file" in the top title.

My old machine is a HP xw4600 Workstation and it runs Linuxcnc great but I thought I would "future proof" my setup with something "less old".

2.9 runs fine on the Z420 but just not usable with the way it runs the stepper motors.

If there is nothing that you actually need 2.9, you should have stuck with 2.7, so here is the ISO
www.linuxcnc.org/iso/linuxcnc-2.7.14-wheezy.iso
If you still want to try to use 2.9, you can try installing the RTAI kernel and corresponding LinuxCNC version from the downloads page, near the bottom of the page, all 3 last links on that page (not counting the link to COC).

It work now.

I was running 2.7 just fine but I put together a new system and installed the latest 2.9.4 and configured it as per the 2.7 settings but now the motion is rough searching for the endstop and even worse returning... actually dropping steps.

To diagnose if it was the new system... I put a new HDD in the old system and installed 2.9 and it's the same.

So I have to assume I tweaked something to make it run smooth last time... I do vaugly remember having this issue but it was years ago and now I can't find/remember what I might have changed?

I added the ini and hal files for 2.9 and the zipped files are from the 2.7 system that worked. Maybe someone can see an error or maybe there are differences between the 2 version of Linuxcnc I need to account for?

Any help on where to start would be muchly appreciated.

Oh my system is a MPS MicroMill 2000HD/LE  running the original Driver Box they where sold with.

 

If this is for a AC servo, the motor encoder needs to go to the drive for
commutation.

If the drive has a simulated encoder output, that is what connects to the 7I97.

The standard qtpyvcp is not pi5 compatible, it requires a special build, this is likely why you're having issues. I don't use pi so I'm not the best source of help, I think rodw has a deb file build available, maybe he will chime in.

Geany is not the same as geany in Linux, mind the upper case.
In the ini it should be geany all lower caseThe first line starts OK, the second shows the result above.