Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - SLTom992

Pages: [1]
1
OLEDs / Writing Messages with NHD-2.23-12832UCB3
« on: July 29, 2014, 01:55:59 PM »
While trying to use

Code: [Select]
    Show_Font57_12832(1, 17, 0, 4);
    Show_Font57_12832(1, 18, 0, 12);
    Show_Font57_12832(1, 19, 0, 20);
    Show_Font57_12832(1, 20, 0, 28);
    Show_Font57_12832(1, 34, 0, 36);
    Show_Font57_12832(1, 35, 0, 44);
    Show_Font57_12832(1, 36, 0, 52);

(0 1 2 3 A B C)

I am unable to get the letters to be any closer than with without distortion of the distance on only some of the letters.

Can anyone suggest why this would be or does anyone have a better function that works correctly? I've tried quite a few different things without getting anywhere. The SSD1305 manual is definitely not clear on this subject.

2
OLEDs / Re: NHD 2.7 Screen Image Streaking
« on: July 29, 2014, 12:42:25 PM »
I know that if you initialize the controller with a Display Offset you can get smearing though I don't know why. Make sure that your offet is zero.

3
OLEDs / Re: Scambled Eggs
« on: July 28, 2014, 03:46:49 PM »
After verifying all of the lines and the control waveforms I got a second display and got precisely the same results.

After knocking my head against the table three or four times I looked at the base drivers again and realized that whoever had written that original code which I had modified had made a major mistake and stupidly I had followed their lead.

The drivers ALL lead with resetting the SSD1305 and so NO command had any effect beyond the default initialization except the very last command accomplished. Once the resets were removed not only were all four lines of the display working but the display was turned right-side up as in the advertisements because in the init function is the remap functions that accomplish that but wouldn't work in my testing because of the resets on each command.

Since I included the code and since these resets are in the original drivers it should have bit the Newhaven people in the butt immediately. So perhaps they simply aren't monitoring these groups.

In any case it appears that their functions are mostly correct. I still have to work on their alphanumeric display since they have a full space between each character instead of allowing the characters to be adjacent.

4
OLEDs / Re: Scambled Eggs
« on: July 27, 2014, 10:58:09 AM »
There is something else that is bothering me - in the pictures that show this display it shows the "top" of the display as being in the upper left with the connector down. We designed our board with that in mind.

I have managed to get the display to operate showing one line only and it is upside down from the pictures.

In the manual it DOES show the zero column and zero row as being in the lower right with the connector at the bottom as it more or less operated. But you have to search for it. This is on Page 3 of the specification sheet and is very easy to miss. So if this is so, why are the available fonts upside down compared to what is being shown in the photographs of the display on the advertisements? Did I get a factory second?

None of the functions seem to operate as is implied by their names and the descriptions of the input values.

If you are selling a display wouldn't it be appropriate to have some library functions that operate with a minimal amount of work to demonstrate the operation of the device? Quite frankly I'm rather surprised at the treatment of a display that could be quite helpful on small handheld instruments of all sorts where a large display would be unnecessary and expensive and time consuming to program.

I have tried to add a picture of the display with the single line and the noise on the rest of the display. But the file size is too large even in a GIF.

The characters show that the DATA lines are working OK and that the commands are therefore available. The question is why only the single line? Why won't the display clear? Why does "fill" only work on that single line?

If I use the "Frame" function the frame shows the LOWER edge of the frame with the sides disappearing up.

5
OLEDs / Scambled Eggs
« on: July 25, 2014, 04:22:03 PM »
I have the 12832 function library for the NewHaven NHD-2,23-12832. I made some modifications on the drivers since I have mine set up for 8080 and not 6800.

When I turn the display on I get a screen full of hash. None of the functions seem to do anything except Display_On_Off(); and possibly init though that may not work and the defaults allow it to work.

It appears as if it isn't getting any data writes. So here is driver for both Command and Data with the only difference the polarity of the D/C line: (PIC18)

Code: [Select]
   

( In the main init routines)

    TRISA = 0b00000011;
 
    ANSELA = 0x03;
 
    ADCON0 = 0b00000101;                // ADC 1 Enabled
    ADCON1 = 0b00000000;                // V ref = power and ground
    ADCON2 = 0b00111110;                //

    PORTA = 0b00000011;
    PORTC = 0b00100000;
    PORTD = 0b00000000;

// In Display.c

#define GPIOB PORTD
#define GPIOC PORTD
#define Send_Data (PORTA | 0b00010000)
#define Send_Command (PORTA & ~(0b00010000))
#define Chip_Deselect (PORTA | 0b000100000)
#define Chip_Select (PORTA & ~(0b000100000))
#define No_Read (PORTA | 0b00001000)
#define Read (PORTA & ~(0b00001000))
#define Write (PORTA & ~(0b00000100))
#define No_Write (PORTA | 0b00000100)
#define Dis_Reset (PORTC & ~(0b10000000))
#define Clear_Reset (PORTC | 0b10000000)

void oled_Command(unsigned char Data)   // 8080 mode
{
    LATC = Dis_Reset;
    LATC = Clear_Reset;
    LATA = No_Read;
    LATA = Send_Data;
    PORTD = Data;
    LATA = Chip_Select;
    LATA = Write;
    OLED_uDelay(0x04);               // Wait 100 usec
    LATA = No_Write;
    LATA = Chip_Deselect;
}


I have a two input scope and WR and CS work properly so I assume the other outputs are as well.

And anyone suggest why none of the functions such as Fill_Block, Fill RAM, Checkerboard, Show_Font57_12832(1, 17, 10, 10); and the like aren't working?

6
OLEDs / Re: NHD-2.23-12832UCB3 C Library
« on: July 16, 2014, 10:10:13 AM »
Thank you for that component library.

Do you also have the waveforms for the 8080 interface? They aren't in the document for the SSD1305 or the Newhaven part.  I appear to be freezing up since the transmissions aren't completing correctly.

7
OLEDs / Re: NHD-2.23-12832UCB3 C Library
« on: July 14, 2014, 11:28:43 AM »
I have written most of the code but am missing the font tables. Are there font tables available? That seems like the most time consuming and the thing that would give people more problems. I would hate to have to sit around here and write 100 different characters on graph paper and then convert that to a font table.

8
OLEDs / Re: NHD-2.7-12864UMY3
« on: July 12, 2014, 03:51:32 PM »
Can someone tell me why there are all these delays in these programs? When I look at the clock speed of the display controller compared to the clock speed of most of the uP's controlling them it looks to me as if the display is much faster. So why would a delay be inserted all over these operations? Not to mention if you have a display added onto a uP doing other work you don't have the time to be waiting for delays to occur and you sure don't have time to put yet more instructions into the interrupt routines and slow them up.

9
OLEDs / NHD-2.23-12832UCB3 C Library
« on: July 11, 2014, 12:57:13 PM »
Is there a C library available for this component that has an ASCII set-up and at least a demonstration of the graphics? All of the libraries I've found on line have a lot of stuff missing out of them. I have a parallel interface.

Pages: [1]