Modding Noritake GU126x32F-K612A4 graphic VFD

I know that it's not necessary in order to perform the cable mod, but I was wondering how exactly unsoldering those wires and soddering them together makes the display work? What is it about those two wires which causes the display to freeze if they aren't soldered together?

 

http://forums.bit-tech.net/showthread.php?s=&threadid=12398&perpage=20&pagenumber=19

Posts 2 and 3 on that page.



Rob.

 

Conditions in LCDC

Ok, LCDC finally allows conditions 1.05.27 release notes

Unfortunately I have not managed to get my head around the inner workings of screenbuilding in LCDC for Noritake displays soooo...

can anyone tell me if this could be used to for example put a sun in the weather screen if the weather forecast is fair, a cloud for when it's gonna be overcast, a raining cloud for rain and a snowflake for snowing?

Could you also give me some pointers to where to do the change in the codes?

Cheers, Chris

Oh, and btw, has anyone had success with Paradynes bargraphs? I'm so close but I still have residue issues and can't get hold of him

 

I'm back..

Hi TSS,

I've just gotten your mail, I'll try and help you out directly rather than add to this thread any more than necessary

Cheers,
Nick

 

Your site down Paradyne? Can't seem to connect to it

 

My websites seem to be up!

www.paradynedsl.force9.co.uk
WinampSA site

Thanks for the heads up though , I'll keep an eye on them.

Cheers,
Nick R

 

Am having problems with my display:

I spoke with Alan? at Itron a short while ago about a problem with the GU162x32 module I have just received. I am able to communicate with it using LCDC (test display) and get reports that a connection is made and data is passed. On his advice I connected serial pins 4 & 8 as in the bit-tech forums to no avail. I have also tried to reset the vfd by crossing pins 5 & 6 on con2 on power up but do not get the expected display. I have also checked the powered up display and the fine wires do not glow slightly as described. Could this be a dead display?

 

are you sure the fuse hasn't blown? You could try a jumping the fuse with a small amperage fuse wire then see if the wires glow. Just make sure that the power is connected the right way round. Unfortunately that was how I killed my 1st display!

 

The power is the right way round, which was my first thought when it wouldn't work. Exactly where is the fuse, I shall give it a go once I know?

 

Yeah sounds like it's blown somewhere along the lines to me... the fuse is a diddy little thing, best let Itron take a look at the display, make sure the fuse is the issue, and fix it for you.

Rob.

 

Found the fuse (its marked f1) and it has blown Itron re sending me a couple so I can replace it. Must say that itron are one of the most helpful and friendly suppliers I have ever dealt with. 9.999999/10.

 

More like 10/10

 

Yeh, could have said 10/10 but thats perfection and nobody's that good.

 

Finally got my vfd working - it was the fuse.

I am now having all sorts of problems trying to build screens. No matter what I do only the first line will show on the display. I am using the noritakea4 definition file and when I try cheeses example it works great just not when I build my own screen. Even building a new screen in cheeses file (which I know works) gives only a single line display. I have tried everything I can think of including resetting the vfd. I just cannot understand why one screens file will work but anything I build will not.

HELP!!!! PLEEEEESE!

 

Building screens is complicated, as I have learned recently.

Do you set cursor positions for the second line and below? I don't think there is any automatic wrapping and the lines in lcdc don't really correspond to the display-lines. For Noritake you point to the exact position on the display instead of a the line/character precision for the MO text displays.

Try setting the cursor position with [##29][##16][##0][##14] for line 2 (check paradynes site for explanations on what the codes mean). Make sure to study and experiment with the commands on Paradyne's site .

Also note that it's good practice to pad each line with [##0] or [##200] (non displayed chars) up to 21 bytes/chars (where [##29] counts as one byte) of data for each line in lcdc. You may otherwise get excessive flickering.

Also try to put static data in before screen events (see Cheese's example file).

Hope this gets you started.

 

thnx tss I am actually getting somewhere at last.

I see cheese uses commands almost as icon files when inserting frames, etc, into a screen (such as his Outro). How are these produced? I want to do make my screen unique in the way cheese has.

I assume these are inaccessible forms of the list of data paradyn es uses in the event command box to make an icon such as his voltages icon. Again how can I do the same, the list of numbers (17,4,4,6,16,0,17,20,4,22,15,0,17,24,4,26,15,0,17,10,18,11,27,0,17,19,18,20,27,0,17,8,5,10,10,0,17,7,20,8,27,0,17,12,5,14,9,0,17,16,11,18,15,0,17,16,21,17,27,0,17,26,21,27,27,0,17,16,5,18,7,0,17,12,13,14,15,0,17,13,24,14,27,0,17,23,24,24,27,0,17,13,4,17,4,0,17,13,10,17,10,0,17,13,16,17,16,0,17,13,21,14,22,0,17,23,21,24,22,0,17,22,16,25,16,0,17,7,4,9,4,0,17,7,11,9,11,0,17,14,20,16,20,0,17,24,20,26,20,0,17,15,23,15,24,0,17,25,23,25,24,0,17,15,9,16,9,0,16,7,5,22,16,15,5,22,16,7,10,22,16,15,11,22,16,15,15,22,16,23,15,22,16,9,20,22,16,18,20,22,16,21,20,22,16,9,27,22,16,15,27,22,16,21,27,22,16,25,27,22,16,37,31,22,[#delay2]) he uses for this icon means nothing to me.

Another wee problem. Regardless of how they are produced (NOR plugin or 20,xl,yt,xr,yb) any outlines have a flashing top line, in the case of the bar graphs it is only after the level of the value shown. Any ideas?

 

I wrote a little VB script to do all my transistions/effects... pretty easy stuff

Rob.

 

Cheese:

Would you like to pass on the knowledge in a how to to the rest of us unworthy's. My VB is VERY basic and any help would be great.

 

hi
guys has this problem been covered if so please point me in the right direction.

When using
lcdc i get error message saying definition file out of date, how do I stop this

Thanks

 

Hi Stuart, welcome to the boards... download the latest version of the lcdc files that's in the first post of this thread, it should sort out your problems

...and griff, the fact I used VB is unimportant. Have a look at the command set for the display (actually the help file in lcdc files download is more helpful as the codes are in decimal there) you'll see what codes correspond to the vfd doing what. Then it's just a case of writing a script to spew out these commands.

Rob.