Advanced Search

Its steel actually.

Made it. Not hard!

Have a few of them in the shop. Made out of solid 2" (50mm) plate offcuts from the scrap dealer. I had them blanchard ground. Just mag drilled and tapped the M16 holes. Cheap and flat fixture tables. I've built some very straight motorbike and push bike frames on them over the years.

Thanks for the heads up on the switches. I'll keep this in mind.

you need a network switch to connect

Poke poke
I'm trying to get my omron servos working here and it doesn't give the 90 error now, however it is giving me an 83 error which is also communication related.

I am starting with a very basil xml and using halrun to test things.

Any thoughts?

 
if you use normal pico and a w5500 board, you need to wire like the dark blue pins in the w5100s-evb-pico, pinout here w5100s-evb-pico pinout new video here Embeddedtronics testing stepper ninja

I'm planning to switch my 3-axis mill conversion from Masso to LinuxCNC using Pathpilot.
I ordered a Mesa 7i96s board. I ordered that board because a friend is also running Pathpilot on his router but he's using a 7i96T board.
Hoping to confirm that the 7i96s board will work for me.
Thanks in advance.

You say the PI pico connection (connections like in the w5100s-evb-pico), but the Pico pins are different for the SPI0, or am I wrong?
I have another question: if I'm going to use your io-samurai, would I need another network card?
 

Use " Halshow " to check that the spindle.1.xxxxx pins are doing the right things, and trace the signals from there.

yes that's how it is.

Yes, if the touch probe uses a contact to ground you can use a pull-up
resistor as Andy suggested.

For 7I76XX inputs this needs to be fairly stiff, say 2.2K 1/2W

This is because the 7I76XX input resistance is 11K and needs an input > 14.4V
for a high level at 24V Vfield, and a 10K resistor will not do this.

Do you want to replace like-for-like or swap out for a LinuxCNC conversion?

not currently, but its on the list

yup, from memory the probe led is a good example, forgot about that one

M62 and friends need connections in HAL to have any effect. Do these connections exist? (motion.digital-out-NN etc)

As far as I know nobody has done this yet, but the change that allowed one to use a custom homing component was put in to support this type of scale.

How's your C coding?

www.linuxcnc.org/docs/devel/html/man/man9/homecomp.9.html

github.com/LinuxCNC/linuxcnc/blob/07cee8...nts/homecomp.comp#L4

However, I don't know if that is strictly necessary. I think that it _might_ be possible to craft a custom HAL component that outputs an encoder position and handles index_enable. This would take the encoder counts as input, and also manipulate the index_enable pin of the encoder counter. (I think it would be necessary to use the position-latching facility of the software or Mesa encoder. I _think_ you can set index-enable, which will zero the counts when the first index is seen, then re-enable index-enable and look at the counts-latched pin when index-enable resets on the second index. But I have not tried this.)

The component would then reset the index-enable that the homing system sees, and pass the correct position into the system. (Note that the "correct" position might be the inverse of the actual position, in some way. The position-after-index-enable is used by the system to calculate how far the current position is from the home position.

component inputs:
index-enable - to / from motion system
encoder position - from encoder counter
position-latched - from encoder counter

outputs:
index-enable - to manipulate the encoder counter
encoder-position - an offset version of the encoder position input

I do have a Heidenhain scale, but i have never done anything with it, and don't know if its a type with encoded index marks.

andypugh wrote:

Yes, it's probably best to turn off CSS when threading. 

Andy,

I wasn't using CSS when threading.  Multiple attempts at tapping the same thread at different speeds resulted in different start points.

What I discovered (through @Aciera's help) was that caxis.comp interfered with threading/tapping, and that LCNC has a bug in G33.1 and G76.

forum.linuxcnc.org/38-general-linuxcnc-q...peed?start=30#317931