@elmoret Thanks for your help on this. I recently purchased a high quality micro USB cable to make sure that that wasn't the issue. It turns out that it was. I think my old cable was damaged and that's why I wasn't able to connecct.
I really appreciate this team's patience.

@dc42 said in Status Duet + Mosaic Palette:

Perhaps they expect you to connect the Pallette to the printer using a USB cable, and then it sends the job to the printer over USB, rather like Octoprint.

This is exactly it.

You lose a lot of Duet functionality, but it does work.

@phaedrux I've tested it by moving the cable away, so that it no longer runs near motor cables, but sadly the info messages remain.

@phaedrux

I had to change P1 to P0. Looks like its working now.

If I left the P parameter out, the panel due creates two chamber heaters, 0 and 1. Not exactly sure why.

@dc42

Thank you for pointing out it.

@edwin The arduino is 5V and the PanelDue is 3.3V. The PanelDue allows 5V input (your resistive voltage divider isn't needed on the output pin). The PanelDue transmits at 3.3V and the Arduino expects input at the 5V level so the serial path PanelDue->Arduino seems like it wouldn't be reliable and needs a pull-up method. If you have a way to see the Arduino serial data I'd check that.

@comediantf2 I'm glad you got it working.

Have you taken it out of the casing to test?

What firmware file exactly did you flash?

@dc42 Thanks. Sigh. But you see. deminimis (the amount at which you pay duty) is $20 Canadian. This is about $18 USD. I will be charged $20 for the privilege of duty being figured out by the post. so I will pay $20 USD for the item, $21 USD for the tax, $20 CAD for duty and $3 CAD (roughly) for tax.

... so in CAD, that's 24 + 25 + 20 + 3 = $72

... and the Canadian retailer is selling some seemingly authentic (not the Israeli company) 7i panels (a slight upgrade) for about the same money ... and I get it in a day or two. and I can still think about repairing this panel some day, if that possibility appears.

@random_task_1
That was the problem. Somehow the crimps on the red wire were bad. I could sware that I had checked that several times already, but that fixed it.

Thanks

Hi, sorry about that, your email went to spam. You should see a response shortly.

Thanks for the heads up on the flash from Duet. That could be useful for anyone else whose computer refuses to see the PanelDue over USB.

@random_task_1 Not sure how to mark this solved but it was the cable order. I finally got them properly seated in the housing in the right order and, what do you know they worked......thanks for the help

@mfs12 @Phaedrux One thing to note, this Out of Filament message appears to have no way to acknowledge it, either from the DWC or from the PanelDue. So from that perspective, something around this message should probably be addressed, It doesn't re-occur on the PanelDue unless I pull out the filament again, but it always displays when connecting to the DWC.

One side note which probably isn't important, but the Duet 0.8.5 with Firmware 1.26.1 and PanelDue with firmware 1.25; this pop-up does not exist or is not triggered. In all honesty, its almost better that this message isn't presented as it's not a constant nag as it is with the newer firmware. The out of filament still works as expected and pauses properly, but without the contact nagging pop-up or DWC message.

@mfs12 thanks
Yes I did it . Now its Working..!

@droftarts

Thank you, hadn't even noticed that my paneldue version should match, updated and problem is resolved.

@dc42 Thanks!

I fixed it by ordering a Micro USB to DIP Adapter 5pin Female Connector B Type PCB Converter pinboard from Amazon and then soldering jumper wires to the associated components based on the v1.1 schematic. Got it working and updated to 1.25.0 firmware now.

For anyone that finds this post in the future looking for that USB part number, your schematic calls out Micro-USB-Receptacle - TJC-0069-B47589-0001

@mfs12 That's fixed it now. The title bar changes to reflect the currently printing file. Any hope for an update for the v1.1 boards for this particular fix also?