12f675_fuse_about_to_blow!

[LEDave]

I am really missing something or there is something else in your code...

Hi mackrackit

I reloaded your code and the rfpic worked exactly as before, namely:

The RFEN led lit for five seconds immediately either button was pressed but nothing was transmitted.

I do not see why you had to move the delay. Your way the delay should be jumped over when a button is pressed...

Mm, I thought (hoped) the PIC would go to SLEEP then IOC would wake it and the program would run from where it went to SLEEP, so the next thing it would do was run the delay loop...? ON INTERRUPT is on hold right now until we get the delay loop to work with the rfpic tx-ing after the delay. I'm not using ON INTERRUPT RIGHT now.

IF (GPIO.3=1) AND (GPIO.4=1) THEN ' pins will be 0 only when buttons are pressed
     E_OUT=0         ' Disable transmitter
     INTCON.0 = 0    ' No buttons down, so clear int on change flag
     @ SLEEP         ' and start snoozin..zzzzzzzzzzz
     @ NOP           ' Do nothing for 1st instruction on wake-up
    FOR I = 1 TO 5
      PAUSe 1000
      NEXT I 
    ENDIF
    E_OUT=1          ' Enable transmitter (+ lights RFEN LED on demo board)
    PAUSEUS 25       ' Allow RF stage to stabilize
 
'Then check the buttons again
 IF (GPIO.3=1) AND (GPIO.4=1) THEN  Main 'Button not pressed or pressed then released
 if (GPIO.3=0) OR  (GPIO.4=0) THEN       'Carry on to ENDIF & Tx DATA

Dave

[cncmachineguy]

Jumping in again, possibly completely off base here. But, is there any kind of max time between when you enable the tx, and when you send it data? Because all I see different about moving the delay loop is then enable is moved after it.

As a side note, why not change the for loop to something much bigger like 1 to 250, then make the pause time of 20. This won't help the current problem, but when you are back to on interrupt you will not be trapped in the pause for near as long.

[LEDave]

Jumping in again, possibly completely off base here. But, is there any kind of max time between when you enable the tx, and when you send it data? Because all I see different about moving the delay loop is then enable is moved after it.

Hi cncmachineguy, I suspect timing has a lot to do with it (although I don't kow enough to say or point to why).

Plenty of head scratching going on here.

As a side note, why not change the for loop to something much bigger like 1 to 250, then make the pause time of 20. This won't help the current problem, but when you are back to on interrupt you will not be trapped in the pause for near as long..

Yes, pauses for too long are bad news for what I'm aiming at with this project.

Dave

[mackrackit]

In my code try moving

 E_OUT=1          ' Enable transmitter (+ lights RFEN LED on demo board)
    PAUSEUS 25       ' Allow RF stage to stabilize

to the beginning of the
Encode:
block...

Search this document for "RFEN"..
http://ww1.microchip.com/downloads/e...doc/70091a.pdf

[LEDave]

I moved the code.

What happens is:

1/ If a button is pressed and released RFEN briefly flashes after the 5sec delay (no data is Tx'd).

2/ If a button is continually pressed, nothing happens at all (RFEN doesn't light / no data is Tx'd.

Dave

[mackrackit]

How is the voltage on the power supply/battery?

I hope Bruce stops in and sees this as I am lost...

[LEDave]

How is the voltage on the power supply/battery?

I'm using a power supply set at 4.66v.

For some reason my attachments are appearing here 'inline' rather than at the page bottom, sorry.

The comment about dataask going high caught my eye. Maybe our timing is off a touch (not sure if or why) with the RFEN coming on and us missing data-ask going high (there is no technical reason why anything I've just typed is remotely true) Just my gut....aka....Agent Gibbs style...!



Dave