Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Digital Inputs add M66 "Wait on Input" GCode #282

Open
fra589 opened this issue Aug 6, 2022 Discussed in #280 · 10 comments
Open

Digital Inputs add M66 "Wait on Input" GCode #282

fra589 opened this issue Aug 6, 2022 Discussed in #280 · 10 comments

Comments

@fra589
Copy link
Owner

fra589 commented Aug 6, 2022

Discussed in #280

Originally posted by mcinquino July 29, 2022
Hello,

I see that in the pinout diagram there are 4 digital inputs on pins 27,29,31 and 33 that are shown. I see that we have M codes - M62, M63, M64, M65 to set the outputs that are shown above these inputs. In linuxCNC we would use M66 to wait on an input. I don't see that M66 is implemented in the list of G codes. Is there a way to use these inputs in G code?

image

Thanks,
Mike

@fra589
Copy link
Owner Author

fra589 commented Aug 6, 2022

M66 is not yet implemented since nobody have asked it for now :)
Normally, it will be not so difficult to add M66 to the GCode interpreter...

Considering all my occupations, I could probably look into the matter after mid-October...

@++;
Gauthier.

@zalexzperez
Copy link

@fra589
So, as I understand, those digital inputs can't be used right now?

I'd like to have a physical button press activate the homing sequence but I don't see a way to achieve this without digital inputs.

@fra589
Copy link
Owner Author

fra589 commented Sep 14, 2022

Hi @zalexzperez,

The use digital inputs can be used by your GCode sender software as there are reported in the accessory state Grbl's output. See https://github.com/fra589/grbl-Mega-5X/wiki/grbl-Mega-5X-v1.2-interface

It's only the M66 "Wait on input", which will pause Grbl until the digital input trigger, which is not implemented today.

Your software can use the output status of accessory state digital input status to send the $H command when your button will be triggered.

@++;
Gauthier.

@zalexzperez
Copy link

@fra589 I was actually thinking of being able to home the machine independently from the G-code sender program, as being able to turn on the machine and immediately pressing a button to home it would be more convenient (easier and time-saving).

I'm not seeing how my controlling programs (UGS and gSender, I prefer the latter) are able to react to (output status) accessory state changes. I barely managed to enable the visualization of output status messages on UGS by digging into the options and finding the "Show verbose output" option.
Are you sure these programs can be configured to send commands on reading the output status?

Thanks in advance,
Alejandro.

@fra589
Copy link
Owner Author

fra589 commented Oct 4, 2022

Hi @zalexzperez,

Since gsender and UGS are open source, you can make your contribution by adding the necessary code...

It's also possible to add code directly in Grbl by adding an input pin which react with homing or to performs the homing automatically when resetting Grbl (it's not too dificult do do).

@++;
Gauthier.

@Ams-Laser
Copy link

Hello, is there hope on implementing M66 wait for input, this would be a real use for my cnc embroidery machine as to wait for neddle up before sending movement

Thanks

Ed

@fra589
Copy link
Owner Author

fra589 commented Mar 11, 2023

Hi @Ams-Laser,

It's still on the TODO list...
I'm very busy at the moment, I'm going to raise the priority, but it's going to take time... Be patient!

@++;
Gauthier.

@Ams-Laser
Copy link

Thanks, ill hold on 😉

@M12b1t83i
Copy link

I need 259

Dprocess at 4 Val

Max 9D

@fra589
Copy link
Owner Author

fra589 commented Mar 20, 2023

@M12b1t83i ????

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants