Advanced Search

Oh hang on you have a working Linuxcnc install ?

If so you can use that to make the USB stick.

This is a very comprehensive article on how to do that
www.cyberciti.biz/faq/creating-a-bootabl...k-on-a-debian-linux/

Or you can search for WSL dd to USB.
WSL is windows subsystem for linux

learn.microsoft.com/en-us/windows/wsl/install

I forgot, do they have step/dir inputs?
If yes, then yes, they can be used with Mesa or parallel port.
Also, mind the power requirements as they do require 5V and 12-24V (or more).
Edit:
Just checked and yes they do have step/dir pins, so yes they will work.

The image needs to be written to the USB stick byte by byte. The ISO format does not have a partition scheme.
I would have looked into why the program wouldn't run

A properly written USB stick for booting Linuxcnc does not have a "partition" scheme.
I think Belana Etcher has a "raw mode" that writes the image file to the USB stick as win32diskimager would.

Hello,

Since you don't describe your detailed workflow, it's difficult to answer correctly.
There may be an offset entered in the tool table, but it's not actually necessary, since the tool length doesn't matter with this procedure.
For my part, I have put together a few routines that do a manual tool change with automatic measurement.
The whole thing assumes that there is a tool in the spindle at the beginning, regardless of whether it is actually used or not, and that this is measured and then used to measure the workpiece height.

I hope I'm doing this correctly.

Many greetings, Frank

That did not boot. I am trying to boot from DVD again. Is there any upgrade path from 2.7.15 to the modern versions that does involve booting an ISO? This desktop is apparently a legacy BIOS.

Unfortunately, "The code execution cannot proceed because Microsoft.UI.Windowing.Core.dll was not found. Reinstalling the program may fix this problem." It did not.

Trusting CoPilot, I am burning the ISO to USB again with MBR partition scheme.

Looks fine, will work just fine.

TL;DR: Can I wire these little TMC2226 (or similar) 3d printer stepper drivers to a 7i96?

Before you laugh I know it seems like a silly matchup. I've been out of the cnc game for a few years now but now I have some projects on mind some I'm trying to plan to reuse some old parts. I'm still fairly out of the loop on the advances made in linuxcnc and hardware since.

I want to build another one of these light weight "3d printed" cncs . By default these machines used arduino/grbl based controllers , but I enjoy linuxcnc so I fully intend on on using linuxcnc instead.

I have a NIB Mesa 7i96 that I never put into production .  I have some raspberry pi 4 Bs laying around from old projects. I would need to find new stepper drivers. These tiny stepper drivers are proven to work fine for these machines. I like the idea of cost and especially space savings with these little chips, and how the original design of the above linked machine integrates their electronics into the gantry. 

So can I just wire these TMC2226s into the 7i96 as a drop in replacement for something  like my old TB6600 s?

I don't quite understand yet if these little chips with all their pins, and uart mode, are a different animal than the old stepper drivers I used before.

PS. I'm excited to find out that there is an official release for the rpi. I've already flashed it and have been poking around in it.

daveansell2 wrote:

once I home the machine on the last joint to home (1) it stops being able to move in one direction on all axes. If I try and move it in the other direction it doesn't move. 
    

Can you try again explaining that as it does not make sense to me, or even better make a video and upload to youtube.

I am having a strange issue I have been running a CNC router with a dual motor axis for a while very happily and have just put in a second limit switch on the dual axis so it unracks itself on home in case it gets out of square, and have a really odd issue.Before I home the machine all the non-dual axes work fine (though it won't let me use the dual axis, which is annoying), once I home the machine on the last joint to home (1) it stops being able to move in one direction on all axes. If I try and move it in the other direction it doesn't move. 

I am attaching the previous version which uses a different config of limit switches, and seems to work fine - davemill-vfd.hal & davemill-vfd.ini
The new config is davemill-vfd-ind.hal & davemill-vfd-ind.hal

Does this make any sense to anyone?
   thanks
 
*** SOLVED *** see my post below

sure: This email address is being protected from spambots. You need JavaScript enabled to view it.

i made an support request (issue) on git...

"Support for additional device ID (0xeb91) for XHC-WHB04B-6 clone (EDING CNC rebrand)"

Thanks for the report, this is fixed.

JT

We have already added at least one extra ID. Should be easy to add more.

github.com/LinuxCNC/linuxcnc/pull/987

I would rather expect joint.N.motor-pos-cmd to re-init to the current encoder feedback value (joint.N.motor-pos-fb) on restart.
Maybe you have a missing HAL connection?
It's probably worth halscoping / halmetering those pins (and others) to see what is happening.