Searching \ for 'Automotive Hints (was Port C is going nuts!)' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: techref.massmind.org/techref/ios.htm?key=port
Search entire site for: 'Automotive Hints (was Port C is going nuts!)'.

Truncated match.
PICList Thread
'Automotive Hints (was Port C is going nuts!)'
1998\01\03@210940 by Andy Kunz

flavicon
face
>In summary, the re-writing of the TRIS registers repeatedly while using
>the TIMER1 and CCP1 together causes grossly wrong port states to be
>written to the pins.

My experience exactly.

Want some real fun with interrupts?  Set the RXD pin to an output and see
what happens with the USART!

>Now, I have been known to be totally wrong from time to time, so I am
>reserving the right to show me my stupidity for my fellow piclisters.

At least you documented your "stupidity" well.  Maybe others will learn to
provide such brief, concise lightbulb experiences on the list!

>line, which will cause a stutter.  It is normally used to choke off the
>engine on high RPM.

Make sure you have good filtering on the power supply and inputs.
Especially, you need a voltage regulator which can respond quick enough to
surges so as to prevent the output to your PIC from going bonkers.

I took the liberty of renaming the reply so you might get some hits on
exactly _how_ to do that.

Andy

==================================================================
Andy Kunz - Montana Design - 409 S 6th St - Phillipsburg, NJ 08865
         Hardware & Software for Industry & R/C Hobbies
       "Go fast, turn right, and keep the wet side down!"
==================================================================

1998\01\04@164759 by Chris Eddy

flavicon
face
I knew somehow that an Andy would come through.  If you have had this
experience, and Microchip lurks here, I wonder why it isn't in any mention in
the erratta.  I re-read the erratta sheets for the first time and found
nothing that resembles either of our predicaments.  Tried to use the byte
capture peripheral on one of the 6X devices and the interrupts never came at
all.  I hear that that one is in the erratta.  I had a problem on the int on
B0 where it just wouldn't interrupt my code consistently, and eventually
walked away and solved the problem another way.  All of the problems mentioned
in the erratta seem to be trivial compared to port pins going nuts on a whim.
Seems like Microchip likes to put the simple stuff in the erratta and stuff
the hard problems behind the door.  It's stuff like this that costs me 6 hours
(6X50=$300.. alot of McDonalds!) at a time.

ATTENTION ALL MICROCHIP CORPORATION ENGINEERING LURKERS:: CLEANUP IN AISLE 5.
IT LOOKS LIKE SHE'S GONNA BLOW AGAIN IF YOU DON'T HURRY UP.

Shit.  Their competitors will see these items fly by and beat them over the
head in the marketplace.  I understand that nobody's silicon is perfect.  But
at least put it in the erratta.

Chris Eddy
Pioneer Microsystems, Inc.

Andy Kunz wrote:

{Quote hidden}

More... (looser matching)
- Last day of these posts
- In 1998 , 1999 only
- Today
- New search...