Solved Duet2 ethernet and 12864 display using ST7567
-
@droftarts
Use the images from this link https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/tree/master/Copy to SD Card root directory to update or build your own from the latest sources if your screen isn't listed.Make the following adjustments
- add
M409 K"job.file.fileName"
in start.g - add
M118 P2 S"//action:cancel"
in stop.g - add
M118 P2 S"//action::paused"
in pause.g - add
M118 P2 S"//action::prompt_begin Resuming"
in resume.g - add
M575 P1 S2 B57600
in config.g of RRF to set baudrate to 57600(The baudrate of the TFT and motherboard must be the same)
There is an RRF specific config.ini to use as a base with all the RRF requirements preset and thats in the same folder as the image above. Just rename it from config_rrf.ini to config.ini and flash as normal
- add
-
@jay_s_uk Thanks, interesting. I'll have to get hold of one, and write up how to connect them in the wiki.
Ian
-
@droftarts i'll be adding it to our wiki for the LPC/STM port shortly.
The functionality has only been added in the last few days so I'm just waiting for it to settle down a bit.
I'll drop you a link when I've added it -
Thanks for the information @droftarts. I've just ordered one of the mini displays for my Duet ethernet.
I'll probably get a second and a duet mini if I like the interface. Sounds like it's configurable so I can get it set up with just the menu options I need.
I found out about this via the post you linked me to about using the display and now I have the pinout I'm really looking forward to seeing it work.
Thanks again
Barry M -
@CNCModeller and @dc42 confirmed that I've got the pinout correct! I'll update the wiki when I get a moment.
Ian
-
@droftarts said in Duet2 ethernet and 12864 display using ST7567:
@CNCModeller and @dc42 confirmed that I've got the pinout correct! I'll update the wiki when I get a moment.
Ian
That's great, thanks Ian.
All the best
Barry M -
I’m going to be setting up one of the Fysetc displays with a Duet WiFi tomorrow. Thanks for the wiring layout.
If I only want display but don’t care about the SD cars I’m assuming I can do without some of the connections. Or are the all required? -
Hi @rilot I'd appreciate it if you'd kindly update us on how it went.
I assume you're going to need the SD +5v connection as a minimum... But I'm only guessing.
Mine won't arrive until the weekend
Many thanks
Barry M -
OK, I got it working apart from the backlight. I'm guessing that the DuetWifi doesn't support the NEOPixel RGB. We have a connection for it though in the pinout for connecting the Mini 12864.
-
@rilot can you control it using M150? This from the Duet 3 Mini 5+ section:
When using a version 2.1 controller, the colours of the three Neopixel LEDs built into the display can be set using the M150 command with LED type parameter X2.
Ian
-
@droftarts I'm using a Duet2Wifi and M150 results in a Command not supported error. This is with 3.2.2
-
@rilot said in Duet2 ethernet and 12864 display using ST7567:
@droftarts I'm using a Duet2Wifi and M150 results in a Command not supported error. This is with 3.2.2
Same here on Duet Ethernet... no baclight and M150 "Command Not Supported"
At least its working, I can now look at a custom menu set.
I built a little connector conversion board to address custom the loom requirements, see below.
Thanks for the help folks
Cheers
BPM -
Hi guys, it there any information on @rilot and my issue re Duet Ethernet / WiFi and the 12864 display doesn't have a working backlight and M150 "Command Not Supported".
Any thoughts would be much appreciated.
All the best
Barry M -
@cncmodeller
M150
is not supported on Duet2 due to lack of memory. There are some details in this thread but it is hard to follow. That thread specifically says V2.1 of the display (the one with a NeoPixel) does not work on Duet2.I can confirm a Fysetc V1.2 12864 display works on Duet2 with RRF 3.2.2, you just need a custom wiring loom. I have since moved on to a Mini5+ where the V2.1 is natively supported.
-
@fulg said in Duet2 ethernet and 12864 display using ST7567:
@cncmodeller
M150
is not supported on Duet2 due to lack of memory. There are some details in this thread but it is hard to follow. That thread specifically says V2.1 of the display (the one with a NeoPixel) does not work on Duet2.I can confirm a Fysetc V1.2 12864 display works on Duet2 with RRF 3.2.2, you just need a custom wiring loom. I have since moved on to a Mini5+ where the V2.1 is natively supported.
Thanks for the heads up.
As I've got one of the 2.1 displays now, perhaps I can drive the neopixel from a separate Arduino using the neopixel library? I just want a backlight running.
If so do we know which pin is the neopixel data pin? It's not obvious to me from the fysetc page.
http://wiki.fysetc.com/Mini12864_Panel/
Many thanks
-
@cncmodeller The schematic for the display is here: https://github.com/FYSETC/FYSETC-Mini-12864-Panel/blob/master/hardware/V2.1/Mini12864(RGB)V2.1_sch.pdf
Looks like the Neopixel control signal is the "Red" pin 5 on EXP1
-
@gloomyandy said in Duet2 ethernet and 12864 display using ST7567:
@cncmodeller The schematic for the display is here: https://github.com/FYSETC/FYSETC-Mini-12864-Panel/blob/master/hardware/V2.1/Mini12864(RGB)V2.1_sch.pdf
Looks like the Neopixel control signal is the "Red" pin 5 on EXP1
Thanks @gloomyandy I'll give it a go and report back.
-
@fulg said in Duet2 ethernet and 12864 display using ST7567:
M150 is not supported on Duet2 due to lack of memory
This statement frightens me. I'm planning on writting big(ger) meta command macros for Duet2.
Now I'm afraid they don't fit....or is the Neopixel library so huge? -
@o_lampe it’s running out of flash ROM space for the firmware, not RAM. Your macros should be fine.
@CNCModeller I have asked @dc42 if he can add Neopixel support to Duet 2; the other forum post suggested he was going to look into it, and I don’t see a reply about lacking memory (though I know it is tight). If it isn’t possible, I’ll update the documentation to say that only boards with single colour backlight (ie v1.2 of Fysetc 12864 LCD) are supported.
Ian
-
@droftarts thanks for the update! It's usable now but not great. I'll hang on for an update from @dc42 but can always fall back on a separate Arduino if required.