Functioning Fadal conversion from Gmoccapy to Probe Basic

I have a functioning 4 axis Fadal 3016L with 21 tool ATC running on LinuxCNC version 2.9 with Gmoccapy. How difficult would it be to convert to Probe Basic? I see MSRDIESEL has a functioning setup with his Fadal. Any thoughts or assistance is appreciated.

Chris

I think the first hurdle is just getting the fadal connected and running on linuxcnc and hash out any issues on the mechanical side converting over to mesa hardware (which unfortunately isn't in stock for most items due to the chip shortage), but once that is done converting over to probe basic would not be so hard, just need to map out the existing atc flow process and then can adjust the atc macro's to accommodate the input/output requirements.  providing there isn't anything super odd with the atc and its a straight forward geneva type drive with index/home sensor outputs, it should be fairly easy.  if it uses a different method it may take a little tweaking.  if you want to start posting some more information of your due diligence for conversion research I am sure we could help sort out a path forward.

As my original post states, I have already completed the conversion to LinuxCNC. The mill has been running for a couple of years now on Gmoccapy. It’s using a 7i92m / 7i77 / 7i72 Mesa card setup.

how are you controlling the atc? macros or classic ladder? or other?

M6 remap with G code. Works perfectly in gmoccapy. Should be fine in Probe Basic. As of last night i am running on Probe Basic and most of my config works as it did in Gmoccapy. Have not tried the ATC yet. I'm really not so sure i even need the ATC widget..

If a moderator sees this post, please merge the linked post with this one.

www.forum.linuxcnc.org/qtpyvcp/47690-pro...ide-sliders-bouncing

Thank You,
Chris

Lcvette,

How do i go about referencing the graphical turret. I assume it's in the Probe Basic M6 remap?

Do a file comparison with something like meld, the macros are probably very close.   The PB sim configs have the atc macros with the widget calls in them.   They contain the phrase "dynatc".  You should be able to merge the two sets of sub files to arrive at a working config.   If you plan on using any of the other functionality such as programmable coolant,  you will want to be sure to bring that code over as well. 

COlger81 wrote:

Lcvette,

How do i go about referencing the graphical turret. I assume it's in the Probe Basic M6 remap?
 

Try this:

;(DEBUG, EVAL[vcp.getWidget{"dynatc"}.rotate{#<homesteps>, "cw"}])

I had to copy that over in to mine to get the screen widget to home at the same time as the physical one.