Bug on I2C lCD
Moderator: Benj
-
- Posts: 54
- Joined: Mon Jan 14, 2013 10:14 pm
- Has thanked: 2 times
- Been thanked: 2 times
- Contact:
Bug on I2C lCD
Hi,
I have open an existing working project from FC7 to FC8.
But now the I2C LCD does not works.
The LCD is a DFRobot (with PCF8574) and the card is a MEGA. I have compare the i2c dialog on both cases :
Good (on FC7) : Bad (on FC8) : As you cas see there is a value added each time.
Best regards
Yannick
I have open an existing working project from FC7 to FC8.
But now the I2C LCD does not works.
The LCD is a DFRobot (with PCF8574) and the card is a MEGA. I have compare the i2c dialog on both cases :
Good (on FC7) : Bad (on FC8) : As you cas see there is a value added each time.
Best regards
Yannick
- Jan Lichtenbelt
- Posts: 797
- Joined: Tue Feb 17, 2009 8:35 pm
- Location: Haren GN, the Netherlands
- Has thanked: 128 times
- Been thanked: 264 times
- Contact:
Re: Bug on I2C lCD
Hi ylanchec
RW should always be at 0V (or GND). It is better to remove the conenction to P1 of the microchip.
Kind regards
Jan Lichtenbelt
RW should always be at 0V (or GND). It is better to remove the conenction to P1 of the microchip.
Kind regards
Jan Lichtenbelt
-
- Posts: 54
- Joined: Mon Jan 14, 2013 10:14 pm
- Has thanked: 2 times
- Been thanked: 2 times
- Contact:
Re: Bug on I2C lCD
Hi Jan,
Of course i can connect RW to GND in Proteus, but on the real card i can't modify this.
The bug seems to comes from the i2c dialog, there are too many bytes in the command. (the last byte)
Best regards
Yannick
Of course i can connect RW to GND in Proteus, but on the real card i can't modify this.
The bug seems to comes from the i2c dialog, there are too many bytes in the command. (the last byte)
Best regards
Yannick
- Jan Lichtenbelt
- Posts: 797
- Joined: Tue Feb 17, 2009 8:35 pm
- Location: Haren GN, the Netherlands
- Has thanked: 128 times
- Been thanked: 264 times
- Contact:
Re: Bug on I2C lCD
Dear ylanchec
Show us the flowcode and perhaps someone can help you with the software
Kind regards
Jan
Show us the flowcode and perhaps someone can help you with the software
Kind regards
Jan
-
- Posts: 54
- Joined: Mon Jan 14, 2013 10:14 pm
- Has thanked: 2 times
- Been thanked: 2 times
- Contact:
Re: Bug on I2C lCD
Hi Jan,
You will find here a zip file including :
- 1 simple fc7 writing "hello" on a LCD I2C --> HEX file
- the same file renamed and opened with fc8 --> HEX file
- proteus 8.8 file with Arduino mega linked to fc7 hex --> WORKING
- proteus 8.8 file with Arduino mega linked to fc8 hex --> NOT WORKING
The problem is the i2c dialog... not good on lcd on fc8 ! Best Regards
Yannick
You will find here a zip file including :
- 1 simple fc7 writing "hello" on a LCD I2C --> HEX file
- the same file renamed and opened with fc8 --> HEX file
- proteus 8.8 file with Arduino mega linked to fc7 hex --> WORKING
- proteus 8.8 file with Arduino mega linked to fc8 hex --> NOT WORKING
The problem is the i2c dialog... not good on lcd on fc8 ! Best Regards
Yannick
-
- Posts: 54
- Joined: Mon Jan 14, 2013 10:14 pm
- Has thanked: 2 times
- Been thanked: 2 times
- Contact:
Re: Bug on I2C lCD
Good :
Yannick
Bad : a 0x00 is immediatly sent after the good value !
Best regardsYannick
- 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: Bug on I2C lCD
Hi Yannick,
I've posted a new version of the v8 component to the update system now. It contains a new property to decide if the backlight is controlled via the main display communication. When set to "No" this should be identical to the v7 component.
Let us know how you get on.
Hopefully the problem is with Proteus and the v8 component would have worked fine with actual hardware. Can you confirm if you have tried on hardware or not and how you got on.
I've posted a new version of the v8 component to the update system now. It contains a new property to decide if the backlight is controlled via the main display communication. When set to "No" this should be identical to the v7 component.
Let us know how you get on.
Hopefully the problem is with Proteus and the v8 component would have worked fine with actual hardware. Can you confirm if you have tried on hardware or not and how you got on.
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
-
- Posts: 54
- Joined: Mon Jan 14, 2013 10:14 pm
- Has thanked: 2 times
- Been thanked: 2 times
- Contact:
Re: Bug on I2C lCD
Hi Benj,
Thank you for your quick response.
I have tested your new update and it's ok on proteus.
I'm going to test on a real LCD at job in few days. You means that the second sent byte is a problem only on proteus ?
On a classical I2C LCD the back light is connected to P3 of 8574.
How is connected the back light on yours ?
Thank you.
Yannick
Thank you for your quick response.
I have tested your new update and it's ok on proteus.
I'm going to test on a real LCD at job in few days. You means that the second sent byte is a problem only on proteus ?
On a classical I2C LCD the back light is connected to P3 of 8574.
How is connected the back light on yours ?
Thank you.
Yannick