Difficulty integrating μOLED-128-G2 with Propeller
guitar_plr
Posts: 31
Hi All,
Just picked up the μOLED-128-G2 (parallax site said G1 but I got a G2). I followed the connection instructions for the sample object in the OBEX, with connection to my PPDB board:
Pin
1-> +5v
2-> TX (P7)
3-> RX (P6)
4-> GND
5-> RES (P5)
I tried loading the sample program "μOLED-128-GMD1_Demo" to the propeller, but when I power on all I get is the 4D Systems splash screen, followed by an analog/digital clock. Nothing seems to show up on the screen other than the built-in demo. I've also removed the jumper across pins 6+8 (per the 4D manual) to bypass any slide show.
Any ideas?
Thanks.
Just picked up the μOLED-128-G2 (parallax site said G1 but I got a G2). I followed the connection instructions for the sample object in the OBEX, with connection to my PPDB board:
Pin
1-> +5v
2-> TX (P7)
3-> RX (P6)
4-> GND
5-> RES (P5)
I tried loading the sample program "μOLED-128-GMD1_Demo" to the propeller, but when I power on all I get is the 4D Systems splash screen, followed by an analog/digital clock. Nothing seems to show up on the screen other than the built-in demo. I've also removed the jumper across pins 6+8 (per the 4D manual) to bypass any slide show.
Any ideas?
Thanks.
Comments
Turns out the G2 is a lot different than the G1, and there are several steps to even getting it to understand serial commands. And even one you get that far, a new driver is required, as the serial commands from the G1 driver don't work (the G1 driver is on OBEX).
I don't have time for all the details right now, but step one is to get a serial environment into the unit. That's done with a programming environment found on 4D's site.
More later, if you're interested.
Jim
I appreciate the reply. Wow had no idea they were that different. So the display actually has to be set up internally before you can interface with it? I'll tinker around and see if I can get it set up per the 4D site and get some serial commands to the display.
If you have some time and could elaborate on what you did to get it working that would great!
Thanks!
In any case, Step 1 is to work through the 4D site to find their Workshop 4 IDE download. With that installed on your PC, and after you load the Serial Environment on the G2, you can start poking the G2 using serial commands. These commands can be found in pdf buried in the 4D site. Don't forget the baud rate of the G2: it turns out that can be changed during the set up, so obviously if that happens, you'll need to adjust what ever you're using to connect to the G2. I used a little terminal program that is included in the Workshop 4 IDE, and started out at 9600 which is the default rate once the serial environment is loaded.
Step 2 is to figure out what commands you really need for your project, and write up a driver method for getting the propeller to send them out to the G2, as well as receive the ACK from the G2. For example, I need only text (a few colors) and rectangles for my project, so I didn't bother with most of the serial commands. First I tested them with their little terminal program, and after confirmation that the commands really worked, I wrote them into the driver method. For example, there are some commands that seemed only to freeze the display (ie changing baud rate on the fly). I didn't bother figuring out what's up with that.
Oh, and one other thing: sometimes when powered up, the G2 seems to be frozen. I dealt with this by sending a RESET signal from the propeller, waiting for the G2 to come alive again, and then started sending it serial commands.
I like the G2, but for all this trouble, I would rather have a G1, with the kinks already clarified.
Hope that helps,
Jim
Jim: Thanks for the details. How did you connect the display to your computer for use with the Workshop 4 IDE? On the site it talks about using a proprietary usb cable to interface with the display.
Andrew: Good idea, I'm going to give Parallax a call to see if they have any updates. Resetting the prop after boot up of the display is not fixing the issue, though.
Thanks again!
You might log on to the 4D Systems forums and ask if you can download the uOLED-128-G2 with the PmmC file for the G1 SGC module.
Ratronic: The PmmC firmware that came with the G2 unit was weird: when put in the serial mode it seemed to indicate that the hardware was G1. But, the serial connection only worked if G2 codes were used. Also, I was able to update the PmmC firmware to version R24. There has been no change in the codes required to operate the unit, but at least it says it's a G2 on the display.
Chris: I recently purchased 4 of these G2 units from Parallax for a project of mine, thinking they were G1's. Now that I got them working, is there a chance I could get one more G2? Or how about a trade for a left-over G1 of mine?
Jim
After installing the older firmware then it would power up as a serial slave excepting SGC serial commands like used in the demo in the OBEX. Don't know if this will work for this model and when reprogramming the firmware (in Workshop 4 IDE) it says if you use another vendors cable it could void the warranty.
Chris: please let us know when you find out more from 4D Systems, and the next steps required.
Thanks!
I have a question relating to the 4D uLED screens as well:
I own a 1.7 inch uOLED-160-G1GFX module and I am not sure if I can use this with any of the existing Parallax OBEX code or I'll have to re-write the drivers.
If I understand well from the documentation, it is a G1 module (the GFX refers to the fact that it can be used standalone as well).
Is there any difference, in terms of code, when this is used with the uOLED-160-GMD1 OBEX code?
Thanks!
- Will Parallax continue to offer G1 units?
- After beating my head against the wall getting the G2 units to work, I'd recommend that Parallax carry them. The screens seem brighter than the G1 units to my eye. With proper documentation and a good example program in the OBEX, they'd be fine.
Jim
As far as I can tell, the G1 model is no longer available which is why they sent us the G2. In testing a few other displays from 4D Systems, Kevin is more familiar with the new software, which is why he'll be spearheading the possibility of us carrying the G2 model.
The minimum delay required for a µOLED-128-G2 after Propeller power on seems to be 1150 milliseconds. Temperature seems to plays a role.
Cheers
http://www.4dsystems.com.au/downloads/Application-Notes/4D-AN-G1001%20-%20Migrating%20from%20GOLDELOX-SGC-GFX%20to%20GOLDELOX.pdf