[How to do instruction] LCD/OLED display using pydPiper

[rh2018]

Hi Remy,
I notice there are some recent minor changes to pydPiper (https://github.com/dhrone/pydPiper). Does your original how-to still apply to moOde 6.5.2 with 16x2 and 20x4 lcd i2c displays?
Have any other users used the install procedure without changes with latest moOde and Raspian releases?
Regards,
Richard.

[DRONE7]

thank you @remy1961 !!!!!!!


My name is Jose Rey, I'm from Argentina.

I read you tutorial and it was posible to me; to configure mi Raspberry Pi 3+  & Piano 2.1 & OLED 0.93" (128*64) i2c interface.





EDIT:  I got a LCD 20x4 with I2C  (HD44780 BACKLIGHT Blue + I2C PCF8754 ); now I've this LCD in my player.






Again, thanks @remy1961 !!!!!

You can use both displays with different outputs...
see my trials here...
http://moodeaudio.org/forum/showthread.p...=piano+2.1

[rh2018]

Hi Bob,
All good now.
Since last time I used Remy's how-to the pydPiper developer has made some minor wording changes to the questions in configure.py.
There are some other fairly recent updates in the repo as well.
Running very well on moOde 6.5.2
Richard.

[funhouse61]

Hi !
First of all thank you for the job done !
my raspi is b+ v1 2 and oled display midaseh002004a 20x4 with moode audio 6.2.

My first installations were going normally, but since recently when I do the test everything is ok and after the final installation I have this kind of display

and it continues even when I start the music, yet I haven't changed anything in the way I install pydPiper.
otherwise I am doing tests on this model of raspberry to familiarize myself with pydpiper and the modification of my page eventually the screen will be coupled with a raspi 3 and a digione card and a sofstart by audiophonics with gpio replicator.
and on this subject should I modify anything, wiring or the script of pydPiper so that everything works together ?
sorry I still have questions, I find that the refresh rate is very long the display is always half a song behind the reality is it due to the raspi which is not the most efficient or I can change something? my screen is wired in parallel to the fact.
last question I tried to integrate tracktype on the screen but once installed here is what it gives.

On the other hand, if you need my pydpiper configuration, you should also explain to me how to get them back to you and send them to you.
sorry for all these questions but i'm starting and i don't know much about it.
I specify that I searched the various forums and on github before posting here but that I did not find my answers.
Please help me !!!

[funhouse61]

I will try with the latest version of moode to see if it changes anything, which I doubt, I am thinking more about a bug on the part of de pydpiper. In addition everything worked very well during my first installations.

[TheOldPresbyope]

I will try with the latest version of moode to see if it changes anything, which I doubt, I am thinking more about a bug on the part of de pydpiper. In addition everything worked very well during my first installations.

The obvious question is, what did you change between the first installations which "worked very well", whatever that means, and the final installation? Suspecting a bug on the part of such a well-tested component as pydPiper seems premature.

I don't have any LCD/OLED displays to work with and I couldn't even find a datasheet online for your "oled display midaseh002004a".

Offhand, the pictures you posted suggest your display is basically functional but displaying incorrect glyphs. Could be wrong driver for the controller on your board, wrong configuration of pydPiper, or possibly even incorrect wiring of data lines if a parallel interface.


Regards,
Kent

[funhouse61]

I will try with the latest version of moode to see if it changes anything, which I doubt, I am thinking more about a bug on the part of de pydpiper. In addition everything worked very well during my first installations.

The obvious question is, what did you change between the first installations which "worked very well", whatever that means, and the final installation? Suspecting a bug on the part of such a well-tested component as pydPiper seems premature.

I don't have any LCD/OLED displays to work with and I couldn't even find a datasheet online for your "oled display midaseh002004a".

Offhand, the pictures you posted suggest your display is basically functional but displaying incorrect glyphs. Could be wrong driver for the controller on your board, wrong configuration of pydPiper, or possibly even incorrect wiring of data lines if a parallel interface.


Regards,
Kent

hello, thanks for answering me.
http://www.farnell.com/datasheets/256640...nkQAvD_BwE

well what happened is that I was experimenting with modifications to the organization of the screen and as I didn't know much about it I was fumbling. So often I had to start everything over again, I tried to uninstall pydPiper, several times, but without success, I started all over again, installing moode and pydpiper but without problem 2 or 3 times . Which leaves me thinking that it might be a bug. but if you think something else why not.
I was just changing the screen's config page and when it didn't suit me I would reinstall everything from scratch so basically I didn't change anything.
  Then, for the final installation: I'm talking about the Rémy1961 instruction guide, that is to say after the test there is the finalization of the installation, on page 1. for me now the test is carried out without problem but it is after this finalization step that it does not work.
  So, whether it's a bad wiring, a bad driver or a bad configuration it wouldn't work right from the test, right?
  on the other hand I will try immediately with the last version of moode audio to see if that changes anything.
  please forgive me but it's google traduction, if you don't understand.

[funhouse61]

hello, so try with the latest version of moode freshly downloaded.
So, as in the Remy1961 instruction guide on the moodeaudio forum I do, the test.
That's what happens.
and after final installation.
I try to restart pydpiper,
It's worse.
I will start all over but without doing the test and I will see.

[TheOldPresbyope]

hello, so try with the latest version of moode freshly downloaded.
So, as in the Remy1961 instruction guide on the moodeaudio forum I do, the test.
That's what happens.
and after final installation.
I try to restart pydpiper,
It's worse.
I will start all over but without doing the test and I will see.

[Don't worry about language translation. The only thing that matters is presenting enough information to allow a diagnosis.]

Ok. So your second image demonstrates in a picture rather than in words what you meant by "worked very well." 

This result would seem to rule out my first and third possibilities: wrong driver or wrong wiring. 

This leaves my second possibility, misconfiguration of pydPiper, as well as your suggested possibility of a bug in the software.

Since I have no LCD/OLED hardware to test with pydPiper, I can't help debug your configuration. Sorry.

Good luck.

Regards,
Kent

[funhouse61]

bonjour, alors essayez avec la dernière version de moode fraîchement téléchargée.
Donc, comme dans le guide d'instructions Remy1961 sur le forum moodeaudio que je fais, le test.
Voilà ce qui arrive.
! [IMG_0252] (https://user-images.githubusercontent.co...da0e6.JPEG)
! [IMG_0253] (https://user-images.githubusercontent.com/ 60401472 / 89038245-45c30d80-d340-11ea-9e45-dd4a1049de65.JPEG)
et après l'installation finale.
! [IMG_0254] (https://user-images.githubusercontent.co...ed9dc.JPEG)
J'essaye de redémarrer pydpiper
,! [IMG_0255] (https: // utilisateur- images.githubusercontent.com/60401472/89038417-989cc500-d340-11ea-8a08-bc354a80eff4.JPEG)
C'est pire.
Je vais tout recommencer mais sans faire le test et je verrai.

[Ne vous inquiétez pas de la traduction linguistique. La seule chose qui compte, c'est de présenter suffisamment d'informations pour permettre un diagnostic.]

Ok. Ainsi, votre deuxième image montre dans une image plutôt qu'avec des mots ce que vous entendez par «très bien fonctionné». 

Ce résultat semble exclure mes première et troisième possibilités: mauvais pilote ou mauvais câblage. 

Cela laisse ma deuxième possibilité, une mauvaise configuration de pydPiper, ainsi que la possibilité que vous suggérez d'un bogue dans le logiciel.

Comme je n'ai pas de matériel LCD / OLED à tester avec pydPiper, je ne peux pas vous aider à déboguer votre configuration. Désolé.

Bonne chance.

Cordialement,
Kent

Bonjour C'est bon merci d'avoir répondu.
 regards, Johannes