a) The GLCD 192644A V5.0 has CS1, CS2 and also a CS3 that is not controlled within all the gcb files I could find in my demo folders directory.
Your online link doesn't contain any KS0108 file.
Should CS3 also be connected and controlled by the microcontroller?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi @Haroen. What do you need a display to do? text , graphics , or both?
Gcb supports more than I can throw a stick at and can't buy them all to try.
I like graphic displays cos they make me do more code and pretty but just giant text is nice.
I'm trying the classic rotating cube for gcb
..... before I do elite :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The big screen GLCD 192644A V5.0 is for a lathe display controller where eventually it has to do both text and later graphics.
The Geekcreit® IIC I2C 2004204 20x4 is for an injection molding project.
This one does only text characters.
Your graphic display video's convinced me to give it a try.
I don't have any default gcb displays laying around so let me know how the rotating cube went.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, just an update...
I've received my displays and tried with the existing ssd1306 and gcld gcb code from the demo files directory and it works great. Thanks.
I was thinking of making a portable dedicated Stand-Alone I2Cscanner with one of these SSD1306 displays.
That depends on how much has to be displayed.
The problem arises with these displays already on I2C, how to scan the I2C-bus properly for a second unknown I2C-address device?
Couldn't this be done by just eliminating the address of the display after the scan and so remains the I2C address of the scanned device?
Last edit: Haroen 2021-01-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are these displays supported by gcb?
a) GLCD 192644A V5.0
b) Geekcreit® IIC I2C 2004204 20x4
It has a separate I2C pcb on the back that can be removed if necessary.
I've browsed the demo files directory and can't figure out which *.gcb files would be compatible.
Yes. and Yes.
a) is KS0108, so go to this web page https://github.com/Anobium/Great-Cow-BASIC-Demonstration-Sources/find/master and type in serarch: KS0108 there are a few
b: i2c LCD: Look in https://github.com/Anobium/Great-Cow-BASIC-Demonstration-Sources/tree/master/LCD_Solutions/I2C_Solutions
These folders are in your demo folders also.
a) The GLCD 192644A V5.0 has CS1, CS2 and also a CS3 that is not controlled within all the gcb files I could find in my demo folders directory.
Your online link doesn't contain any KS0108 file.
Should CS3 also be connected and controlled by the microcontroller?
Hi @Haroen. What do you need a display to do? text , graphics , or both?
Gcb supports more than I can throw a stick at and can't buy them all to try.
I like graphic displays cos they make me do more code and pretty but just giant text is nice.
I'm trying the classic rotating cube for gcb
..... before I do elite :)
The big screen GLCD 192644A V5.0 is for a lathe display controller where eventually it has to do both text and later graphics.
The Geekcreit® IIC I2C 2004204 20x4 is for an injection molding project.
This one does only text characters.
Your graphic display video's convinced me to give it a try.
I don't have any default gcb displays laying around so let me know how the rotating cube went.
Hi, just an update...
I've received my displays and tried with the existing ssd1306 and gcld gcb code from the demo files directory and it works great. Thanks.
1) Geekcreit® IIC I2C 2004204 20x4
GCBcode: display_analog_port_value_on_lcd_display_using_i2c_lcd_data_bus_mega328p.gcb
2) 0.96 Inch Oled I2C Oled Display 128X64 SSD1306
GCBcode: glcd_simple_oscilloscope_mega328p_for_ssd1306@16.gcb
sprites_for_mega328p_and_ssd1306.gcb
3) 0.91 Inch Oled 128X32 Display SSD1306 I2C
GCBcode: glcd_simple_demonstration_hardware_i2c_with_timed_updates_mega328p_for_ssd1306_128_32@16.gcb
Great to hear!!
Nice.
I was thinking of making a portable dedicated Stand-Alone I2Cscanner with one of these SSD1306 displays.
That depends on how much has to be displayed.
The problem arises with these displays already on I2C, how to scan the I2C-bus properly for a second unknown I2C-address device?
Couldn't this be done by just eliminating the address of the display after the scan and so remains the I2C address of the scanned device?
Last edit: Haroen 2021-01-23
Repeating... I would use the I2C Discovery program((s) in your demo folder - this the quickest way to test all the I2C devices,