I looked in the forums and did find "answers" to? this but nothing that did not seem like a lot of work and beyond my current understanding of how mach 3 works and how to hack it. So, the question is, is it possible to add a parts counter that keeps track of how many times a gcode is run? I can probably edit my screen as I have done it in the past and can probably re-figure out how the editor works.

?

I would like to have an on screen counter either in the main program space or elsewhere and ideally would like to be able to decrement the counter in case a part was rejected. I am making a lot of little wooden parts and even if the job runs properly some parts are not good enough to keep because of things like out of square stock that was not noticed or excessive damage caused by crazy grain.?

?

I have various electrical counters that i can use as a switch so if this will be a big project the simple electrical switch would be easier. I am currently using a counter app on my phone but the environment is too messy for the phone and I am not good at remembering to increment manually.?

?

I just thought of something that might work but it will not allow for decrementing. I could keep all the bad parts until I finish the job and then count them separately. I have a foot switch that starts the program. I think it might have two internal switches so one could operate the counter.

?

I also like programming Arduinos and might have something thrown together that I can convert to some sort of smart counter but I am running out of time for projects. Need to just get some work done and spend less time with distractions.

?

Still a hopefully simple computer bed solution would be best.

?

?

“I just thought of something that might work but it will not allow for decrementing. I could keep all the bad parts until I finish the job and then count them separately.”

?

What about two bins one bin for good parts, one bin for bad parts and a set of weighing scales.

[Edited Message Follows]

It sounds like the parts you are talking about are not using the 4th axis A. If you set A to zero at the start of your loop you can have a counter that increases by 1 at the end of the loop and moves A to that value. The A axis DRO will then act as a visible loop count.

Here is what I expect it to have added to the code:-

#111=[0] ; pick a suitable number for the subroutine counter
G0 A 0 ; set A to zero, if necessary you can put an M1 pause here to remind you if A has a large value to set zero and restart.

; call the subroutine

; end program

;? subroutine

#111=[#111 + 1]
G0 A [#111]

; return from subroutine

If you have not got the A axis set up then it should not be hard to set it up with a high speed to simulate it as required for this process.? If you are using A and are willing to modify the screen then use axis B and add the B axis DRO somewhere.

Martin

that looks like an easy solution. i am using the A axis. i should post a video some day. the machine is pretty neat but still full of bugs after just 7 years working on it.?

i would like to add a B axis dro to the screen but might need to do some searching to find a computer that will run the screen editor. most of my computers are running win 10 now and i am almost certain that the screen editor does not work anymore. i looked at it briefly and could not get anything to work.

i do have an xp machine running the router so i can probably do it there.

any suggestions on the best way (which program etc) to edit a screen, possibly on a win 10 computer?

?

?

Best regards, Spencer Chase
67550 Bell Springs Rd.
Garberville, CA 95542 Postal service only.
Laytonville, CA 95454 UPS only.
Spencer@...
Spencer@...
Spencer@...


(425) 791-0309
(707) 223-8212

------ Original Message ------

From: "Martin Connelly" <martin.at.leasingham@...>

To: [email protected]

Sent: 2/15/2020 1:23:12 AM

Subject: Re: [MachCNC] parts counter

[Edited Message Follows]

It sounds like the parts you are talking about are not using the 4th axis A. If you set A to zero at the start of your loop you can have a counter that increases by 1 at the end of the loop and moves A to that value. The A axis DRO will then act as a visible loop count.

Here is what I expect it to have added to the code:-

#111=[0] ; pick a suitable number for the subroutine counter
G0 A 0 ; set A to zero, if necessary you can put an M1 pause here to remind you if A has a large value to set zero and restart.

; call the subroutine

; end program

;? subroutine

#111=[#111 + 1]
G0 A [#111]

; return from subroutine

If you have not got the A axis set up then it should not be hard to set it up with a high speed to simulate it as required for this process.? If you are using A and are willing to modify the screen then use axis B and add the B axis DRO somewhere.

Martin

If you use the b axis you can see the count on the diagnostics screen. No need to add the DRO to a screen then.

Martin

[Edited Message Follows]

It sounds like the parts you are talking about are not using the 4th axis A. If you set A to zero at the start of your loop you can have a counter that increases by 1 at the end of the loop and moves A to that value. The A axis DRO will then act as a visible loop count.

Here is what I expect it to have added to the code:-

#111=[0] ; pick a suitable number for the subroutine counter
G0 A 0 ; set A to zero, if necessary you can put an M1 pause here to remind you if A has a large value to set zero and restart.

; call the subroutine

; end program

;? subroutine

#111=[#111 + 1]
G0 A [#111]

; return from subroutine

If you have not got the A axis set up then it should not be hard to set it up with a high speed to simulate it as required for this process.? If you are using A and are willing to modify the screen then use axis B and add the B axis DRO somewhere.

Martin

two question. i did get it to work with a simple test program putting all the code for the part in a sub and calling it a number of times. once i realized that the B axis was not enabled and i enabled it, it worked :)

how do i run a sub continuously instead of a fixed number of times???

it seems that the #111 variable needs to be initialized which is why i need a top level program and then a sub. if i don't use a sub and don't initialize the variable it does not work, program is constantly updating the B DRO.

so i guess i do need to put all the code in a sub, right? but how do i keep it running indefinitely until i stop the top program?

?

?

Best regards, Spencer Chase
67550 Bell Springs Rd.
Garberville, CA 95542 Postal service only.
Laytonville, CA 95454 UPS only.
Spencer@...
Spencer@...
Spencer@...


(425) 791-0309
(707) 223-8212

------ Original Message ------

From: "Martin Connelly" <martin.at.leasingham@...>

To: [email protected]

Sent: 2/15/2020 1:23:12 AM

Subject: Re: [MachCNC] parts counter

[Edited Message Follows]

It sounds like the parts you are talking about are not using the 4th axis A. If you set A to zero at the start of your loop you can have a counter that increases by 1 at the end of the loop and moves A to that value. The A axis DRO will then act as a visible loop count.

Here is what I expect it to have added to the code:-

#111=[0] ; pick a suitable number for the subroutine counter
G0 A 0 ; set A to zero, if necessary you can put an M1 pause here to remind you if A has a large value to set zero and restart.

; call the subroutine

; end program

;? subroutine

#111=[#111 + 1]
G0 A [#111]

; return from subroutine

If you have not got the A axis set up then it should not be hard to set it up with a high speed to simulate it as required for this process.? If you are using A and are willing to modify the screen then use axis B and add the B axis DRO somewhere.

Martin

If you use the b axis you can see the count on the diagnostics screen. No need to add the DRO to a screen then.

Martin

I have modified the standard screen set by adding a small B axis DRO to the first 3 screens. It can be downloaded from here.



Martin

Just spotted a toggle on the diagnostics screen for toolpath on/off. Turn it off for fast loading.

Martin