J'utilise une autre bibliothèque :
[url]https://github.com/olikraus/u8g2[/url]
Ici, à des fins de test, mon changement, y compris l'évaluation modifiée de l'encodeur d'Alain :
---- deleted----
Ce n'est donc pas une version officielle, juste pour tester !

Changement: En raison de problèmes possibles. Archive Zip supprimée.

oublier quelque chose....
J'ai eu une brève interruption de quelques millisecondes aujourd'hui quand j'ai coupé. J'avais déjà coupé exactement la même pièce deux fois sans aucun problème.
Le résultat ressemble à ceci : J'avais l'écran 128x64 connecté, il se peut donc que cela cause des problèmes ?

Feldsalat a écrit : mer. nov. 06, 2019 5:02 pm J'utilise une autre bibliothèque :
[url]https://github.com/olikraus/u8g2[/url]
Ici, à des fins de test, mon changement, y compris l'évaluation modifiée de l'encodeur d'Alain :
LMFAO_V4_7_12864_031119.zip
Ce n'est donc pas une version officielle, juste pour tester !

Alright
Yes me too when i test the display without the cnc firmware , the screen work fine ( nice refresh ) But it's normal ! i have just to print and that all ^^

But i found a explaination about my time to display ! On the RAMP 1.4 the Ext2 is used to talk in SPI .
Therefor this SPI is used with a Software solution and not a Hardware solution ! CF Issue : [url]https://github.com/olikraus/u8g2/issues/87#issuecomment-261021039[/url]
I understand now why on my ender 3 ( pluged in ext3 ) work Fine !
But in the pinout definition for the 2560 mega. The SPI pinout is 50 51 52 53:
And in my class LCD where i construct my class i call this pinout : So the solution wille be to plug the LCD on the SPI HW !

For your interruption, yes, I think this is the root of the problem ( or not ^^ ) .
For me, i comment all méthod called to display on the screen when i'm in PC mode And Tadam ! it work

Hmmm .. Wrong way ... The adapter is pluged on the Aux3 ( ramp ). So, it's well connected to the HW SPI :s ... But i don't understand why when i use this pins for the instance of the lib ... The screen Work Oo ... Okay ... Back to investigation

The 128x64 is a serial display, therefore pin 16/17 -> TX/RX2
With my machine the display runs almost without any problems. Have you tested my Arduino Sketch?

Feldsalat a écrit : mer. nov. 06, 2019 10:26 pm The 128x64 is a serial display, therefore pin 16/17 -> TX/RX2
With my machine the display runs almost without any problems. Have you tested my Arduino Sketch?

I tested your sketch but the 128x64 LCD doesn't work :/

But i try your u8g2 lib and it's work ! it's faster than my lib !

This is my repository : https://github.com/ThibaudetTevai/cnc_filchaud
( In Work In Progresse )

The version of GitHub doesn't work for me. Compiles only after changing from <include "Bounce2.h> to #include "Bounce2.h" in rotBtn.h
Both displays show nothing (reasonable) and the beeper does not sound as usual.

Feldsalat a écrit : jeu. nov. 07, 2019 10:09 am The version of GitHub doesn't work for me. Compiles only after changing from <include "Bounce2.h> to #include "Bounce2.h" in rotBtn.h
Both displays show nothing (reasonable) and the beeper does not sound as usual.
IMG_20191107_094933802.jpg

Okay Thanks for your feedback
Yes i put Bounce2.h if the dev. haven't the lib. in his personal Arduino library

I cut the ISR Buzzer because every reboot of the FW the program is beeping the Buzzer and it disturbs my entourage at the end of the 30th "biiiip" :p

In this moment i switch back to the ISR Uart with register. Before I was under the arduino Serial Librarie ( and he was work fine ).
Now the TX_WRITE() work but the ComParse() does not seem to work.
I need to put a wire on the debug pin for see if the FW through in the Comparse() methode

FR:
Ok merci pour ton retour:)
Oui je mets Bounce2.h si le dev. n'a pas la lib. dans sa bibliothèque arduino

Je coupe l'ISR du Buzzer car à chaque reboot du FW le programme fait biper le Buzzer et cela dérange mon entourage au bout du 30 éme bit :p

En ce moment je reviens à l'UART configuré via Registre. Avant j'étais sous la bibliothèque d'arduino (et elle marcher bien).
Maintenant, le TX_WRITE () fonctionne mais le ComParse () ne semble pas fonctionner.
J'ai besoin de mettre un fil sur la broche de débogage pour voir si le FW passe dans la méthode Comparse ()

For your information:
Again I had short interruptions while cutting. This time with 2004 display. But I had forgotten to comment out the "u8g2 library". It is not needed, but can it still cause problems? At the next cuts I will see...

Feldsalat a écrit : jeu. nov. 07, 2019 9:45 pm For your information:
Again I had short interruptions while cutting. This time with 2004 display. But I had forgotten to comment out the "u8g2 library". It is not needed, but can it still cause problems? At the next cuts I will see...

Oh ! So if you have again the problem , that mean is not the screen :/
Same thing for the librairie . When you compile and if you not use an function from the U8g2 lib, the compiler didn't include some code from this lib.
The declaration #include say at the compiler "get this file and find the function i use in this code" . Maybe you should put a trace on debug pin with an oscilloscop . But at this point and in my experience in Jedicut/Alden i see no solution :s

PS : I burned 2 pololu this night xD ( with fan on it ) xD