The display output was working immediately, there was only a minor issue in the APP_LCD_Clear() routine (6 lines cleared instead of 8 )
Best Regards, Thorsten.
Nice 
I have also written a driver for the DOG clcd using SPI, it seems quite a bit quicker than the parallel driver so do you think it is worth committing? If so what should I call it? dog_spi ?
It would be useful if people wanted to use more than 2 of them.
Cheers
Phil
Yes, would be nice if you could add this driver as well. “dog_spi” sounds ok
MIOS: In order to select the display, just add a “USER_LCD_Select” function (with exactly this name) to the driver, it would make it compatible to clcd_multi
MIOS32: the function to select a LCD device is already part of MIOS32, the LCD number is stored in mios32_lcd_device. This function is only used for CLCD drivers, as we need to address the displays separately once special characters should be initialized. GLCD drivers usually allow to combine multiple displays to a big screen without any restrictions, so that a device selection isn’t required.
Best Regards, Thorsten.
The MIOS32 based DOGM touchpanel driver
Best Regards, Thorsten.
tk and phil: thank you!
i’m really looking forward to being able to get what i want out of my live controller. this is gonna rock.
for those who don’t know: this is for a $15 touchpad that can be attached to the low cost DOG character lcds (the m size) available at mouser.
so now we all have the ability to put touchscreens on our midiboxes for x/y pads and menus.
Ubercoolische!
Thanks T.
hey phil: i have a couple questions and comments about connecting this and your schematic:
did you limit the current from the 5v b+/b- source? your schematic shows a resistor to the cathode but it doesn’t say a value.
your connections to anode and cathode from b+/b- are backward. also should be 9x1uF capacitors, and i believe they can be polarized because the pins of the lcd are labeled p and n. i’m sure non-polarized are ok but harder to find in that capacitance (is this correct?).
does it count backward with the data lines? you connect your first to d7 and i’m assuming it goes backward from there to other lcds? in my pcb schematic i’ve connected like this:
D7 –> lcd1
D6 –> lcd2
D5 –> lcd3
D4 –> lcd4
D5 –> lcd5
i’ve also adapted this to the pinning of the core32’s lcd header instead of the regular core. i’m not sure if the pinout is the same (doesn’t matter i guess), but are any of the actual connections different?
thanks!
ultra
Hi Ultra.
Yes I limited the current to the backlight as per the datasheet, 56R IIRC.
I always screw up anode/cathode connections on circuits (bit of a mental block I think) yes you are quite correct!
The datasheet doesn’t mention P/NP caps but the datasheet example uses NP and luckilly I had a never finished talkback project that used lots of 1uF NP so I stole them You may be able to use polarized but it could be a bit tricky working out which way round to put them. Maybe worth checking with TK to see what he used?
Yes you are quire correct about the data line assignments. I moved away from the conventional D0=lcd1, D1=lcd2 because I am using an 18F4685 and D0-D3 are not available so I thought that I would start at D7 instead!
AFAIK, the pinout for the CORE32 LCD is different to the CORE8 to make it more 1-1 for standard CLCD’s so you may need to change it a bit…
Cheers
Phil
Sorry, you are quite right, with the N and P connections on the LCD connections, you should be fine with 1uF polarized electrolytics…
Cheers
Phil
thanks PT!
edit:
so does this mean that for mios32/core32, i want lcd1 = d0, lcd2 = d1, etc..?
i’m not even plugging this into the pic core at all.
Yes with the CORE32, d0=lcd1, d1=lcd2 etc etc.
Phil
thanks PT.
TK: i might be living in excess here, but i was hoping to connect 5 of these touchpanels. i suppose there’s only room on the core32 for 3 of these?
Hi all,
I created some Eagle libraries:
http://www.midibox.org/dokuwiki/doku.php?id=eagle_midibox_library
I will create the related schematic and Eagle3D the next days.
Best Regards
Jack
Hi all!
Have someone checked if one of this displays fits into Wilba’s Sequencer?
Best Regards
Jack
Hi Jack!!!
Yes, I check this: there are no 2x40 DOG LCDs available, but large displays which are properly aligned to the 16 GP encoders and buttons are essential for the ergonomic user interface.
Best Regards, Thorsten.
Hi Thorsten,
Yes, I check this: there are no 2x40 DOG LCDs available, but large displays which are properly aligned to the 16 GP encoders and buttons are essential for the ergonomic user interface.
I know.
Which distance have the encoder to each other?
Is there enough room to fit 6 displays (3 Encoders per display)?
Can you send me your Eagle schematic (mbhp_lcd7_dog.pdf)?
I want to use it for my Eagle library.
Best Regards
Jack
Yes I thought about this as well.
If you put 3 x DOG CLCD’s together, the viewable would be approx 165x15mm. For this you will get a 48x3 display. The viewable area is fairly close to a 40x2 size CLCD viewable area (152.5x16.5) I don’t know how big the slots on Wilba’s panel are but it could possibly be made to work.
I’m not sure how workable it would be and whether 48x3 is a usable size. The current SPI based DOG CLCD driver (that I have just committed) would support up to 8 of them so 6 could replace the 2 off 40x2 displays…
Cheers
Phil
Hi Phil,
my idea was to use six DOGL128-6 (128x64 or 67,8mm x 48,26mm). :)
But I don’t know if it is a good idea.
Best Regards
Jack
So, you really want to overwork all seq_ui* files for a derivative which is probably only used by yourself, because it’s more expensive (and slower) than really required?
Best Regards, Thorsten.
Hi Jack.
That would give you a pretty big display, about 150x6 with the standard font
The ‘actual’ window size is about 34mm, 48.26 is the external dimension but still pretty big!
Not sure if it would fit though and as TK said you would have to redo all of the UI…
Phil