I found the reason for the problem. Perhaps you explain its nature. The steps motors of the axes A and B had 6 wires 4 of which were sweaty to the controller. After replacing the engines with 4 wired problems did not appear.
When it's showing the white screen do you hear any beeps when you touch the screen as if you were pressing buttons? This would assume that the firmware hasn't already been cleared.
@jackantubis nice, thanks for sharing, I am rebuilding a Tevo Little monster for a total of 1000mm Z size, so I love the wireless solution for the paneldue
@mitch Lots of places to shift electronics (ebay, craigslist, offerup marketplace), I'm in agreement about saving it from a landfill. But seems really disrespectful to come here to do it. Just my 2c.
@R006 that command refers to paths that have spaces in them (between Program and Files) so in each case the whole path/filename needs to have quotation marks around it. I'm not a user of CMake so I don't know how to make that happen, unless that whole line appears in CMakeLists.txt and you can just edit it. Developers who build under Linux typically avoid spaces in file and folder names to avoid this sort of problem.
I built PanelDueFirmware successfully under Eclipse/Windows a few days ago. I have the same space in the file paths as you do and Eclipse puts the quotation marks in automatically.
@dc42 Thank you very much for taking me into consideration and responding. We decided to use a different method. Thank you again for your answers. 😊 😊 👍 👍
@sinned6915
Hello, I have the same issue on PanelDue7.0/V3 controller.
I can't recompile the firmware with the modified PanelDue.cpp file because I don't have the skills. Would it be possible to share the one you use? Thanks in advance
@jay_s_uk You did a great job identifying the right place to customize the software (at least for me, it would have been a lot of work).
Anyways, considering that in this case I would need to host the whole programming environment for this minor change, which would not be persistent at the next release, I decided to rather try to create a macro and use the BtnCmd plugin to make it available in DWC.
Happy to report that I was able to flash all six PanelDues (four V2s & two V3s), and I'll accept user error. Let me explain what I did as I know others will likely fall into the same trap I did. I installed BOSSA like normal which includes the baked-in CDC driver. The port doesn't show up in Device Manager just yet. Plug in the PanelDue and the BOSSA Driver still doesn't show up yet. The instructions say to press the erase button. Well, I hadn't held the button long enough apparently. Windows will eventually detect and then you will see the BOSSA driver appear in the device manager. I may have figured this out sooner had I left the PanelDue plugged into the screen, but since I'm using a 7" screen, I was concerned about power - there was nothing wrong with having it plugged in, and it went black as it states in the instructions. 🤦 Now to plug back into the printers and see the fruits of my labor suffering.
