Is this not the case with your hardware? If so then please can you tell us where you got your LCD from so we can have a look at the specs and see why it is working differently.
J got my LCD from "Electronique Diffusion", http://www.elecdif.com.
Ref. for ElecDif is "OPLCD4X16C".
Ref. on the display is "ECM 1604C-RN-YBS".
J can't find doc. on web for this display.
It works fine with the change J made.
Ok I think we have this under control now. 4x16 LCDs require the 0x90 and 0xd0, 4x20 displays require the 0x94 and 0xd4. I have edited the components and should be able to provide a more long term solution to the problem shortly.
Please could you try out this new component for me and see if it fixes the problems you were having.
Simply drop the contents of the archive into your Flowcode V3/components and then restart Flowcode. You may want to make a backup of your LCD component files first incase there is a problem.
Please could you try out this new component for me and see if it fixes the problems you were having.
Simply drop the contents of the archive into your Flowcode V3/components and then restart Flowcode. You may want to make a backup of your LCD component files first incase there is a problem.
Ben:
I use the LCD code that appears in the "Articles" section to support custom characters (http://www.matrixmultimedia.com/mmforum ... =26&t=4796). Do the code modifications described in that article apply to your new LCD component code? If not, can you describe how to modify your code to support custom characters.
Will the v4 LCD component incorporate your update and the custom-character-enabling code? I may be wrong but it seems that these general enhancements are not being rolled up into successive versions and it seems to me that they should be. Surely you wizards are better equipped to accomplish this successfully than are the individual Users.
Custom characters for simulation is rather a tricky one and we feel at the moment that as the program will work instantly on the hardware there are better uses of our time. Eg other more important things that need working on. Sorry to bear the bad news. We have an article in our knowledge exchange portion of the forum that details creating and using custom characters.
It isn't the ability to simulate custom characters that I was referring to. The simulator is handy but I find it more useful to debug on the target system because of timing concerns.
What I'm referring to seems to me to be more like a revision control issue and a question of who has the ultimate responsibility to assure that enhancements that Matrix offers on the Forum get incorporated into successive versions of Flowcode. The case in point in my previous post was the LCD custom-character-enabling code that was presented in Steve's Forum article. At least in my opinion, that feature should have been rolled up into the v3.6 version of the LCD component (and all subsequent versions) and I think that you guys are obviously the best qualified to do that. There may be other examples but that's the one that caused my v3.2 code to fail to compile to HEX under v3.6. I chased my tail for several days not knowing if I had a bad installation or what until Steve reminded me that I needed to modify the LCD component to support my custom characters.
Anyway, I think you get the idea and I agree that you shouldn't spend you valuable time enhancing the simulator!
I understand your concern, but this is not an issue of version control. The customization of the LCD code presented in the article I wrote was just that - an example of how to customize the C code for the components. We did not (necessarily) intend it to be incorporated into the main LCD code (although perhaps eventually this will be the case). It was probably intended for Flowcode users who also write in C.
Regarding the question of who has ultimate responsibility for Flowcode enhancements, then I suppose I do. But you cannot assume that the enhancements and customizations we offer through the forum will ever become incorporated into Flowcode itself, although some may do so.
Of course, we'll always provide excellent support for anyone wanting to migrate these customizations into a later version of Flowcode. But we can never guarantee that such customizations will continue to work once Flowcode has been upgraded.
Thanks for the reply and I understand your position.
My fear of course is that components or .fcd code that I modify per your Forum posts will not be upwardly compatible with newer releases of Flowcode. Upgrading, then, is somewhat like playing Russian roulette and troubleshooting, when required, is likely to be beyond my limited programming skills. I have to rely on you for the diagnosis and cure. No complaints so far on the support side, though. You guys have always been terrific at fixing my problems.