Advanced Search

Yes, reverse feed is possible and also used in EDM machines that use linuxcnc,

 

Hi all!

I've been trying to use wiznet w5500-evb-pico as step generator for linucnc.
I was successfull loading remora-rp2040-2.0.0.uf2, from github.com/scottalford75/Remora-RP2040-W5500

But, when trying to compile, i was less lucky:

/tmp$> cmake -DPICO_SDK_FETCH_FROM_GIT=on ./Remora-RP2040-W5500-main/
/tmp$> make
I've got some include errors like: pico_bootrom/bootrom.c:9:10: fatal error: boot/picobin.h: No such file or directory
#include "boot/picobin.h"

The same for: runtime_init.h,runtime.h
But those files are available in the sdk source.

My Q&D solution was to copy locally to complete the build.
After that, the build made a loadable uf2 image.
But the rp2040 has been crashing during my tests.

Suggestions?

Gluca.

Was this on another topic a while back, or is it another setup/machine?

O.M.G. - I should RTFM

spindle.M.revs IN FLOAT
For correct operation of spindle synchronized moves, this signal must be hooked to the position pin of the spindle encoder.

Ignorance is NOT bliss.

PCW wrote:

It should still work with the tristate bit connected, as long as the tristate enable pin is false.
 

Thanks, I'll reconnect it.

Shocking development: I've managed to get the spindle orienting without using the shot-pin, and without having to set index-enable true and rotate the spindle to re-find the index.

Based on Andy's advice a couple years ago, I had connected pid.o.error to pid.o.Pgain through a lincurve array.  After watching things in halshow today, I discovered that Pgain wasn't changing in response to the orient error; i.e. lincurve wasn't doing anything.

Turns out I had the lincurve starting x-values set to an order of magnatude smaller than required for lincurve to adjust the output.  Result was that lincurve didn't 'kick-in', ever.  The shot-pin was required to lock it in place because the pid wasn't adjusting - just causing the spindle to wag back and forth.

After changing the values and connecting pid.o.index-enable the spindle now orients from any position.  No shot-pin, no pre-orient spin-the-spindle index-enable dance.

Sadly, this hasn't fixed the rigid tapping failure.

It should still work with the tristate bit connected, as long as the tristate enable pin is false.

The index-enable is getting cleared when the index pin goes true.

Just tested that by disconnecting the tristate_bit and manually setting the index-enable signal high and running the spindle for a second.

If you manually set the index enable signal true
and is is not over-driven by some other source,
it should get cleared at the index position by the
physical index signal. If this does no happen, you may
have a hardware issue with the index signal.

I think I just found the point in history where I blew past the fact that pid.o.index-enable needed to be connected to something.

forum.linuxcnc.org/24-hal-components/458...-yay?start=40#245756

 

LinuxCNC can do this on it's own, easily
forum.linuxcnc.org/show-your-stuff/50177...ny-solder-bot#314119
No need for cams, just a simple lathe with spindle encoder.

PCW wrote:

Is motion-digilat-out07 false when you try to rigid tap?
 
 

Yes, digital-out is false when I try to rigid tap.

I haven't set up halscope to try to catch an index pulse or other brief signal, but the index-enable signal doesn't go true when I try to rigid tap.

EDIT - Minor troubleshooting update

I disconnected tristate_bit from motion-digital-out in halshow and ran a short tapping program to see if digital-out was holding the index-enable pin/signal false.

No change in behavior - spindle just spins & waits.

While it was spinning, I manually set the SPINDLE-INDEX-ENABLE signal high and all the nn.index-enable pins went high.
encoder.00.index-enable
pid.s.index-enable
spindle.0.index-enable

No change in behavior.

I did discover that I don't have pid.o.index-enable connected to anything.  I don't know if this is related to the tapping problem, but I wonder if it's the reason I had to do the tristate_bit gymnastics when I set this up a couple years ago.  IIRC, during orient attempts the spindle would just spin and nothing was triggering the index point.

Now we have control of TMC drives through UART, apparently:
forum.linuxcnc.org/show-your-stuff/50177...ny-solder-bot#314119

iforce2d wrote:

- UART control of TMC2209 stepper drivers (set microsteps and phase current via HAL pins, can adjust at runtime)

I am sure the form member 3dtech_ks will be very happy for this, he has a strange obsession with TMC drives and printer boards!

found something, a clue but not the reason why, i suspect its a remnant edit from working on the tool table database mode, running a comparison to see where we broke it, looks like its not reading newly added tools at startup which triggers the error message because the tool isn't read into linuxcnc at start up. will update when a fix is up.

Hello everyone! I'm hoping for some insight on linux cnc if this could be the right choice for my end goal, I have and old cam machine Im hoping to retro fit with a cnc control to elimate have to design and cut new cams for each part, I have a decent understanding of the machine and how it works. Tho I have never tried something like this tho (a cnc intergration)
The machine would be 2 axis z,x it has to fixed tools that simply swing in and out on a tool head that work oppsite of each other 1 goes in 2 goes out vice versa.it has an 8k spindle Also a 4000 rpm material straightening unit. with a carriage that move foward and back. 
The timing is all done by cams, belts and chains. 

Is building a system like this something I can do with linux cnc? Is this a feasabile project for intergatation?
Any resources I could check out beyond this site maybe people who have attemped similar?

Any tips, information and thoughts would be welcome 
attached is a photo of a machine similar to what id want to retrofit