Hi everyone. In 1x16 LCDs, the behavior in realworld, is more like we were using a 2x8 LCD, one side the other. The result is that using the LCD module, every goes fine in simulation but in the real LCD we obtain only the first 8 digits.
Splitting the chain to print into 2 fields, one starting at 0,0 and the other at 1,0, we can print the complete chain.
Sometimes, this is no so practical.
Is there a patch for fix this?
Yhank you.
1x16 LCD in Flowcode
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: 1x16 LCD in Flowcode
Hello Polanco
This is a tricky one. Some 1x16 LCD operate the same as the Flowcode simulation where you have one line of memory and it works well. However the split line LCDs that you are using are a little more troublesome. The problem is that the LCD device memory is split half way across the line. I cant see an upside to doing this but there probably is one.
It may be possible to track the position of the cursor based on clear and cursor function calls and jump to the relevant section of memory if needed. I will have a quick look into this if I get some time today.
This is a tricky one. Some 1x16 LCD operate the same as the Flowcode simulation where you have one line of memory and it works well. However the split line LCDs that you are using are a little more troublesome. The problem is that the LCD device memory is split half way across the line. I cant see an upside to doing this but there probably is one.
It may be possible to track the position of the cursor based on clear and cursor function calls and jump to the relevant section of memory if needed. I will have a quick look into this if I get some time today.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel