Advanced Search

Hello

Looking for help on where I go to change the 7i84U outputs to sink/source. the manual says I need to change the output parameters, is this done in hal?

Thanks

I like to wire E-Stops to power, not enable pins, with as few steps as possible. Soft e-stop can control an enable/disable line, but "real" e-stops I want to pull power from motors. On my machine, it's set up so that the Mesa card is powered separately from the motors/spindle. The Mesa card directly controls the enable lines for the motors, but the power enable signal (to a relay controlling motor power) is also physically routed through the e-stop button such that pressing the button will remove power regardless of what the Mesa card wants. You can get e-stop buttons with multiple switches in them if you want/need multiple circuits being separately switched by one physical button.

I generally also like to wire things such that "power applied" is "enabled", so that a broken wire or loose connection will only disable the machine.

If you've got other safety hazards from just yanking power (eg, a Z axis that could fall), you may need to consider those.

Hi Victo4,

congrats for your project, that is pretty cool.

Your modded vertical Linuxcnc version is available to download?
I can't find it on your github...

Thanks and regards,
Adam

I assume you're referring to the hal file, "num_stepgens=4"

Yes, but you can also do this in pncconf so the GPIO pins become
available I/O options in the configuration utility.

I assume you're referring to the hal file, "num_stepgens=4"

my1987toyota wrote:

Oh this just got interesting!

Oh YESSSSS!

Yes, load 4 stepgens so the unused pins revert to IO pins.

Oh this just got interesting! 

I have a Mesa 7i92 card with the firmware file 7i92_5ABOBx2D.bit loaded, using a Chinese 5-axis breakout board on connector P2. Pins 16 and 17 are currently taken up by stepgen. Is there any way to reassign them so I can use pin 17 to control a relay and pin 16 for mist coolant?

github.com/scottalford75/Remora-RP2040-W5500/pull/15

I haven't solved PIO yet (I went down a path that was interesting but did not work), but this PR allows stepping a little faster (50KHz), but also allows a lot more precision in step pulse generation and configuration of steplen, stepspace, dirhold, dirsetup, and dirdelay on the RP2040.

It also documents my future idea about PIO. I know how to make it work now and hope to get to it soon.

Thanks for the information HansU, I'll update my glade and fix the errors.

The GMOCCAPY documentation indicates that if no EMBED_LOCATION is defined, the the glade VCP will be floating. Is that no longer valid?

What specific errors are happening?

Are you getting failed posts, or g-code that doesn't work?

Keep in mind that the generic F360 post will require editing for machine-specific M-codes and other features.

I did have to modify the post to output G43 properly.

After reading it a bit more closely, I think the current QtDragon documentation regarding Bridge_HAL is clear. It would only be helpful to add an example of the use of Oword subroutines to the [MDI_COMMAND_LIST] section, so it's understood that in addition to macros like G0 Z25;X0 Y0;Z0, subroutines can also be used.

Something I'd like to see, though I'm not sure if it's possible, is that AXIS has some functions that are executed through Key Bindings, which are very restricted in QtDragon. For example, in my case, I designed a control panel with a keyboard and external buttons. AXIS has the function to clear the plot, and if there's an error, a window appears on the screen indicating it. In AXIS, you can simulate closing this window with an external button, but in QtDragon, you can only close it using the mouse or the touchscreen. The same applies to deleting the plot; in QtDragon, you can only delete it by clicking the button.

little tool to see the hal-values in realtime:

Will do thank you. How would they be connected to estop, for future reference