Noritake Graphic VFD (128x32) free samples

[MacAttak]

I have both and had no problem getting the 140x32 one working, but so far haven't been able to get anything but gibberish on the 128x32 module. And that's only when swapping the busy/reset pins (if I leave them the "correct" way then I get nothing on the screen output). The two modules use exactly the same serial pinout and the cable is exactly the same between them, so it should be working.

Might try removing those solder jumpers to drop the speed of the 128x32 down to 38400.

[liquibyte]

I have both and had no problem getting the 140x32 one working, but so far haven't been able to get anything but gibberish on the 128x32 module. And that's only when swapping the busy/reset pins (if I leave them the "correct" way then I get nothing on the screen output). The two modules use exactly the same serial pinout and the cable is exactly the same between them, so it should be working.

Might try removing those solder jumpers to drop the speed of the 128x32 down to 38400.

I had this issue at first as well.  I believe that I had the wrong library at first, their site is kind of confusing to navigate.

[MacAttak]

The library is different between the two modules?

[chrisbrown]

Using the out-of-the-box configuration, you need to use 115200 baud for the 128x32 and 38400 baud for the 140x32. Don't confuse it with the USB serial baud rate; that's independent.

The library is the same but you need to set the dimensions and model number (7000 or 7003) in your setup() routine.

[MacAttak]

Yeah, I was doing all of that.

Here is what was actually wrong (in case anyone else has this trouble):

The order of function calls while initializing the display module is important (unless you are using the 7000, which is what the library defaults to). You need to call interface() FIRST, before calling isModelClass().

The sample code does the opposite (by "sample code", I am talking about when you go to File..Examples..GU7000 menu in Arduino after installing the library). So that sample code works with the larger 7000 module because the constructor for the class defaults to that one. For all other modules, you need to make sure to call interface() first otherwise you will get garbage output from the driver.

The sample project code (a separate download) is written correctly and does not have this problem. It is only an issue with the installed sample templates.

[liquibyte]

Yeah, I was doing all of that.

Here is what was actually wrong (in case anyone else has this trouble):

The order of function calls while initializing the display module is important (unless you are using the 7000, which is what the library defaults to). You need to call interface() FIRST, before calling isModelClass().

The sample code does the opposite (by "sample code", I am talking about when you go to File..Examples..GU7000 menu in Arduino after installing the library). So that sample code works with the larger 7000 module because the constructor for the class defaults to that one. For all other modules, you need to make sure to call interface() first otherwise you will get garbage output from the driver.

The sample project code (a separate download) is written correctly and does not have this problem. It is only an issue with the installed sample templates.

Yeah, that's it.  I was thinking it was the library but the sample code is different by just enough to gum up the works.

[echen1024]

The example is written quite badly if you ask me.
To make it work:
as MacAttack said, reverse the order of the isModelClass and the vfd.interface. It must call vfd.interface BEFORE vfd.isModelClass

Also, BUSY and RESET are mixed up. If using it on Arduino pins, the pin config should be set to 2, 6, 4, with Baud rate of 115200. 38400 WILL NOT WORK!

[macboy]

...Also, BUSY and RESET are mixed up. If using it on Arduino pins, the pin config should be set to 2, 6, 4, with Baud rate of 115200. 38400 WILL NOT WORK!

The default baud rate for the 128x32 display is 115200. For the 140x32 display (the currently available one) the default is 38400. On the 140x32, the baud rate can be set to 1 of 4 presets with jumpers. I'm not certain about the 128x32 one.

[MacAttak]

They both have the same jumpers. But on the 128x32 module jumpers 0 and 1 are closed with a bead of solder, and that puts it into 115200 baud mode. On the 140x32 module none of the jumpers are closed, which sets it to 38400.

The pins worked the same for me on both - nothing was wrong with the reset/busy. I used pins 2, 3, and 4 of my Uno just as described in the sample instructions.

[iceisfun]

These things work awesome!

Adding $80 to the BOM is a lot, you can get a pretty nice TFT setup for less money so it seems like its just for getting that classic VFD look.

[Fsck]

These things work awesome!

Adding $80 to the BOM is a lot, you can get a pretty nice TFT setup for less money so it seems like its just for getting that classic VFD look.

VFDs also have advantages in extreme weather. These are rated for -40C through 85C

[Greyersting]

I feel bad about leeching off free samples but not bad enough to not leech off free samples

[v1rt]

Hi folks,

I really need your help. I'm new to electronics but I can follow instructions well. I received my Noritake 7003B. I'm reading the documentation specifically the pinout on CN2. I'm a bit confused as to what pin on 7003 goes to which pins on my Arduino UNO.

Here is what I think the connection should be

Pin 1 connects to 5v+ on UNO
Pin 2 which is SIN, I don't know where it goes
Pin 3 connects to GND on UNO
Pin 4 connects to a digital pin on UNO
Pin 5 is not used
Pin 6 connects to the RESET pin on UNO

Can someone please correct it?

Thanks a lot!

V1rt

[v1rt]

I'm good now.

[Greyersting]

I'm good now.

Can you post the solution for other people who may be having that problem?

[macboy]

Also, BUSY and RESET are mixed up. If using it on Arduino pins, the pin config should be set to 2, 6, 4, with Baud rate of 115200. 38400 WILL NOT WORK!

The /Reset and /Busy lines are not mixed up. /Reset is pin 6; /Busy is pin 4.

HOWEVER you must note that on the 140x32 display (GU140X32F-7000) the signals are "Not Reset" and "Not Busy" (which is why I wrote /Busy instead of Busy). They are negative logic or Active Low. That means that a low voltage means Reset (or Busy) and a high voltage means Not Reset (or Not Busy). I strongly suspect that you and macattak have overlooked that. For most applications, you do not need to connect the /Reset signal, and it can be left floating to allow the module to operate normally. The /Busy can be used to ensure that you do not over-run the serial receive buffer while the module is busy doing other things (the buffer is only 12 bytes long FYI).

On the 128x32 display (GU128X32D-7003), SBUSY is Active High and Reset is Active Low.

For reliable operation with a microcontroller, you should connect the /Busy to an input on your micro, and only send data while that pin is HIGH. For operation with a PC RS-232, you can connect the /Busy to the CTS handshaking line. This will prevent the PC from sending data while the module is busy. Take care to note the polarity of the signal... The RS-232 port exects a 'positive' voltage to mean "clear to send", but at TTL/logic level, the CTS line is negated so that "Low" is "clear to send".

In my case I am using a USB-RS232 (RS-232 levels, not TTL level) converter with the 140x32 display. The serial and CTS lines are connected directly from the DB-9 connector to the SIN and /BUSY lines, and this works fine for me. (Note that not all USB-RS232 converters will necessarily interpret a "zero" volt signal as equivalent to a negative voltage one). Without the CTS line used, the module will drop characters in certain cases. With the CTS line, this never happens.

[v1rt]

I noticed that even if only pin 1, 2 and 3 of the VFD 7003 are connected to my Arduino, it will still work.

However, even if all 5 wires are connected to my Arduino, my VFD  dies once my stepper motor starts.
What is the fix for this? Looks like my VFD is not getting enough voltage once the stepper motor starts. Stepper motor is sucking it! Is there an electronic part that I can add to prevent this from happening?

Again, my vfd configuration is really simple. I directly connected CN2 pins of 7003 to my Arduino.

VFD 7003	ARDUINO UNO
Pin1	5v+ on breadboard which is also connected to 5v+ on UNO
Pin2	Connected to pin12 on UNO right now.
Pin3	GND
Pin4	connected to pin8 on UNO
Pin5	not used
Pin6	Connected to pin A5 on UNO

This is how I am initializing it.
GU7000_Serial_Async interface(9600, 12, 8, A5); // BAUD,SIN,BUSY,RESET

Any help would be greatly appreciated.

[v1rt]

I'm good now.

Can you post the solution for other people who may be having that problem?

This code worked for me.

#include <GU7000_Interface.h>
#include <GU7000_Parallel.h>
#include <GU7000_Serial_Async.h>
#include <GU7000_Serial_SPI.h>
#include <GU7000_Serial_Sync.h>
#include <Noritake_VFD_GU7000.h>

GU7000_Serial_Async interface(9600, 12, 8, A5); // BAUD,SIN,BUSY,RESET

Noritake_VFD_GU7000 vfd;

void setup() {
  _delay_ms(1000);           // wait for device to power up
  Serial.begin(9600);
  vfd.begin(140, 32);       // 140x32 module
  vfd.interface(interface); // select which interface to use
  vfd.isModelClass(7003);   // select display model
  vfd.GU7000_reset();       // reset module
  vfd.GU7000_init();        // initialize module

    _delay_ms(1000);           // wait for device to power up
 
      vfd.GU7000_setCursor(0, 0);
      vfd.print("test1"); 
      vfd.GU7000_setCursor(120, ;
      vfd.print("test2"); 
      vfd.GU7000_setCursor(137, 16);
      vfd.print("test3"); 
      vfd.GU7000_setCursor(110, 24);
      vfd.print("test4");
}
void loop(){
}

[echen1024]

I see a few problems. The 140x32 module is the 7000 series, and the 128x32 is the 7003. 9600 baud will not work on the VFD. It must be 38400 for the 7000 or 115200 for the 7003.

[v1rt]

I see a few problems. The 140x32 module is the 7000 series, and the 128x32 is the 7003. 9600 baud will not work on the VFD. It must be 38400 for the 7000 or 115200 for the 7003.

Wrong. Mine is 7003B and I am using 9600. I have to short J1 pin to be able to use 9600. If I want 115200, J0 and J1 should be shorted. My 7003B is also 140x32. For the 7003, it is working great with 9600 but a bit flaky when using 115,200. Noritake told me to add vfd.isGeneration('B'); but it didn't help making it stable.

[macboy]

Wrong. Mine is 7003B and I am using 9600. I have to short J1 pin to be able to use 9600. If I want 115200, J0 and J1 should be shorted. My 7003B is also 140x32. For the 7003, it is working great with 9600 but a bit flaky when using 115,200. Noritake told me to add vfd.isGeneration('B'); but it didn't help making it stable.

Are you checking the busy flag before sending data, or just blasting it at the display and expecting it to work?

[macboy]

I noticed that even if only pin 1, 2 and 3 of the VFD 7003 are connected to my Arduino, it will still work.

However, even if all 5 wires are connected to my Arduino, my VFD  dies once my stepper motor starts.
What is the fix for this? Looks like my VFD is not getting enough voltage once the stepper motor starts. Stepper motor is sucking it! Is there an electronic part that I can add to prevent this from happening?
...

Your power supply may be too noisy for the VFD. You can try adding power supply decoupling to the VFD. Add a fairly large (say 100 to 220 µF) capacitor between V+ and GND right at the VFD module. Also ensure that the power supply is decoupled at your microcontroller and at the driver (the H-bridge or FETs) for the stepper motor. If the power supply voltage is sagging to a voltage too low for the VFD you will need to use a stronger (higher current) supply, or use a separate supply for the motor.

If you are picking up switching noise from the stepper, that is harder to deal with. Ensure that the power supply wires for the VFD are a twisted pair, and the SIG (serial signal) is also a twisted pair with a ground wire. you could try adding a ferrite choke to the wire harness close to the VFD. Stepper motors aren't as bad as brushed motors for noise, but they have their own unique noise issues, depending on how you drive them.

[v1rt]

Wrong. Mine is 7003B and I am using 9600. I have to short J1 pin to be able to use 9600. If I want 115200, J0 and J1 should be shorted. My 7003B is also 140x32. For the 7003, it is working great with 9600 but a bit flaky when using 115,200. Noritake told me to add vfd.isGeneration('B'); but it didn't help making it stable.

Are you checking the busy flag before sending data, or just blasting it at the display and expecting it to work?

That's what Noritake told me too. However, I am not really sure how to check it. I'm new to electronics. How do I check it in Arduino? Do I check BUSY if it's HIGH or LOW? Please guide me. Thanks!

[v1rt]

I noticed that even if only pin 1, 2 and 3 of the VFD 7003 are connected to my Arduino, it will still work.

However, even if all 5 wires are connected to my Arduino, my VFD  dies once my stepper motor starts.
What is the fix for this? Looks like my VFD is not getting enough voltage once the stepper motor starts. Stepper motor is sucking it! Is there an electronic part that I can add to prevent this from happening?
...

Your power supply may be too noisy for the VFD. You can try adding power supply decoupling to the VFD. Add a fairly large (say 100 to 220 µF) capacitor between V+ and GND right at the VFD module. Also ensure that the power supply is decoupled at your microcontroller and at the driver (the H-bridge or FETs) for the stepper motor. If the power supply voltage is sagging to a voltage too low for the VFD you will need to use a stronger (higher current) supply, or use a separate supply for the motor.

If you are picking up switching noise from the stepper, that is harder to deal with. Ensure that the power supply wires for the VFD are a twisted pair, and the SIG (serial signal) is also a twisted pair with a ground wire. you could try adding a ferrite choke to the wire harness close to the VFD. Stepper motors aren't as bad as brushed motors for noise, but they have their own unique noise issues, depending on how you drive them.

This is awesome!!! However, since I'm new to electronics, it will be hard for me to understand and implement but I will do my best.

So last night before I saw your post, I already added 100uF on V+ and GND. The VFD still turn off. When I press a button, the menu shows up in the VFD like .5 seconds only. I checked the voltage where the VFD is connected, it was only 4.16v when motor is running. That tells me that my battery isn't strong enough. However, I was wondering why the same battery worked for my friend's VFD 7000 in my own setup. The difference is that he brought in a breadboard with few parts in it. I do not recall since I didn't pay attention to it. He connected the wires from the VFD to that breadboard he brought. Then he only asked me for 1 digital input pin on Arduino. He also asked me where the 5v+ was on my breadboard.

Ensure that the power supply wires for the VFD are a twisted pair, and the SIG (serial signal) is also a twisted pair with a ground wire.

I was using 1 thin solid 22 or 24g wire taken from a ethernet cable.

you could try adding a ferrite choke to the wire harness close to the VFD.

I don't understand this one. I hope you can make a drawing for me. I want to know which pins it will be connected.

[macboy]

Are you checking the busy flag before sending data, or just blasting it at the display and expecting it to work?

That's what Noritake told me too. However, I am not really sure how to check it. I'm new to electronics. How do I check it in Arduino? Do I check BUSY if it's HIGH or LOW? Please guide me. Thanks!

On the 140x32 (7000 series), the SBUSY signal is negative logic (i.e. an active low signal), so a high voltage means "Ready" and low voltage means "Busy". On the 128x32 display, the opposite is true; it is active high, so the signal is high for "busy" and low for "Ready".

From the datasheet: "Data can be stored into receiving buffer. However, it recommends not sending the data when SBUSY=1." ("It recommends" is just awkward Japanese->English translation, read it as "We recommend". Also note that "SBUSY=1" does not imply a high voltage; i.e. with negative logic, a 'Low' is a '1').

Since there is a 12 byte receiving buffer, you can burst up to 12 bytes of data to the display after ensuring it is "Ready". Then you should wait for the SBUSY signal to indicate "Ready" again.

This is awesome!!! However, since I'm new to electronics, it will be hard for me to understand and implement but I will do my best.

So last night before I saw your post, I already added 100uF on V+ and GND. The VFD still turn off. When I press a button, the menu shows up in the VFD like .5 seconds only. I checked the voltage where the VFD is connected, it was only 4.16v when motor is running. That tells me that my battery isn't strong enough. However, I was wondering why the same battery worked for my friend's VFD 7000 in my own setup. The difference is that he brought in a breadboard with few parts in it. I do not recall since I didn't pay attention to it. He connected the wires from the VFD to that breadboard he brought. Then he only asked me for 1 digital input pin on Arduino. He also asked me where the 5v+ was on my breadboard.

Look at the datasheet, section 2.2, Electrical Ratings. Minimum power supply voltage = 4.75 V.

you could try adding a ferrite choke to the wire harness close to the VFD.

I don't understand this one. I hope you can make a drawing for me. I want to know which pins it will be connected.

Google "Snap on ferrite". Put one of those over all the wires coming from the display, close to the display. May or may not help, it depends on how noisy the environment is and how long the wires are. The ferrite helps prevent the wires from acting like antennas. Fix the power supply issue first.