@JRDM If you haven't turned it off and on since, send M122 for the error report, which should give a hint about what happened.

Ian

I tried to paint the glass bed white and apply the capton again. It seems to be working, so I will have all the options.
For a long time I would also like to change the probe, but every time I make a change it takes 5/6 days to fix it well.

@mwolter That's what I'm noticing as well. Seems the disconnect notifications in the log aren't affecting usability. Just annoying

@chrishamm said in DWC2 and nginx reverse proxy - cont.:

I don't think it's a nice solution to redirect static DWC2 resources. You may be better of building DWC2 with publicPath set to /dwc instead of / in your case. This will create a new bundle that loads DWC2-related files from /dwc instead of /.

I agree it is not a nice solution, or even a solution at all. While rebuilding DWC2 custom for me, will most likely work, and I have though about it as well. I am not a fan of having to build firmware myself each time an update comes around. Unless I can convince you the publicPath should be set to /dwc by default 😉 .

@Veti
Thank you Veti
I´ll give that a try.
//pe

@bearer Thanks for the response.

I was all set to say "yep, the same", but I figured the least I could do is set it to another IP address in config.d and go there.

So. Many. Hours. Wasted.

Looks like something else grabbed 192.168.1.77 while my printer was offline and wouldn't let it go, causing a conflict. I just set Duet to 192.168.1.222 and the web interface came up without issue.

Bleh. Much appreciated!

oh... my mistake. I'll have it posted.
thanks

Restriction #2 if because it's only letting you select pins that support analog input, which is needed for probe types 1 and 2.

Ok, I will see if I can find myself a tasty crow to eat .... 🙂

I've deleted all the content of 'sys' folder and I've re-uploaded all the files. It seems to be better.
Anyway this is the M122 command response
Screenshot_20200120-154908.jpg

yes it works with 2.0.6 thank you !

@Danal 😨 upps

Well, that's not good but I'm glad it's not just me.

As I have stated in the github issue, whilst the developer console was open in chrome there was no problem, stopping the network log in console brought the problem back again.

Still can't reproduce it though.

I got it!

It looks like when I first tried to update DWC through DWC itself, a new DWC-SD folder was created in the www folder and/because it didn't work. Then on the SD card I put all the 2.0.6 files in the new DWC-SD folder what was wrong. That was quite confusing. Emptied the whole www folder and put the 2.0.6 files into it. Now it works.

Thanks!

@chrishamm
Nice Work Thanks alot!
Iam happy now ! 🙂 I can use the RPI with ffmpeg & Telegramm 😄

@chrishamm Yes, confirmed fixed. Many Thanks 🙂

Just a closing remark to this thread ..... apparently the M999 error message was a known bug in the web interface and has been fixed in version 2.06

yet another little question: i have a duet 3 where fan0 is not predefined. how do i configure the fan to be active at power on?

I can confirm that DWC 2.05 has fixed this issue 🙂
Great work & thanks.