Advanced Search

"Reset to 100%" would not work if you are using analog signals for the overrides.
So it will be only options for proceed and abort.

Dude, your machines look awesome by the way! 

there is only one RAM module in the PC, but i tried to swap it with a module from another PC. Both module have different speeds, sizes and manufactors. The same is for a second graphics card i tried.

But again without luck.

Wish i had another Ryzen CPU for testing but i haven't.

I’ve just discovered that the Mesa Configuration Tool (at least the version available prior to 8/19/2024) does not configure the manual tool change section correctly.  I recently discovered this when my file did not stop at the M6 command and continued on to the next set of code.  I was able to look at a .hal file set up with pncconfig and copy the manual tool change section from there and now everything works correctly (I get the manual tool change pop up window when the M6 command is encountered). This is a Mill setup that uses the AXIS GUI.

Here are the two configurations:

Pncconfig version that works:

#  ---manual tool change signals---
net tool-change-request    <= iocontrol.0.tool-change
net tool-change-confirmed  => iocontrol.0.tool-changed
net tool-number            <= iocontrol.0.tool-prep-number 

#  ---Use external manual tool change dialog---
loadusr -W hal_manualtoolchange
net tool-change-request    =>  hal_manualtoolchange.change
net tool-change-confirmed  <=  hal_manualtoolchange.changed
net tool-number            =>  hal_manualtoolchange.number

#  ---ignore tool prepare requests---
net tool-prepare-loopback   iocontrol.0.tool-prepare      =>  iocontrol.0.tool-prepared


Mesa Configuration Tool version that doesn’t invoke the manual tool change pop-up or pause the code at M6:

#  Manual Tool Change Dialog
loadusr -W hal_manualtoolchange
net tool-change-request    =>  hal_manualtoolchange.change
net tool-change-confirmed  <=  hal_manualtoolchange.changed
net tool-number            =>  hal_manualtoolchange.number

# create signals for tool loading loopback
net tool-prep-loop iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
net tool-change-loop iocontrol.0.tool-change => iocontrol.0.tool-changed

 Regards,

Skylor

Interface between ARM-Core and FPGA-Part works, using AXI.

next step: udp2axi program for the ARM-Core

I would think that could be done with 2 mux2 components
(1 for X and 1 for Z) that select between anglejog outputs
when anglejog is enabled and direct MPG counts when
anglejog is not selected.

I didn't know about g93 you're right that's definitely the way to go