Advanced Search

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

BTW linux 2.9.1 version
and new fusion linux cnc version

Also some guidance on troubleshooting issues "like" this would be deeply appreciated.

They are actually disable pins, not ensable. Its best to leave them disconnected as you have enough to worry about for now. Sometimes they are useful for estop but as Tommy says leave well alone for now;

I’m having a lot of trouble configuring my LinuxCNC turn profile with Fusion 360. Could someone explain how they set theirs up? Does the standard post/profile work properly on your machine? I keep running into a ton of errors, even when trying the example files. Any guidance or working configurations would be really appreciated.

northernstepper wrote:

Or should I leave them unconnected.

Yes, at least for now, till you get the machine working properly.

Thanks for the help.

Installing it on another computer worked. At first it gave the same error because it didnt have the drivers for the wireless card. Plugged it in and it installed no problem.  Im wondering if I wasnt getting internet on the cnc, it said it connected successfully and internet worked when I booted live.