Could be bad breadboard...

-Adam

On 7/20/2011 6:46 AM, jb-electronics wrote:
What do you use for connective wires? When they are poorly insulated against each other and they touch at some point, you might get some crosstalk that disturbs your BCD signal.

Jens


 Am 20.07.2011 15:42, schrieb Shane Ellis:
Unfortunately, i'm still at the breadboard stage, so no soldering yet. I forgot a lot about nixies, and programming, so I'm taking baby steps.

Keep these suggestions coming, eventually we'll figure it out.

Shane

On Wed, Jul 20, 2011 at 8:40 AM, jb-electronics <webmas...@jb-electronics.de <mailto:webmas...@jb-electronics.de>> wrote:

    Maybe some bad soldering? Happened to me several times.

    Jens

    Am 20.07.2011 15:07, schrieb Shane Ellis:
    Unbelievable.  I yanked out the four data wires, (picaxe to
    74141), double checked them, and NOW, I get 4,5,6,7!!!!  What is
    going on!?
    Shane

    On Wed, Jul 20, 2011 at 4:48 AM, jb-electronics
    <webmas...@jb-electronics.de
    <mailto:webmas...@jb-electronics.de>> wrote:

        Hi,

        I think the problem can be circled fairly easy:

        Create some sample code that is supposed to have the Nixie
        tubes read out a static "12:48" for example. Then check the
        corresponding BCD inputs on each chip. If the right number
        appears there (in BCD format, that is) and the chip displays
        a wrong number, then most likely the chip is defective.

        If you realise there are already the wrong numbers on the
        BCD inputs then you might want to recheck your wiring and
        coding.

        It sounds really obvious, sorry for that, but this is the
        first thing I do when this happens, and it happens more
        often than one would actually presume. One of my favourites
        was when I had a software-internal bit shift that made all
        my numbers about twice as low as intended ;-) I thought it
        was a circuit issue. So you might want to check out your
        software as well.

        Jens

        Am 20.07.2011 11:05, schrieb Terry Kennedy:

            On Jul 20, 1:20 am, Shane Ellis<mime...@gmail.com
            <mailto:mime...@gmail.com>>  wrote:

                It's an IN-14.
                I have a running version of this exact same circuit,
                I built into a
                Christmas ornament, been running perfectly since I
                powered it on, on
                December 23rd.  I looked at my old files, and this
                is identical, and still
                this one is acting buggy.  I'll mess with it again
                tomorrow, and let
                everyone know what, if anything, I figured out.

            Are using the Soviet K155ID1 decoder / driver? There was
            a bad batch
            of those which caused all sorts of havoc. It could
            probably happen in
            the non-Soviet parts, too.


-- You received this message because you are subscribed to the
        Google Groups "neonixie-l" group.
        To post to this group, send an email to
        neonixie-l@googlegroups.com
        <mailto:neonixie-l@googlegroups.com>.
        To unsubscribe from this group, send email to
        neonixie-l+unsubscr...@googlegroups.com
        <mailto:neonixie-l%2bunsubscr...@googlegroups.com>.
        For more options, visit this group at
        http://groups.google.com/group/neonixie-l?hl=en-GB.


-- You received this message because you are subscribed to the
    Google Groups "neonixie-l" group.
    To post to this group, send an email to
    neonixie-l@googlegroups.com <mailto:neonixie-l@googlegroups.com>.
    To unsubscribe from this group, send email to
    neonixie-l+unsubscr...@googlegroups.com
    <mailto:neonixie-l+unsubscr...@googlegroups.com>.
    For more options, visit this group at
    http://groups.google.com/group/neonixie-l?hl=en-GB.

-- You received this message because you are subscribed to the
    Google Groups "neonixie-l" group.
    To post to this group, send an email to
    neonixie-l@googlegroups.com <mailto:neonixie-l@googlegroups.com>.
    To unsubscribe from this group, send email to
    neonixie-l+unsubscr...@googlegroups.com
    <mailto:neonixie-l%2bunsubscr...@googlegroups.com>.
    For more options, visit this group at
    http://groups.google.com/group/neonixie-l?hl=en-GB.


--
You received this message because you are subscribed to the Google Groups "neonixie-l" group.
To post to this group, send an email to neonixie-l@googlegroups.com.
To unsubscribe from this group, send email to neonixie-l+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/neonixie-l?hl=en-GB.

--
You received this message because you are subscribed to the Google Groups "neonixie-l" group.
To post to this group, send an email to neonixie-l@googlegroups.com.
To unsubscribe from this group, send email to neonixie-l+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/neonixie-l?hl=en-GB.

--
You received this message because you are subscribed to the Google Groups 
"neonixie-l" group.
To post to this group, send an email to neonixie-l@googlegroups.com.
To unsubscribe from this group, send email to 
neonixie-l+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/neonixie-l?hl=en-GB.

Reply via email to