Panel Due: now better AND cheaper!
-
what advantajes have this?
[[language]] If you have a Duet Ethernet or a Duet WiFi revision 1.01 or later and the PanelDue will be close enough to the Duet, you can now use just a 10-way ribbon cable to connect them together. The 4-way connector is still provided for users who wish to site them more than about 300mm apart. -
1. It's an easier cable to make.
2. You will be able to use the SD card socket on the TFT panel.
The disadvantage is the limited cable length.
-
Hi is there any reason why I couldn't use a long 10 pin cable such as this one
Sorry if this is a stupid question
-
1480mm is too long, the SD card's signals degrade at that length. 400mm is about the max.
If the PanelDue needs to be that far away, then you'll have to sacrifice using the SD card in the PanelDue.
-
Hi guys, can anyone please guide me to a BASIC user guide to start with DUET wifi without 1000 pages of engineer texts? I have just received the board last week and trying to see which firmware it is running and whether I need to update it before installing into the machine etc. So, far I was not able to find any clear guide about "Getting started with the Duet WiFi" (there is a place dedicated to that, but it has nothing there except for warnings).
Some pages are 404 error here, others do not match with the link text.
Shouldn't there be a simple thing somewhere which should say:
1. here is the link to the EXE tool you will need to work with your board.
2. here is the link to firmware files that are available atm.
3. Enjoy.Product is sold at a very premium price which assumes some sort of infrastructure available to work with it, right? Is there any?
Buying it I assumed there absolutely has to be a clear guide to firmware upgrades and a clear link to the tool to do that.I also tried to upgrade the firmware on Paneldue 7in hoping it may resolve quality issues, but with no luck, since PC does not even see the panel due controller at all. Screen turns on, but the device is not detected by PC. Which is okay I guess, because the quality issues on 7inch screen are very real and I took the risk buying it, now will need to return. The LCD ribbon in a back has a design flaw which is quite big - signals mix with each other due to poor isolation and you get all sort of color artefacts on the screen when you touch that ribbon or move it even very slightly. If you do not move it, the picture on a screen is unacceptable too. But nothing to complain about - that was my own decision to try the unit under recall. I thought it was a quality issue with some units and maybe i will get lucky, but it is more a design flaw which will be on every single unit produced unfortunately.
Also, I am really hoping you guys can take a fresh look at your documentation and redo it from the scratch from the user point of view. As from my view it is a total mess right now, because I am not a developer, I am a simple user and a lot of it makes zero sense to me. Try to understand what user needs when he purchases a fresh board, simulate the situation and make a simple clear start guide. I have spent so much unnecessary time looking for all this info and I am still nowhere near, because documentation is made for the developer and not for the user. A lot of documentation I have already went through covers printers setups, firmwares etc when I haven't even started and can not find basic things still
-
Also, since I am not able to use your screen I was really hoping to find some info on how to connect your board to a third party RepRap compatible controller via UART4 port or something similar. I have MKS controller which is really nice and works pretty good, except for the fact that so far I was not able to make it talk to your board (and MKS does not offer any main boards comparable to duet in functionality, not even close). It looks like it establishes the connection, but was not able to send any commands to the board yet. Is there any documentation about connecting DUET to a controller using URXD0/UTXD0 interface?
-
Another question is: is it possible to create custom UI for this display with different look for the interface, different buttons layout etc? I noticed relatively big CSS files on SD card of the board, but not sure where they are being used.
-
The 7" TFT panels vary in quality. Some of them work OK, but others don't. The 5" and 4.3" panels have some shielding around the Kapton ribbon cable, which is missing from the 7" version. Maybe adding that would make them work more consistently.
We are in the process of writing a new "Start Here" guide for using Duet electronics.
The Duets accept GCodes from multiple sources, including USB, the PanelDue connector (which is just a UART with 3.3V signal levels), http, telnet, and the SD card.
-
Is the protocol how the display and the Duet communicate documented somewhere? I'd love to tinker with it.
-
Is the protocol how the display and the Duet communicate documented somewhere? I'd love to tinker with it.
It's just plain G-code. PanelDue requests status updates via M408 in certain intervals and RRF respondswith JSON objects. I suggest you have a look at M408 if you want to know what they look like.
