Custom M1xx commands & halsampler

More
11 Nov 2011 13:49 #14768 by Grimg
When I try to use custom M command (it needs to change the state [true-false] on 1 parport-out pin) it seems that I can't sample it with (hal)sampler.

In User Manual V2.5 , p138 it only says: "Make sure the parport pin is not connected to anything in a HAL file."

Does this mean that it is not possible to sample with halsampler until the program in custom command executes, or is "sampling option" just disabled somewhere in some config file by default?

If the answer is: NO, it is not possible, I have a couple of ideas for solving this problem:

Plan #1. Tweak somehow the (hal)sampler so that I can sample it in custom commands (IMO least feasible),
Plan #2. Find some utility program on net that changes the parport registries (basically it produces the desired effect),
Plan #3. Making custom HAL component (and using G code parameters),
Plan #4. Something else?

Any thoughts?

Grimg

Please Log in or Create an account to join the conversation.

More
13 Nov 2011 19:52 #14794 by andypugh
Grimg wrote:

When I try to use custom M command (it needs to change the state [true-false] on 1 parport-out pin) it seems that I can't sample it with (hal)sampler.

People wanting to change one pin from G-code typically use the flood coolant or mist coolant outputs, (M7,M8, M9) or the spindle on/off (M4, M4, M5).
That way the signal travels through HAL, so you should be able to see it with Sampler.

Please Log in or Create an account to join the conversation.

More
15 Nov 2011 15:41 #14837 by Grimg
Thanks for info.

It does the job.

Please Log in or Create an account to join the conversation.

Time to create page: 0.168 seconds
Powered by Kunena Forum