Hi, I am playing with a timing circuit that counts down from a variable set by a pot on ADC...this is working (cimulating) but at the end of the program, the LCD component macro prints the string "End" on the 16X2 LCD which is still present at the end of simulation.
Now then, to cut costs, I have substituted the 16X2 LCD component with the 16X1 component......no other changes to the code. At the end of the program using the 16X1 LCD, the word "End" shows only for a brief period and then the display blanks.......showing nothing at the end of the simulation.
Is this normal? will this be the case in hardware or is it a bug in the component or it's macro?
Dave
16X2 LCD works, 16X1 doesn't.
Moderator: Benj
-
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: 16X2 LCD works, 16X1 doesn't.
Hi Dave,
That seems odd if you have examples of the two programs I would be interested to see them.
I would think its a simulation problem though, the hardware shouldn't have any problems like this.
That seems odd if you have examples of the two programs I would be interested to see them.
I would think its a simulation problem though, the hardware shouldn't have any problems like this.
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
-
daveb0360
- Posts: 139
- Joined: Mon Sep 21, 2009 10:17 am
- Location: Leicester
- Has thanked: 35 times
- Been thanked: 12 times
Re: 16X2 LCD works, 16X1 doesn't.
Hi Ben,
I have progressed the project now so the error isn't there any more but I will backtrack over the weekend and send you the file for you to look at. I think you are right, this is probably a sim problem but one that could catch users out if not debugged.....it certainly had me guessing and I decided to use the second line for other messaages as a work around in addition to a second display for other debug use whilst simulating.
Dave
I have progressed the project now so the error isn't there any more but I will backtrack over the weekend and send you the file for you to look at. I think you are right, this is probably a sim problem but one that could catch users out if not debugged.....it certainly had me guessing and I decided to use the second line for other messaages as a work around in addition to a second display for other debug use whilst simulating.
Dave