|
|
I've considered CrystalFontz support but it'll be a little more effort as only the USB-A port on the V3 can do USB host, so it'll need USB hub support, which isn't available out the box (e.g. I'll need to implement the USB hub support myself). USB hubs are relatively simple, at last. Do you have a picture of the OLED as hooked up not working? |
|
|
See attached picture. |
|
|
Attached is the photo. |
|
|
If upload didn't work, picture can be view here... https://cloud.kc2wbx.com/index.php/s/LDeByfYbsnixwna |
|
|
Hmm, looks like something's up with the file upload feature, I'll check that. But yes, your photo looks pretty much ideal, strange that it's not working - did you buy the ones I linked on Amazon or another brand? If the latter can you let me know which? Otherwise I'll buy them again and see if there's anything that needs tweaked |
|
|
I purchased these... https://www.amazon.com/gp/aw/d/B079BN2J8V?psc=1&ref=ppx_pop_mob_b_asin_title |
|
|
Yup, those are the ones I've been testing on. Let me grab a few more to confirm they didn't change anything (like the I2C address). The OLED is actually controlled by the smaller chip near the front of the PCB, which also does the VCOM serial command line you get when you connect a computer to the micro USB port. Are you able to connect that and confirm that you get the command prompt? |
|
|
The command line works 100%. I also upgrade to latest firmware just in case that was the issue. |
|
|
I had the exact same problem. OLED display not working, CLI working / PCB working fine - sadly i can not buy the recommended display in my country. - bought a cheap "SSD1306" version from aliexpress - was not working - Found out that third pin has to be "SCL" and not "SCK" - I accidently bought the wrong communication variant (documentation should be updated) - i bought the Gerui variant from amazon - https://www.amazon.de/dp/B0CT2QP43S - NOT WORKING (not sure if DOA or just not working, didnt test any further) - i bought the Makerhawk variant from amazon - https://www.amazon.de/dp/B07BDFXFRK - Works! - I have to idea what the difference between the Gerui and the Makerhawk one is. One reads YY D525 and the other YY 202301 on the silk screen - let me know if i can help with testing. Btw i socketed the display to move it into a 3D print later on :) - And helped me with testing the different displays. |
|
|
Oh, that's excellent to know, so there's definitely some kind of difference. I can't find Gerui on Amazon.com but I'll just grab a random selection of even more brands and try those to see if some of them don't work. Hopefully it's as something as an unexpected I2C address and I can just tweak the code. |
|
|
I think the names are just random fake names. Maybe it is just an issue with voltage? (specification reads 3,3 to 5v) since the communication protocol is the same? I noticed that the same shematic was posted on my makerhawk (working) amazon listing as pb4610 link (which was not working) |
|
|
I tried the Amazon (https://www.amazon.com/iPistBit-Display-Luminous-Compatible-Raspberry/dp/B0D2NRMHM9) part you had in a link but still no output �. USB terminal still works. |
|
|
I've grabbed a few different brands from Amazon, some work instantly, some work intermittently, so I'm hoping I can take a look at improving compatibility with the intermittent ones which should fix this issue. |
|
|
Hi, please try the attached firmware update. This update only updates the chip that controls the display/USB so it should apply pretty quickly, though the virtual serial port will disappear during the update. Also, the red light will flicker whilst the chip is being updated to indicate activity. Actual update instructions are the same as usual per https://issues.tattiebogle.net/dokuwiki/doku.php?id=mantis:ide_simulator:v3#firmware_upgrades screen20251014.fw (27,392 bytes) |
|
|
I tried doing the firmware update but all I'm getting is a flashing X led along with the attached output from the virtual serial console.
Screenshot 2025-10-19 173808.jpg (61,006 bytes) |
|
|
Ok, I figured it out. I had to downgrade to firmware update0508.fw (Initial release for V3), then apply the screen20251014.fw which now the screen works (HURRAY!!!). |
- Anonymous
