Still, I'm a lot better with the hardware.
Your explanation may have given a clue.
I did check, but am not able to press the button the correct time.
The decoder I used, does not have both 0 when idle. (It does at startup)
And I'm not able to press the button for the correct time.
I've used a 4 Mhz chrystal. Is that a correct frequency?
The work "CLOCK" is displayed very fast, just as fast as one can say it.
(A bit slow) It's the same speed as spelling it fast, just enough time to
pronounce every letter. (What I'm trying to say is, maybe the part is running
I will have a look at the processor settings again, just to be sure.
Thanks for the efford so far.
>-- Oorspronkelijk bericht --
>From: "Chris" <fixitsan@...>
>Date: Sun, 04 May 2008 14:17:01 -0000
>Subject: Betr: [smartsockets] Re: 2 tube clock with PIC16F88
>--- In firstname.lastname@example.org, guus.assmann@... wrote:
>> Hello Chris,
>> Yes, I've noticed that the connections from the PIC to the tubes
>> That's why two programs are needed, obviuosly. (And version 1 and
>> It should be fairly simple to change the program to suit
>my "choice" of connections.
>> If I've seen it right, it's just one table.
>> I have some programming experience.
>> Long ago, I started with the 8080 processor.
>> Later also the 8085. But mainly I used the 6502 in both an Elektor
>> computer and of course in the Atari XL.
>> I've done some more programming on 8052 and 80C552. Also the
>> is nice.
>> But I was never very good at the software.
>> I've also build and modifies a Propellor-Clock. (Henk Soubry)
>> This one uses an PIC. But I only changed the codes for the remote
>> I can read and mostly understand the code.
>> Also, I have a PIC-starter kit. So it should be possible to do
>> (I like designing and building PCB's much more)
>That's not an insignificant amount of experience ! I've only
>programmed two cores so far and they are both PIC's. I'm hoping to
>get some ARM (M3 cortex) experience soon
>I have just quickly built up the clock circuit as per the diagram in
>the file section 'barebones' which has just been added, but with no
>loudspeaker output and no backup supply components connected. I
>doubt they would be able to cause a problem like the one you are
>All 4 resistors connected to the micro are 10k. ( I appreciate their
>value is not clear) The resistor limiting current to the encoder,
>which is 680R because it was already attached to the encoder so I
>just used that, but anything from 330R to 680R should work well.
>The capacitors are disck ceramic 33pf, crystal is 4MHz, and the idle
>state of the encoder channels A and B is '00'. The pushbutton is
>also '0' at rest
>At powerup 'clock' is displayed, the menu items change with rotation
>of the encoder. When 'clock' is displayed and I press the button for
>0.5 seconds and release it, the time is displayed, first hours, then
>mins, then seconds. When I press the button again the word 'clock'
>is displayed to signify that the menu selection system is active
>The code in the files section is taken directly from the IC I used.
>My source was the file already in the files section, which I used in
>order that I could validate it. I have written the config words in
>the file description, CW1 = 3F02 and CW2 = 3FFF
>My programmer automatically selects the fuse settings from the
>config words, which are as follows....
>CODE PROTECT ROM disabled
>SWITCH OVER MODE enabled
>CODE PROTECT EEP disabled
>CCPMx CCP1 RB0
>FLASH WRITE PROTECT disabled
>The correct processor is the 16F88, not the 16F84 ( I will make that
>correction in the diagram )
>I can't think what could be causing your crashes. Obviously the pins
>on the schematic are not in numerical order but you would probably
>have checked that I'm sure
>As long as the button has a pulldown of 10k and the current limiting
>resistor is in the circuit there shouldn't be any reason for it to
>crash like that, even without a current limiter it should work
>reasonably well due to the high impedance characteristic of an input
>pin, but it is almost as if there is a short being created somewhere.
>Sorry I can't be more help. Both the chip in the ZM1350 socket and
>the chip in the 2-tube clock circuit were programmed using the
>files which I downloaded from the files section this morning, but I
>can see how a problem could be so frustrating with what is such a
>Please keep me posted