MACRO COUNTER HELP

[Jasond0530]

I'm trying to make a macro counter that will count parts using #100 between 06.00 in the morning and 18.00 in the evening and #101 for counting nightshift parts between 18.01pm and 05.59am.

think I have the dayshift sorted but getting hung up on the nightshift counter!!

 

O7999(COUNTER)

(#3012 SYSTEM CLOCK)

N100
IF[[#3012GT060000]AND[#3012LT180000]]THENGOTO3
 
IF[[#3012LT060000]AND[#3012GT180000]]THENGOTO4
N200
 
N1
IF[#3012LT055959]GOTO4
 
N2
IF[#3012LT180000]GOTO3
 
GOTO300
 
N3
#100=#100+1(DAY COUNTER)
 
GOTO300
 
N4
#101=#101+1(NIGHT COUNTER)
 
N300
M99
 

 

can anybody see where I'm going wrong or even point me in the right direction

TIA

[jlw™]

I've made counters like this in Siemens before but never in Fuhnook.

 

In Siemens I always had to asign the system variable for the clock to another variable to use it.

 

So try #103=#3012 and then use #103 in your evaluation.

 

Also, in my Fuhnookish experience you don't want to use #100's. Every machine I've had my hands on used that range for Renishaw or system macros. Start at #500 and go up.

[THEE THAINZ™]

Someone else asked this a little while back. You might trying searching the macro thread you may find it in there. Times like this we should all be missing Tim.

[themachinist]

jlw is right about using variables in the #100 range. You need to be careful which ones you use. Sometimes it is useful to check the macro variables prior to using a new program. If you didn't put the value in it then it is likely that variable is used by a canned cycle.

 

The variables in the #500+ range are better suited to your application (persistent part count across shifts) since they will survive a power cycle.

 

I don't see a path to N1 or N2 in your program. What are they for?

 

Can you describe the problem with the night shift counter?

Custom-Macro-Quick-Reference-1.pdf

[Jasond0530]

 

So try #103=#3012 and then use #103 in your evaluation

 

This is what I figured, referencing something that is changing every second wont help!

 

The variables in the #500+ range are better suited to your application (persistent part count across shifts) since they will survive a power cycle.

 

I don't see a path to N1 or N2 in your program. What are they for?

 

 

 

The #500 are better, just got to work out which ones the Renishaw probe are not using. The N1and N2 were from earlier attempts.

 

Now have it working, with a few extra bits that should store the previous shifts count in another variable and reset the new shifts count.

 

 

%

O9007(COUNTER)

 

#105=#3012

#106=#3011

 

N100

IF[[#105GT060000]AND[#105LT180000]]THENGOTO3

 

IF[#105LT055959]GOTO4

 

IF[#105GT180000]GOTO4

 

GOTO300

 

N3

#100=#100+1(DAY COUNTER)

 

IF[#101EQ0.0]GOTO6

#103=#101

#101=0.0

 

N6

 

GOTO300

 

N4

#101=#101+1(NIGHT COUNTER)

IF[#100EQ0.0]GOTO7

#102=#100

#100=0.0

 

N7

N300

M30

%

 

I have also added this to the M30 call set in the M/c parameters, i.e M30 will call and run this protected sub and then end and rewind after it is read.

[jlw™]

Nice, glad you got it working!

[BFleeger]

I see you got it working by splitting your night shift test

        IF[#105LT055959]GOTO4
 
        IF[#105GT180000]GOTO4

 

I noticed on your original code, you have an "AND" where there should be an "OR" (Not sure if you can use OR in these macros, I am new to this)

But you can not be LT 0600 and GT 1800 at the same time.....

         IF[[#3012LT060000]AND[#3012GT180000]]THENGOTO4

 

If you can combine this back together, might save the machine some processing steps.

[Guest]

At home so I haven't tested this but I think it will work.

 

%

O9007(COUNTER)


#105=#3012

#106=#3011


(DAY SHIFT

IF[[#105GT060000]AND[#105LT180000]] THEN #100=#100+1(DAY COUNTER)

IF[#101NE0.0] THEN #103=#101

IF[#101NE0.0] THEN #101=0.0


(NIGHT SHIFT

IF[[#105LT055959]OR[#105GT180000]] THEN #101=#101+1(NIGHT COUNTER)

IF[#100NE0.0] THEN #102=#100

IF[#100NE0.0] THEN #100=0.0

M30

%