RA3 won't get a high level.

[mister_e]

i didn't check the whole thing but i confirm that it blink PORTB.5 led, then turn on the LED on PORTA.3, then turn it off.

Your PIC i/o is dead OR there's a bad contact.

And i posted a link before in post #2 about the config fuses.

[selbstdual]

Good ideas.

i didn't check the whole thing

How can I support you in doing so ?

Your PIC i/o is dead OR there's a bad contact.

Having replaced the PIC I don't think so. I usually press it gently but firmly in the socket. Sometimes I even press when running.

And i posted a link before in post #2 about the config fuses.

Having read it fully, I will comment that. After my first impression it is just a summary of what fuses are possible. I think I am limited to the ones MPLAB offers ?! Additionally most settings are set to work in most cases so do you suggest focusing on something special for this issue ?

[mister_e]

I think I am limited to the ones MPLAB offers ?

Yes, you're limited to what's in the .INC file of your PIC.

How can I support you in doing so ?

Well if the simple TOGGLE PORTA.3 loop don't work, you have to fix it first. Trust me it's working here.

Additionally most settings are set to work in most cases so do you suggest focusing on something special for this issue ?

Well depending what you call most case.. but me, i use around 50 different PIC model and i have thousands PBP code examples, templates, projects and includes store in my computer. So... how on hearth can i remind what i'd set in all of them and how the hardware is set-up on board... I can't even predict what i'll do next time. This is why i always comment the default config fuses and set ALL of them in my code. One day if i have to modify it, i have only one place to check.

Same rules apply to the other thousand code example on other microcontroller brands and other compiler i also use.

[selbstdual]

Well if the simple TOGGLE PORTA.3 loop don't work, you have to fix it first. Trust me it's working here.

I fixed it, now it works. Let's see if the other code works aswell.

Tell me something: How can I be sure that a problem can be found in the externals ? There are so many switches in the chip - the manufacturer calls them features, I name them obstacles.

[selbstdual]

The other code doesn't work, because the capacitor doesn't discharge.

I am using a WIMA MKS 4 0,01/250-N4 capacitor, I guess that means 10nF.

The resistor is 40K.

That should mean it takes 0,00004 seconds to charge and at a maximum the same to recharge due to - er - well-intended voltage levels.

Then I am recharging it, while counting, but it doesn't stop. When short circuiting the capacitor it works, so the code is OK.

Is this cap no 10nF - cap ?

Is there anything to be changed in the code ?

ADCWert = 0
Trisa.3 = 0
High Porta.3

Pauseus 244


Trisa.3 = 1
High Gruene_LED
WHILE Porta.3 = 1
ADCWert = ADCWert + 1
WEND
Low Gruene_LED
Zaehler = 600 - ( (600 / 1200) * ADCWert) ;to keep time even
Pauseus Zaehler
RETURN

[mister_e]

maybe because your Pauseus 244 is way too high? try to remove it.

[selbstdual]

This is right. It should be 40.

But.

I found out that the circuitry itself acts as a huge capacitor compared to this one.

I replaced it with 58 pF and threw away my calculations. Now it's time
to experiment....

I am using it ratiometrically but the same value doesn't seem to exist two times.

Wert:
	ADCWert = 0
	Trisa.3 = 0
	High Porta.3

	;Pauseus 800
	
	
	Trisa.3 = 1			
	WHILE Porta.3 = 1
		ADCWert = ADCWert + 1
	WEND
	Trisa.3 = 0
	Low Porta.3 ;To make UC = Vss
	Pauseus 100 ;To make UC = Vss
	RETURN

Somehow the capacitor has to have time to charge, having a too high value for Pauseus doesn't affect the measurement, it makes sure that the cap is surely charged. But here I cannot know when it's surely charged, but this must be more than zero.

[sotoshie]

I fixed it, now it works. Let's see if the other code works aswell.

how did you fix it? do you still remember?

[Acetronics2]

how did you fix it? do you still remember?

Hummmmm,

how to tell it ???

Last Activity:- 8th May 2008 12:14.

6 years after his last post ...
( and moreover ... I thought he had been banned !!! )

Alain