wizpic said:Thanks for that I can't understand what's going on, My end seems fine
Sorry to be a pain could you give this one a try for me
I 've redone it so it should be better, if not them I'm stuck and shall have to look deeper into it
rajudp can you share source code so I can try and see where I may be going wrong
Thanks
Wizpic
can post hear completa ckt & working hex code ?birlan97 said:It's working fine now
wizpic said:rajudp what does your hex hile run at (the one you uploaded for us) ?
birlan97 dam I thought I cracked it then, Because it runs fine my end and does not do what it does on your videos
wizpic said:Yes the hex is working fine my end, I run it on a esaypic board, I would not say it is your PCB at all, There is something not quite right either it be my end or you end , I would say more than lightly my end measn that rajudp's code work fine
birlan97 said:Right !
First part of the code was taken from an old one and forgot to change
On the pcb I have 4Mhz Quartz !
i compiled it for 20mhz ( #use delay(clock=20000000) and #fuses HS,NOWDT,NOPROTECT,NOLVP) from your code, if you compiled it for 4 Mhz Quartz then the display update rate will be less
wizpic said:i compiled it for 20mhz ( #use delay(clock=20000000) and #fuses HS,NOWDT,NOPROTECT,NOLVP) from your code, if you compiled it for 4 Mhz Quartz then the display update rate will be less
This what I thought, My code was compiled to run at 4MHZ and thought that birlan97 was unsing a 20MHZ crystal, this would casue the readngs to bounce, So if birlan97
ran your code that was compiled to run at 20MHz and he used a 4MHZ crystal this would explain why the readings are sable,
birlan97 did you recompile at 4MHz and tried that ?
wizpic
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?