VFD update for testing

**veetid** · 01-21-2007, 07:39 PM

I created a new centrafuse.exe to test VFD functionality for HD44780 displays...

Simply close Centrafuse and overwrite the one file and reload, setup your VFD.

I was sent a VFD that didn't work and these changes fixed the device and made it work.

I need to also make sure that the code changes did not break VFD's that were already working, one of the VFD's I was testing with stopped working with the new code... I might have to make an option to for two write methods, but it was my one flaky old VFD...

Post feedback on whether this fixes your VFD problems or if it breaks your VFD that was working just fine in RC5, or if it does nothing...

david

**veetid** · 01-22-2007, 01:17 AM

I have updated the code again... This should work with all HD44780 VFD displays...

I was able to get all 5 I have now working with this code...

Let me know your results... Follow same instructions as above...

Check later post

david

**AngryMan** · 01-22-2007, 09:14 AM

Originally Posted by veetid

I have updated the code again... This should work with all HD44780 VFD displays...

I was able to get all 5 I have now working with this code...

Let me know your results... Follow same instructions as above...

david

Dave, you are a Genius. I'll go home and hook up my other LCD to try this out. THANKS!

**AngryMan** · 01-22-2007, 12:00 PM

IT WORKS!!!

**midiwall** · 01-22-2007, 12:08 PM

Wow... okay, ignore my PM on the Flux site - it looks like you have it under control!

I have my display with me at work today 'caus I was gonna start working on some code for you. I'll fire up CF here in a bit and see how things go.

Thanks man!

**midiwall** · 01-22-2007, 12:14 PM

_score_

Well done dude. It works.

So... what'd you do?

**midiwall** · 01-22-2007, 12:22 PM

Hmm.... The VFD module is burning a LOT of CPU.

It looks like VFD has about a 17% overhead on this machine, (2.4Ghz P4, 1.5gig RAM, WinXP). Playing a track with VFD disabled shows CF pulling about 3%. If I enable VFD (and then restart CF to get it to take) playing the same track shows about 20-23% CPU.

I know it's an intensive process, but I'm thinking this is gonna kill the M10000 in the truck.

**veetid** · 01-22-2007, 02:02 PM

Originally Posted by midiwall

Hmm.... The VFD module is burning a LOT of CPU.

It looks like VFD has about a 17% overhead on this machine, (2.4Ghz P4, 1.5gig RAM, WinXP). Playing a track with VFD disabled shows CF pulling about 3%. If I enable VFD (and then restart CF to get it to take) playing the same track shows about 20-23% CPU.

I know it's an intensive process, but I'm thinking this is gonna kill the M10000 in the truck.

I tested it on my M10000 and it works... It does take some CPU and if there are some issues I will try to improve...

I could easily lower the refresh rate, but for things like speed and scrolling titles it has to be pretty fast, which uses some CPU...

I believe it will work though...

david

**veetid** · 01-22-2007, 02:03 PM

Originally Posted by midiwall

_score_

Well done dude. It works.

So... what'd you do?

One line of code after a basic write command was wrong, just took awhile to find it...

stupid xor operator...

david

**midiwall** · 01-22-2007, 02:19 PM

Originally Posted by veetid

I tested it on my M10000 and it works... It does take some CPU and if there are some issues I will try to improve...

I could easily lower the refresh rate, but for things like speed and scrolling titles it has to be pretty fast, which uses some CPU...

Can you make scrolling optional? I'd ditch scrolling titles to get back even 10% CPU.