Matrix user forums

hi guys,
i recently purchased this: http://www.ebay.co.uk/itm/141087179782? ... EBIDX%3AIT
which i know isnt the correct display for use with flocode, but for the price i thought i would have a go,
it works, but the refresh rate seems really slow, you can see it plotting the screen, which is really inconvenient!

any ideas? is there a bit of c code i could slap in there to get it working properly? i could probably upload a video just to show you whats going on, if that would help?

thanks,
matt

Hi Matt,

Would you mind posting your program so we can have a quick look to see if there are any easy optimisations that could be made.

hello,
thanks for the quick reply!
ive attached the program, in the simulation its super fast, but in real life that takes around 5 seconds to finish the program,
thanks,
matt

Hi
Im sure benj wrote a driver for that display in this thread http://www.flowcode.co.uk/mmforums/viewt ... 57&t=15161

Regards
Dazz

yeah, i did see that, but it doesnt seem to work as well as the built in driver in flowcode, only half the screen starts up and the rest is a mix of weird colours, bit of a weird one, i think!

thanks,
matt

HI
Sorry to be a pain, can you add your findings on the new driver to the thread i linked to, im waiting for lcds to arrive, and benj asked for some feedback on the driver but as yet there is none, if you could it will be helpfull

Regards
DAzz

no problem, i will do that now, i hope that the driver can be fixed to it works properly, however as i said, the built in one seems to work well, just refreshes really slow?

matt

Hello,

I have had a go at speeding up the EBM001 code. I can get the time to clear the screen (nice test as it writes to each and every pixel in one operation) down from 4.14seconds to 2.23 seconds on a PIC16F1937 @ 19.6608MHz. However it makes the code less reliable and if you power cycle the module it then doesn't boot up correctly. I'll try and have another go when I get chance and see if I can speed it up reliably. At the moment there really isn't much FAT in the code to strip out, I got the speed boost mainly by shifting the 16-bit colour data out 16-bits at a time rather than 8-bits and fiddling with when the CS pin is toggled.

A faster device should allow the display to go much faster. For example the display should fly with the new ECIO40P16 released today!
http://www.flowcode.co.uk/product.php?Prod=ECIO40P16

thats very interesting, because you can actually see the pixels changing along the screen, but to refresh the screen i have to clear the whole screen then it has to re build any boxes and text etc that i had put in place. it shouldnt be too much of a problem with what im using it for, but still a bit more speed wouldnt go a miss! im wondering though, would a faster crystal make the chip run faster? or would that damage the chip? because im using a 20mhz crystal, i was wondering if i could maybe use something like a 100mhz?

thanks,
matt