PIC18EXT.BAS Alteration

[rdheiliger]

Couldn't go to bed before i hooked up the pulse inputs.

When i hook up the pulse input to PortC.5 i get pulses on PortC.5 and not on PortC.4.

When i hook up the pulse input to PortC.4 i get counts on PortC.4 and PortC.5 as well.

The traces are paralell for awhile but if i was getting cross talk between traces i would think it would be in both directions. But its not. I can eliminate everything in the program that refers to PortC.4, put pulses into PortC.4 and still get pulses on PortC.5. There are no shorts between the traces or anything else on the board. It appears to be internal to the ports.

I did notice that these two ports do not have smitt triggers as most other inputs do. Can this have some thing to do with it.

Also there are internal pullups on these two inputs. I supposedly disabled them by setting UCFG.4 to 0 as well.

My pulse input is from a hall effect switch with a 1K pull up resistor.

Any thoughts????

RD

[mister_e]

Weird... work perfectly here with 10K external pull-up (EasyPIC 4) but push-buttons... big deal... While i'm still awake, could you post your code so i can test it here?

Maybe not a bad idea to start a new thread as it's a out of topic from the original.

PS: for your tests.. did you left one or the other pin floating or you had a pull-up attach to?

[rdheiliger]

this is part of a pretty large program.

the code for the alias'

SCLK var PortC.0
ColPump var PortC.1
RadPump var PortC.2
RadFlowInput var PortC.4
ColFlowInput var PortC.5
SerRecieve var PortC.6
SerTransmit var PortC.7

this is the code to read pulse width:

gosub checksw
if colflocal > 0 then 'if have a calibration number, read the collector sensor
pulsin colflowinput,0,colflo
colfloacc = colfloacc + colflo
endif
gosub checksw
if radflocal > 0 then 'if have a calibration number, read the radiant heat sensor
pulsin radflowinput,0,radflo
radfloacc = radfloacc + radflo
endif
gosub checksw

i am averageing over 10 scans then writing the colflowacc and radfloacc to an lcd

don't stay up too late.

RD

[mister_e]

in meantime try something,
1 reload the BootLoader firmware and disable the USB voltage generator config fuse,
2 load it in your PIC and dump your program in ...
3 see if it change anything...

Also try on another set of pin... i may think of few thing when using PULSIN on those specific pin....

[mister_e]

I'm unable to reproduce the issue here...

        RadFlowInput var PortC.4
        ColFlowInput var PortC.5

        ColFlow var word
        RadFlow var word

        pause 500
        hserout ["Testing...",13,10]                

start:        
        pulsin colflowinput,0,colfloW
        pulsin radflowinput,0,radfloW
          

        hserout ["    PORTC.4=",DEC rADFLOW,_
                 "    PORTC.5=",DEC cOLFLOW,13,10]

        GOTO START

Seems to be a hardware problem... if you have any schematic and part#, that would be handy.

[rdheiliger]

I did try turning off the USB voltage. Same result.

I was leaving PortC.5 floating when running the pulses into PortC.4 and vice versa. By tying PortC.5 low or high thru a 1K resistor the problem does go away. Interesting that i don't have to tie PortC.4 low when putting pulses into PortC.5.

Will get another pulse input set up tomorow and see if the problem goes away.

I am using a water flow sensor that counts pulses of a magnetic rotor passing a hall effect switch. Am blowing air thru the sensor to test. Am assuming you are using a push button??

The board is my own design. It is intended as a solar collector control and monitor. This is about the last bug to have it all working.

Will let you know tomorow, if having both sensors connected works.


Thanks for the help!!

RD

[mister_e]

Your welcome! you could still use HPWM for your tests... this one have 2 channel.. just play with duty cycle and hop.. you're in business.

I also tried to left a pin floating but didn't had any problem.. must be because i use a development board and not a breadboard

But... on the other side, i don't see your full code, maybe somewhere you write to PORTC.x and it cause some "extra noise". BTW if you want to write to a single pin, consider LATx register instead of PORTx. Maybe you already know it?