Pages: 1 [2] 3 4 ... 10
 11 
 on: October 31, 2015, 09:37:28 AM 
Started by willystyle - Last post by nonentity
So I've put everything together, no visible cold solder joints, I plug everything in and do the voltage test - disconnected I can get to about 183v on the low end of the pot. Once the tubes are in, it reads about 149 or so, but only the middle two tubes light up and it seems as though multiple cathodes are lit. If it is displaying a number, it's indistinguishable to me. I also tested each of the tubes from anode to every cathode to verify there are no shorts in the tubes. I'm using the basic code off the site.

Looking for the next logical test steps...

Thanks in advance!

Can you tell us if your driver chips may have been fried? Pictures would help, but that's my first thought.

 12 
 on: October 31, 2015, 09:36:18 AM 
Started by catdotgif - Last post by nonentity
Hey All,
      The nixie clock I built based on the Arduinix circuit is still going strong after three years.  Recently, the #3 digit on one of the IN-4 tubes stopped displaying as a number, and now there's just a blobby glow on one side of the tube.  I've had that happen once before on a tube that doesn't display the full 0-9 digits, and swapping it with another tube eventually cleared it up.  But this one appears to be sticking around.

I'm assuming what has happened is that some kind of filament bridge has formed between the number and the adjacent anode mesh.  I was thinking maybe I could run low voltage current through it to burn out the bridge, but I thought I'd post the issue first to see if anyone has had a similar problem and found a solution for it.  

thxthx!

Do you think it could be cathode poisoning?  If so, to reverse it, swap the anode and cathode for the digit in question and run it in "reverse" for a bit.

 13 
 on: August 06, 2015, 12:14:45 PM 
Started by eplambec - Last post by eplambec
Hello everyone,
   I'm using an arduinix and 6 IN-18's to display a stock ticker price that is being sent to the arduino via a raspberry pi. I currently have a code that uses four bulbs and the readout and am looking for help to turn that code into six. The code was developed to omit the cents of the stock price. I am attempting to include the full price. For example, the pi is scraping a price of 1789.43. The four bulbs would readout 1789. I would like it to display the full 1789.43. I have include my current arduino code. Thanks for any help.

E

#this is based on the Arduinix 6-digit clock code. It includes code to drive
#the Adafruit I2C 128x32 OLED display for debug purposes.

#include <SPI.h>
#include <Wire.h>
#include <Adafruit_GFX.h>
#include <Adafruit_SSD1306.h>
#define OLED_RESET 14

Adafruit_SSD1306 display(OLED_RESET);

// SN74141 (1)
int ledPin_0_a = 2;                
int ledPin_0_b = 3;
int ledPin_0_c = 4;
int ledPin_0_d = 5;
// SN74141 (2)
int ledPin_1_a = 6;                
int ledPin_1_b = 7;
int ledPin_1_c = 8;
int ledPin_1_d = 9;

// anode pins
int ledPin_a_1 = 10;
int ledPin_a_2 = 11;
int ledPin_a_3 = 12;

void setup()
{
  pinMode(ledPin_0_a, OUTPUT);      
  pinMode(ledPin_0_b, OUTPUT);      
  pinMode(ledPin_0_c, OUTPUT);      
  pinMode(ledPin_0_d, OUTPUT);    

  pinMode(ledPin_1_a, OUTPUT);      
  pinMode(ledPin_1_b, OUTPUT);      
  pinMode(ledPin_1_c, OUTPUT);      
  pinMode(ledPin_1_d, OUTPUT);      

  pinMode(ledPin_a_1, OUTPUT);      
  pinMode(ledPin_a_2, OUTPUT);      
  pinMode(ledPin_a_3, OUTPUT);    

  Serial.begin(19200);
  display.begin(SSD1306_SWITCHCAPVCC, 0x3C);  // initialize with the I2C addr 0x3C...
                                              // ...for the 128x32 OLED display
  display.clearDisplay();                     // set up I2C display
  display.setTextSize(2);
  display.setTextColor(WHITE);  
}


void DisplayNumberSet( int anod, int num1, int num2 )
{
  int anodPin;
  int a,b,c,d;

  // set defaults to blank display
  a=1;
  b=1;
  c=1;
  d=1;
  anodPin =  ledPin_a_1;     // default on first anode.

  // Select what anod to fire.
  switch( anod )
  {
  case 0:    
    anodPin =  ledPin_a_1;    
    break;
  case 1:    
    anodPin =  ledPin_a_2;    
    break;
  case 2:    
    anodPin =  ledPin_a_3;    
    break;
  }  

  // Load the a,b,c,d.. to send to the SN74141 IC (1)
  switch( num1 )
  {
  case 0:
    a=0;
    b=0;
    c=0;
    d=0;
    break;
  case 1:
    a=1;
    b=0;
    c=0;
    d=0;
    break;
  case 2:
    a=0;
    b=1;
    c=0;
    d=0;
    break;
  case 3:
    a=1;
    b=1;
    c=0;
    d=0;
    break;
  case 4:
    a=0;
    b=0;
    c=1;
    d=0;
    break;
  case 5:
    a=1;
    b=0;
    c=1;
    d=0;
    break;
  case 6:
    a=0;
    b=1;
    c=1;
    d=0;
    break;
  case 7:
    a=1;
    b=1;
    c=1;
    d=0;
    break;
  case 8:
    a=0;
    b=0;
    c=0;
    d=1;
    break;
  case 9:
    a=1;
    b=0;
    c=0;
    d=1;
    break;
  case 10:
    a=1;
    b=1;
    c=1;
    d=1;
  }  

  // Write to output pins.
  digitalWrite(ledPin_0_d, d);
  digitalWrite(ledPin_0_c, c);
  digitalWrite(ledPin_0_b, b);
  digitalWrite(ledPin_0_a, a);

  // Load the a,b,c,d.. to send to the SN74141 IC (2)
  switch( num2 )
  {
  case 0:
    a=0;
    b=0;
    c=0;
    d=0;
    break;
  case 1:
    a=1;
    b=0;
    c=0;
    d=0;
    break;
  case 2:
    a=0;
    b=1;
    c=0;
    d=0;
    break;
  case 3:
    a=1;
    b=1;
    c=0;
    d=0;
    break;
  case 4:
    a=0;
    b=0;
    c=1;
    d=0;
    break;
  case 5:
    a=1;
    b=0;
    c=1;
    d=0;
    break;
  case 6:
    a=0;
    b=1;
    c=1;
    d=0;
    break;
  case 7:
    a=1;
    b=1;
    c=1;
    d=0;
    break;
  case 8:
    a=0;
    b=0;
    c=0;
    d=1;
    break;
  case 9:
    a=1;
    b=0;
    c=0;
    d=1;
    break;
  case 10:
    a=1;
    b=1;
    c=1;
    d=1;
  }

  // Write to output pins
  digitalWrite(ledPin_1_d, d);
  digitalWrite(ledPin_1_c, c);
  digitalWrite(ledPin_1_b, b);
  digitalWrite(ledPin_1_a, a);

  // Turn on this anode.
  digitalWrite(anodPin, HIGH);  

  // Delay
  // NOTE: With the difference in Nixie bulbs you may have to change
  //       this delay to set the update speed of the bulbs. If you
  //       dont wait long enough the bulb will be dim or not light at all
  //       you want to set this delay just right so that you have
  //       nice bright output yet quick enough so that you can multiplex with
  //       more bulbs.
  delay(2);

  // Shut off this anode.
  digitalWrite(anodPin, LOW);
}

////////////////////////////////////////////////////////////////////////
//
// DisplayNumberString
// Use: passing an array that is 8 elements long will display numbers
//      on a 6 nixie bulb setup.
//
////////////////////////////////////////////////////////////////////////
void DisplayNumberString( int* array )
{
  // bank 1 (bulb 0,3)
  DisplayNumberSet(0,array[0],array[3]);  
  // bank 2 (bulb 1,4)
  DisplayNumberSet(1,array[1],array[4]);  
  // bank 3 (bulb 2,5)
  DisplayNumberSet(2,array[2],array[5]);  
}

int NumberArray[6]={10,10,10,10,10,10};
const int MaxChars = 4;
char strValue[MaxChars+1];
int index = 0;
int stock_price = 0;
int d3, d2, d1, d0 = 0;

void loop()    
{
  if (Serial.available())
  {
    display.clearDisplay();               //clear I2C display
    char ch = Serial.read();              //read char data from RPi via USB serial cable
    if (ch > '9')
    {
      Serial.println("'A' received");     // received command to blank display
      NumberArray[6]=(10,10,10,10,10,10); // '10' blanks a digit
      DisplayNumberString(NumberArray);
      delay(1000);
    }
    if (index < MaxChars && ch >= '0' && ch <= '9')
    {
      strValue[index++] = ch;            //build 4-digit string
    }
    else
    {
      strValue[index] = 0;      
      stock_price=atoi(strValue);            //convert ascii to integer
      index = 0;                             //reset index for next time
//      Serial.print("the stock price is "); //print to debug console
//      Serial.println(stock_price);
      d3 = stock_price % 10;                 // use modulo math to separate integer into indiv. digits
      d2 = (stock_price / 10) % 10;
      d1 = ((stock_price / 10) / 10) % 10;
      d0 = (((stock_price / 10) / 10) / 10) % 10;
      display.setCursor(0,18);     // print stuff to OLED display (was used for debug)
      display.println(stock_price);
      display.display();           // this actually prints what was just set up to OLED
    }
  }
  NumberArray[2] = d0;             // print each digit to a tube (ordering depends on tube board)
  NumberArray[3] = d1;
  NumberArray[1] = d2;
  NumberArray[5] = d3;             // MSB
  DisplayNumberString(NumberArray);
}

 14 
 on: July 15, 2015, 07:35:19 PM 
Started by willystyle - Last post by willystyle
So I've put everything together, no visible cold solder joints, I plug everything in and do the voltage test - disconnected I can get to about 183v on the low end of the pot. Once the tubes are in, it reads about 149 or so, but only the middle two tubes light up and it seems as though multiple cathodes are lit. If it is displaying a number, it's indistinguishable to me. I also tested each of the tubes from anode to every cathode to verify there are no shorts in the tubes. I'm using the basic code off the site.

Looking for the next logical test steps...

Thanks in advance!

 15 
 on: July 13, 2015, 01:33:50 PM 
Started by doghousedean - Last post by doghousedean
Hello,

I have a I2C RTC module and would like to know how to wire it to the arduino, physically I mean.  as the Arduinix shield covers all the inputs.

The docs say I should use pins Analog 4 and 5, is this still possible?

Thanks

Dean

 16 
 on: May 26, 2015, 03:25:05 PM 
Started by catdotgif - Last post by catdotgif
Hey All,
      The nixie clock I built based on the Arduinix circuit is still going strong after three years.  Recently, the #3 digit on one of the IN-4 tubes stopped displaying as a number, and now there's just a blobby glow on one side of the tube.  I've had that happen once before on a tube that doesn't display the full 0-9 digits, and swapping it with another tube eventually cleared it up.  But this one appears to be sticking around.

I'm assuming what has happened is that some kind of filament bridge has formed between the number and the adjacent anode mesh.  I was thinking maybe I could run low voltage current through it to burn out the bridge, but I thought I'd post the issue first to see if anyone has had a similar problem and found a solution for it.  

thxthx!

 17 
 on: April 10, 2015, 01:33:01 PM 
Started by Schnolle - Last post by Schnolle
Hi Guys,

My Name is Thomas, I'm a mechanical engineer and CAD Developer from Germany.
Last Christmas Santa brought me an Arduino starter set and I thought about what I could use it for.
I always like Nixie clocks and when I found the Arduinix, I started this project.

On eBay I found a vintage box with nice compact dimensions and a high top cover which seemed fit very good.







I wanted to combine the clock with a desk light and also added two small e14 vintage light bulbs.
There are RGB LEDs under each Tube and two additional LEDs underneath some gear-wheels.
The color of the LEDs can be controlled via 3 switches, the additional 3-way-switch toggles the display of the current time or date.

There is a micro switch which is toggled by the box cover to completely shut it off when closing.
A battery powered RTC module keeps the time while the box is closed.







The two knobs on each side control the brightness of the LEDs and the light bulbs.

Check out this video for more details including a little "animation" I added when the tubes are activated:
http://fotos.thomas-spiller.de/Personal/Arduino-Nixie-Clock/i-42VVnX3

It all went pretty smooth thanks to all the great threads I found in this forum.
I'd like to thank you all for describing your great projects and how you managed to realize them.

Regards,

Thomas

 18 
 on: March 13, 2015, 09:41:36 PM 
Started by Emblazed - Last post by Wingloader
Hi everyone!!  

FYI, I did search the forum and I didn't see anyone talk about this one...

I am using the code from http://www.arduinix.com/Main/Downloads.htm for the 6 tube crossfade.  There is something that doesn't make sense for me.  I'm trying to learn how this actually works.

Here is the problem:

1)  ledPin_a_1 is defined as pin 10 and initialized as OUTPUT but is never referenced anywhere else in the code.
2)  ledPin_a_4 is defined as pin 13 but is NOT initialized as OUTPUT but it is used in the DisplayFadeNumberString function.
3)  in the DisplayFadeNumberString, ledPin_a_4 IS used even though ledPin_a_4 is never initialized as an OUTPUT.  
4)  if this is a 6 tube clock code, why do we need 4 anodes?

code snippets below

Thanks!
Joe

Code:
// anode pins
int ledPin_a_1 = 10;
int ledPin_a_2 = 11;
int ledPin_a_3 = 12;
int ledPin_a_4 = 13;

In setup:
 pinMode(ledPin_a_1, OUTPUT);      
  pinMode(ledPin_a_2, OUTPUT);      
  pinMode(ledPin_a_3, OUTPUT);  



void DisplayFadeNumberString()
{
 
  // Anode channel 1 - numerals 0,3
  SetSN74141Chips(currNumberArray[0],currNumberArray[3]);  
  digitalWrite(ledPin_a_2, HIGH);  
  delay(NumberArrayFadeOutValue[0]);
  SetSN74141Chips(NumberArray[0],NumberArray[3]);  
  delay(NumberArrayFadeInValue[0]);
  digitalWrite(ledPin_a_2, LOW);

  // Anode channel 2 - numerals 1,4
  SetSN74141Chips(currNumberArray[1],currNumberArray[4]);  
  digitalWrite(ledPin_a_3, HIGH);  
  delay(NumberArrayFadeOutValue[1]);
  SetSN74141Chips(NumberArray[1],NumberArray[4]);  
  delay(NumberArrayFadeInValue[1]);
  digitalWrite(ledPin_a_3, LOW);
  
   // Anode channel 3 - numerals 2,5
  SetSN74141Chips(currNumberArray[2],currNumberArray[5]);  
  digitalWrite(ledPin_a_4, HIGH);  
  delay(NumberArrayFadeOutValue[2]);
  SetSN74141Chips(NumberArray[2],NumberArray[5]);  
  delay(NumberArrayFadeInValue[2]);
  digitalWrite(ledPin_a_4, LOW);
  

 19 
 on: February 28, 2015, 10:30:04 PM 
Started by nonentity - Last post by nonentity
Is it okay to use this code with a V1 board?  When comparing this and the original code I see the input pins are the same, but there are a few things in here I don't understand and wanted to make sure.

Yes, but you might have to flip the anode connections.  A1 to A4, etc.

 20 
 on: February 24, 2015, 03:35:15 PM 
Started by nonentity - Last post by netflow
Is it okay to use this code with a V1 board?  When comparing this and the original code I see the input pins are the same, but there are a few things in here I don't understand and wanted to make sure.

Pages: 1 [2] 3 4 ... 10