Problem with external interrupts (B0-B2) on 18f452

[cncmachineguy]

How fast are you spinning the wheel? I have not looked at the code yet, but it seems quite possible from your description the LCD part is taking too long. If you don't get out of the ISR before the next magnet you will have serious trouble.

[cncmachineguy]

OK, Looked at the code. By my very rough estimation, your ISR will take at least 28.125mSec to get through. That works out to around 3RPS or 180RPM assuming 12 interrupts per rev. For the purpose of debuging, How you tried to spin the wheel by hand and stopping between each magnet to see if the display shows the correct info?

Also it may be on interrupt messing you up. You may have better luck with DT_INT.

[TDuman]

Hi Bert,
Again, thanks for the reponse.
Does your estimated 28.125 MSec include the serial transmission to the LCD? If so what about without it, as it is only temporary to see what I'm getting. I am turning the wheel very, very slowly, just to see interrupts the intflag values.
Below is a table of the results for one revolution I am getting. The last column is the elapsed minutes.

Int # Int1Flg Int0Flg Int2Flg Count(A) Count(R) Count(B) Seconds
1 1 0 0 1 0 0 31
2 1 1 1 1 0 0 63
3 1 1 1 1 0 0 78
4 1 0 0 2 0 0 96
5 1 1 1 2 0 0 128
6 1 1 1 2 2 2 139
7 1 0 0 3 0 0 154
8 1 1 1 3 0 0 165
9 1 1 1 3 0 0 176
10 1 1 0 3 0 0 189
11 1 1 1 3 0 0 204
12 1 1 1 3 0 0 211

I plan to change timer0 to give me 10 or 100 counts per second, in order to get a more precise time with which to calculate rate. Should that work?
Forgive me if I plead ignorance of the DT_INT, can you enlighten me?
regards
Tom

[cncmachineguy]

Hi Tom, I hope you don't mind I am posting your code from the first post so its easier for folks to see. Plus it just makes it easier for me to look at your results and follow the code.

DEFINE LOADER_USED 1
DEFINE USE_LFSR 1
Include "modedefs.bas"     'this is required for RS232 comms
ADCON1=7
' Assign variable names
DBGDSPL     VAR PORTB.5      'Debug display port
CurrPuls    var byte
PulseA      var word
PulseB      var word
PulseR      var word
LastACnt    Var word
LastBCnt    Var word
LastRCnt    var word
CurrSec     var word
LastSec     var word
IntCount    var word                    
pause 10
trisb=%00000111
T0CON = %10000011       'Define Timer0 - 1:16
RCON.7 = 0
INTCON = %10110000      'Enable TMR0 & Pin B0-B2 interrupts 
INTCON2= %10000000      'Falling Edge
INTCON3= %11011000
goto start
'---------------------------------------------------------Interrupt Code
Disable                 ' No interrupts past this point
myint:
if INTCON.1<>0 or INTCON3.0<>0 or INTCON3.1<>0 then    'Pulse Interrupt
    IntCount=IntCount+1
    if INTCON3.0=1 and INTCON.1=0 and INTCON3.1=0 then PulseA =PulseA +1
    if INTCON3.0=0 and INTCON.1=1 and INTCON3.1=0 then PulseR =PulseR +1
    if INTCON3.0=0 and INTCON.1=0 and INTCON3.1=1 then PulseB =PulseB +1
 
    SerOut DbgDspl, N9600, [$1b,$2a,$80]        'turn on background lighting of debug display
    SerOut DbgDspl, N9600, [$1b,$30]
    SerOut DbgDspl, N9600, ["I:",#IntCount, " A:", #INTCON3.0, " R:", #INTCON.1, " B:", #INTCON3.1]
    SerOut DbgDspl, N9600, [$1b,$32]
    SerOut DbgDspl, N9600, ["A:", #PulseA, "R:", #PulseR, "B:", #PulseB, "S:", #CurrSec]
    INTCON.1=0 : INTCON3.0=0 : INTCON3.1=0
endif
if INTCON.2=1 then              'timer overflow interrupt
    CurrSec = CurrSec +1
    TMR0H=11 : TMR0L=186        'set tmr0 cycle count to 3002 so overflows in 1.0 sec
    'TMR0H=231 : TMR0L=147      'set tmr0 cycle count to 59283 so overflows in .1 sec
    'TMR0H=253 : TMR0L=143      'set tmr0 cycle count to 64911 so overflows in .01 sec
    INTCON.2 = 0
endif
Resume                  ' Return to where interrupt occured
Enable                   
'---------------------------------------------------------End of Interrupt code
Start:
PulseA=0 : PulseB=0 : PulseR=0 : CurrSec=0 : LastSec=0 : IntCount=0
LastACnt=0 : LastRCnt=0 : LastBCnt=0
SerOut DbgDspl, N9600, [$1b,$2a,$80]        'turn on background lighting of debug display
SerOut DbgDspl, N9600, [$1b,$30]
SerOut DbgDspl, N9600, ["Start "]
SerOut DbgDspl, N9600, [$1b,$32]
pause 10
 
On Interrupt Goto myint ' Define interrupt handler
Mainloop:
    if PulseR<>LastRCnt or PulseA<>LastACnt or PulseB<>LastBCnt or CurrSec<>LastSec then
'    SerOut DbgDspl, N9600, [$1b,$2a,$80]        'turn on background lighting of debug display
'    SerOut DbgDspl, N9600, [$1b,$30]
'    SerOut DbgDspl, N9600, ["I:",#IntCount, " A:", #INTCON3.0, " R:", #INTCON.1, " B:", #INTCON3.1]
'    SerOut DbgDspl, N9600, [$1b,$32]
'    SerOut DbgDspl, N9600, ["A:", #PulseA, "R:", #PulseR, "B:", #PulseB, "S:", #CurrSec]
    endif
    pauseus 1
GOTO Mainloop
end

My time estimate is based soley on the serout stuff. I was just taking a guess at the number of bytes sent at 9600 baud.


As for DT_INT, search it on this forum and you will find tons of help. I am not so good at finding and posting the links or I would. Basically it is an awesome include to handle all your interrupt needs. It gives you true interrupts as if you had ASM interrupt, but without the hassle. With on interrupt, the problem is you are limited to only seeing the INT after each PBP instruction. So for code with a pause for instance, the interrupt won't fire until after the pause is done.

[cncmachineguy]

Tom, for some reason, I am having trouble pisturing you magnet/sensor setup. Is it possible for the magnet to fire the int, but none of the 3 IF conditions are met? Is there anyway you can make a quick sketch showing the relationship of the magnets sensors, and pully? Doesn't need to be fancy, just a visual. Or even a picture might do it.

[TDuman]

Hi Bert,
Attached is sketch I drew in Paint.
Regards
Tom

[cncmachineguy]

That helps a ton.

so I don't know if my approach is flawed, I have something wrong in the code, or there is some hardware problem.

It may be a little of each. But first lets attack the hardware. I don't think you need the "R" signal. you can get the counts from the A or B. Now, the reason I want to drop it, besides making the code a little simpler, is I fear you may have some overlap in the fields. This could be why you get the wierd stuff with rising or falling edge trigger. Do you have access to a scope to actually watch B and R to see in B dies before R rises?

[TDuman]

Hi Bert,
No, I don't mind.
As a newcomer, I was hesitant to put too much in the post.
I hope you can find whatever flaw I may have. I did a google search for DT_INT. I had seen it before when I was scouring the i-net for articles relating to my problem. I had taken note of it and saved a link for possible future use. It may improve my code and cpu time, but at this point, do see a flaw in the existing approach I am taking? Should this work?
Regards
Tom
PS: I see your next post requesting sketch as I am posting this reply, I'll post a sketch in my next reply

[TDuman]

Thanks for the response.
With this code, I am moving the wheel very slowly so I can see the interrupts and what values the intflags have. I know that when I actually start spinning the wheel quickly that portion will have to be taken out of the interrupt handler. There is a section of code in the mainloop to display the counters and elapsed time, that is diabled so that the display from the actual interrupt subroutine is long enough to be able to read it.
In the final version (assuming I can solve this problem, the max rpm will be 100-150 RPM