Advanced Search

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

 

i am getting it with tool 199, this is a wierd bug, I am digging into it but im having trouble finding where its coming from. I am not finding any of the error information in the debug or any of the src files, I will report back when i find something more on it! thanks for bringing this to my attention!

I suspect you need to only enable the tristate when orienting
otherwise your digital output 07 will control index enable
rather than the encoder hardware for G33.

EDIT: Never mind, that does look like what you are doing.

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

hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2

You still have the Ethernet driver (hm2_eth) invoked in the hal file, you need the
RPI4 SPI driver (hm2_rpspi)

This might be better as a new thread, but this one was already made so I'll just tack it onto here...

Over the last year I've occasionally been adding new functionality to this 'weenyPRU'. The PC that was running my large router died so now I'm running it with a Pi4 and one of these units. Looking good so far.

The new features are:
- UART control of TMC2209 stepper drivers (set microsteps and phase current via HAL pins, can adjust at runtime)
- XGZP I2C pressure sensor (150Hz), will be used to sense vacuum pressure in my SMT pick-and-place
- DS3502 I2C digital potentiometer, currently using this to control the VFD of my router
- HX711 load cell amplifier (80Hz), will allow my pick-and-place to probe heights

The poor little F103C8 is now looking very busy, not sure if it can be pushed to do much more than this. Here's a scope of some load cell testing:
 

From your error report:
./CNC_V_Mill.hal:10: parameter or pin 'hm2_7c80.watchdog.timeout_ns' not found
6722
So just omit that line in the hal file and try again.