well if the processor isn't doing anything else, you could just sit in a software loop. well if the processor isn't doing anything else, you could just sit in a software loop. well if the processor isn't doing anything else, you could just sit in a software loop. well if the processor isn't doing anything else, you could just sit in a software loop. see how much time is used in the loop. (sorry....lol) first calculate the number of clock cycles executed in 31 minutes. (assumes you are using 4Mhz xtal) 31 mins * (60 secs / 1 min) * ( 4,000,000 clocks / sec ) * ( 1 cycle / 4 clocks ) movlw 30 movwf counter1 movlw 40 movwf counter2 movlw 50 movwf counter3 loop1 decfsz counter3,f ; uses 1 clock cycle goto loop ; uses 2 clock cycles decfsz counter2,f goto loop decfsz counter1,f goto loop nop ; will end up here in awhile note: the inital values of counter1 2 and 3 are not correct, as the student it's your task to figure out the correct values. hint: try to get the loop to execute for 1 minute while testing, waiting for 35 minutes to see if your code is working might take along time to debug. michael -----Original Message----- From: Steven Kosmerchock To: PICLIST@MITVMA.MIT.EDU Date: Monday, June 01, 1998 8:13 PM Subject: need a 35 minute loop for 16F84 >Hey everybody, >I have a problem that I need some help with. I'm creating a timer to control something. I am having a problem with the overall time delay. I basically want the PIC to send a signal after 31-35 minutes after it has been powered up. I will be honest and tell everybody that I'm not real experienced with mico's. I am an EE student. I have access to a PICStart plus and have been playing around with MPLAB. Programming a chip isn't the hard part, but getting the chip to do what I want IS! I would love to get some code examples if anybody has done anything like this. > >Thanks in advance, >Steve > >email: steve.kosmerchock@celwave.com >