author

g0pkh

Inbox View Profile
9Comments

Tell us about yourself!

  • g0pkh commented on oliverb's instructable DCF77 Signal Analyzer Clock

    Hi BrettMany thanks for coming back to me. That was very kind to ask the permission from the chap on my behalf and send me the updated code. However maybe it is just me being new to Instructables. I can see I have a patch, but I cannot see how to download or view any of its content. What am I doing wrong ?Kind regardsPete

    Sent you an email Brett.Regards

    View Instructable »
  • g0pkh commented on oliverb's instructable DCF77 Signal Analyzer Clock

    Sorry.. I posted this as a reply to 4nealalan, rather than directly to you Brett Hi BrettAnother nice clock, very well done. I have been playing with another design myself too, but nothing to show for it yet.I have been trying the DCF decoder used in your example.But have noticed a problem, I have been using it without a superfilter (although I have one I could try).Before I do however I would like to get the decoder working without. I have noticed however that although I can a get a sync, and the correct time is displayed, there seems to be no checking made on parity. Therefore I can suddenly on subsequent minutes, get a completely incorrect time and or date being display.for example 34/03/16. The display may then correct on the completion of the next minute, only to change to some othe…

    see more »

    Sorry.. I posted this as a reply to 4nealalan, rather than directly to you Brett Hi BrettAnother nice clock, very well done. I have been playing with another design myself too, but nothing to show for it yet.I have been trying the DCF decoder used in your example.But have noticed a problem, I have been using it without a superfilter (although I have one I could try).Before I do however I would like to get the decoder working without. I have noticed however that although I can a get a sync, and the correct time is displayed, there seems to be no checking made on parity. Therefore I can suddenly on subsequent minutes, get a completely incorrect time and or date being display.for example 34/03/16. The display may then correct on the completion of the next minute, only to change to some other incorrect value shortly afterwards.Have you noticed this ? Do you have any suggestions ?I live just north of London so don't get a brilliant signal, however using Udo's DCF library my other clocks work really well with no hiccups at all.I suspect adding the superfilter will help, but I would like to get the code working correctly without first, if at all possible.I have tinkered with the "split times" but doesn't really make much difference.Obviously the code thinks the recieved data is correct and displays it even though it is significantly different to the previous minute.Can you think of any suggestions that may help ? Parity checking improvements perhaps ?Kind RegardsPete G0PKH

    Hi BrettAnother nice clock, well done. I have been playing with a design myself too, but nothing to show for it yet.I have been trying the DCF decoder used in your example.But have noticed a problem, I have been using it without a superfilter (although I have one I could try).Before I do however I would like to get the decoder working without. I have noticed however that although I can a get a sync, and the correct time is displayed, there seems to be no checking made on parity. Therefore I can suddenly on subsequent minutes, get a completely incorrect time and or date being display.for example 34/03/16. The display may then correct on the completion of the next minute, only to change to some other incorrect value shortly afterwards.Have you noticed this ? Do you have any suggestions ?I…

    see more »

    Hi BrettAnother nice clock, well done. I have been playing with a design myself too, but nothing to show for it yet.I have been trying the DCF decoder used in your example.But have noticed a problem, I have been using it without a superfilter (although I have one I could try).Before I do however I would like to get the decoder working without. I have noticed however that although I can a get a sync, and the correct time is displayed, there seems to be no checking made on parity. Therefore I can suddenly on subsequent minutes, get a completely incorrect time and or date being display.for example 34/03/16. The display may then correct on the completion of the next minute, only to change to some other incorrect value shortly afterwards.Have you noticed this ? Do you have any suggestions ?I live just north of London so don't get a brilliant signal, however using Udo's DCF library my other clocks work really well with no hiccups at all.I suspect adding the superfilter will help, but I would like to get the code working correctly without first, if at all possible.I have tinkered with the "split times" but doesn't really make much difference.Obviously the code thinks the recieved data is correct and displays it even though it is significantly different to the previous minute.Can you think of any suggestions that may help ? Parity checking improvements perhaps ?Kind RegardsPete G0PKH

    View Instructable »