Advanced Search

Thanks for your quick reply.

can you enlighten me as to how you found that out? what lines in the hal can i modify to get them correct? Also can you tell me the difference in LinuxCNC between joint and stepgen?

Also, i am fairly certain i added the second Y motor in the configurator, does it not like repeat setups?

The hal file shows mapping:

JOINT STEPGEN  AXIS

0         0           X
1         2           Y
2         4           Z
3         3           A

Both files attached. 

I thought i had mapped the
board step/dir 0 -> X
step/dir 1 -> y1
2->z
3->c
4 ->y2
(i hope this is what you mean by how is it wired).

The encoder i am not even worried about yet i just want the machine to move and everything to register right now.

The tool table should look like this once you add X and Y to the custom_config.yml file:

 

very easy, enter an x and y offset in the tool table for the probe. these are normally 0.0000 since the tool and spindle share the same centerline, but if your probe is offset, you can find the center of a probe calibration ring with an indicator on the spindle, and set a work offset to zero for x and y. then use the probe (with the probe tool offset for x and y set to zero and use the probe position only option on the probing page. when the center has been probed, the x and y dro's will show you how far from the spindle centerline the offset probe center is. enter these in the tool table under the x and y offset column, save and reload the table. if the entries are correct, the main dro's should now show zero.

now when you load the probe tool, the tool offset is called up which will include the x and y offset. so when you probe the work to set an offset it will be taken into account and when the probe tool is unloaded in the user interface and its offset deactivated the zero point will correspond to the spindle centerline.

if you do not have the x and y columns showing in the tool table, open the custom_config.yml file from your config folder and at XY to the tool table display settings as shown below:

This will now display those columns in the tool table when you next run probe basic!

Enjoy!

Chris

Good that you mention Python. A couple weeks ago I learned how to build custom .comp components and I was thinking about moving the communication and logic Part into one.
But I am not sure how much this would improve anything. I guess the Bottleneck is the USB Serial anyway? What do you guys think?

“Working with cnc” is a whole lot different than knowing how to operate a particular machine, say a mill or a lathe.

I like the fact there’s no adds.

It would nice to see a link of method to donate a few coins. If I’ve missed it if someone has a link it would be appreciated.

Whilst the editor is a pain, switching to “source view” can make life easier for edits.

Does remora use the spidev interface ? Whilst ai haven’t looked at the remora driver code lately I noticed a ref to bcm2835 headers which ties it to the RPi4. The RPi5 is a different kettle of fish.

Best bang for buck is going to be an ex corporate PC that has a PCIe for a Parallel Port card.

If just for a proof of concept, the Wheezy image of Linuxcnc with an RTAI kernel wouldn’t be a bad choice, ok it runs linuxcnc 2.7 and an old version of Debian that has been EOL for a few years, but it still works.

I ran my mill with a BBB using the Wheezy image of MK so no having to work over ssh. Was a decent setup for a while.

Linuxcnc-RIO is well worth looking at.

Well said. Especially like the comment about python.

Just a note, the 7i90, FPGA (not having a go but there is always some that breaks the rules) can be used as smart serial device. Just digital i/o and 3 mpgs, but the firmware that runs on the softcore can be modded for 4
Mpgs. Tho it was a little frustrating to do at first.

Posting your hal and ini files would make this easier to diagnose

How are the drives wired to the 7I96S?

(TB2 pin numbers to drive signal names)