Propellor Head
by i-Bot
Tue Feb 26, 2008 3:48 pm
I uploaded the Spin files for the Propellor head LCD with the added option to display bitmaps. I also added a bit to ignore Null bytes, since these were seen before the LCD port was initialised. The LCD port cannot send Null.
http://robosavvy.com/Builders/i-Bot/Rob ... .13%5d.zip
The spin code is programmed to the uOLED-96-Prop from the propellor tool. For this you need the propellor plug from parallax or the uUSB-MB5. You will need the objects contained in the archive, because the SD card driver is configured for the uOLED, and not standard.
The uOLED connects to the C3024 controller on the LCD port.
C3024 LCD Port Signal via 1.5K resistor to uOLED pin10 = propellor pin 18
C3024 LCD Port 5V direct to uOLED pin 1 - uOLED Vcc Supply input
C3024 LCD Port GND direct to uOLED pin 4 - uOLED GND ground
For bitmaps it only supports 96*64 .BMP files in 24 bit colour format. These can be created by the MS Paint program. Either create or copy an image and then resize to exactly 96 wide by 64 high. This is then saved as a .bmp file with 24 bit colour. The .bmp files must be located in the root directory of the micro SD card which is to go into the uOLED.
You will see a file "shrek.bmp" in the archive. You can change the spin code to use a dfifferent one on startup. To call an image from Robobasic using:
PRINT &H1b, &H60, "shrek", &HFF
This will display the file "shrek.bmp", or any other 96*64 24 bit .bmp file you have on the SD Card
Update to display is rather slow, at about 1.5 sec, so if anyone can speed it up, please help. The delays are in both the reading of the FAT filesystem, and in the display.
http://robosavvy.com/Builders/i-Bot/Rob ... .13%5d.zip
The spin code is programmed to the uOLED-96-Prop from the propellor tool. For this you need the propellor plug from parallax or the uUSB-MB5. You will need the objects contained in the archive, because the SD card driver is configured for the uOLED, and not standard.
The uOLED connects to the C3024 controller on the LCD port.
C3024 LCD Port Signal via 1.5K resistor to uOLED pin10 = propellor pin 18
C3024 LCD Port 5V direct to uOLED pin 1 - uOLED Vcc Supply input
C3024 LCD Port GND direct to uOLED pin 4 - uOLED GND ground
For bitmaps it only supports 96*64 .BMP files in 24 bit colour format. These can be created by the MS Paint program. Either create or copy an image and then resize to exactly 96 wide by 64 high. This is then saved as a .bmp file with 24 bit colour. The .bmp files must be located in the root directory of the micro SD card which is to go into the uOLED.
You will see a file "shrek.bmp" in the archive. You can change the spin code to use a dfifferent one on startup. To call an image from Robobasic using:
PRINT &H1b, &H60, "shrek", &HFF
This will display the file "shrek.bmp", or any other 96*64 24 bit .bmp file you have on the SD Card
Update to display is rather slow, at about 1.5 sec, so if anyone can speed it up, please help. The delays are in both the reading of the FAT filesystem, and in the display.
by i-Bot
Wed Feb 27, 2008 12:43 pm
You do need to put the files onto the Micro SD card from a card adapter in the PC. The SD card must be formatted as FAT16.
I choose not to use Graphics Composer, because when it puts files onto the SD card it seems to use a special format, and you have to pick up the sector address on the SD card from the text file created by the Graphics composer to address the files. The 16bit colour 565 format used is also not very common
So I figured best to use standard FAT format , and standard 24 bit .bmp files. I may regret this as the directory get bigger, and the disk fragmented !
I choose not to use Graphics Composer, because when it puts files onto the SD card it seems to use a special format, and you have to pick up the sector address on the SD card from the text file created by the Graphics composer to address the files. The 16bit colour 565 format used is also not very common
So I figured best to use standard FAT format , and standard 24 bit .bmp files. I may regret this as the directory get bigger, and the disk fragmented !
by limor
Sun Mar 02, 2008 4:05 pm
Hi, maybe your spam filter is deleting emails.
your package was received and signed for by someone called "Massaro" on Feb 25. check out this tracking page:
http://www.parcelforce.net/popup_POD.ep ... 40613223GB
your package was received and signed for by someone called "Massaro" on Feb 25. check out this tracking page:
http://www.parcelforce.net/popup_POD.ep ... 40613223GB
by grisuzone
Mon Mar 03, 2008 1:30 pm
Hi to everybody
I am very happy about the Seriousness of Robosavvy and I want to communicate him/it to everybody
You/they have very kindly contacted me to resolve the problem of my package not received
I wanted to make to know to all this Entrusted you
Robosavvy OK very serious shop
thanks
I am very happy about the Seriousness of Robosavvy and I want to communicate him/it to everybody
You/they have very kindly contacted me to resolve the problem of my package not received
I wanted to make to know to all this Entrusted you
Robosavvy OK very serious shop
thanks
by grisuzone
Wed Mar 19, 2008 8:46 pm
hi
He/she asks on oled
How do I do to recall from tails ROBOBASIC an image on OLED?
I would want to change expression (image) to ROBONOVA for every different routine
I for example call martial_arts_pose I stamp image hard
I call Dance I stamp image smile
How Robobasic I recall code in spin OLED?
thanks
He/she asks on oled
How do I do to recall from tails ROBOBASIC an image on OLED?
I would want to change expression (image) to ROBONOVA for every different routine
I for example call martial_arts_pose I stamp image hard
I call Dance I stamp image smile
How Robobasic I recall code in spin OLED?
thanks