Duet3 upgrade - java error
-
@dc42 Ahhh, I had a shortcut in my browser set to reprap.htm ..... went back to just the ip and got the new web interface. Unfortunately this brought up a second issue (doesn't it always) in that I can't seem to go back to the old user interface which I prefer.
I put the reprap.htm file back on the memory card, it sees it and displays it but without any formatting like boxes and things, it just prints it as individual lines. What else did I manage to screw up ? -
@jens55 said in Duet3 upgrade - java error:
@dc42 Ahhh, I had a shortcut in my browser set to reprap.htm ..... went back to just the ip and got the new web interface. Unfortunately this brought up a second issue (doesn't it always) in that I can't seem to go back to the old user interface which I prefer.
I put the reprap.htm file back on the memory card, it sees it and displays it but without any formatting like boxes and things, it just prints it as individual lines. What else did I manage to screw up ?It sounds like you deleted some of the other DWC 1.22.6 files from /www. Just reinstall them. You can have both DWC2 and DWC 1.22.6 files in the /www folder, they don't interfere with each other.
Is there anything in particular you do that provokes the Javascript error when you use DWC 1.22.6 with RRF3? I've just tried it and so far it works for me.
-
The javascript error went away after I upgraded to the new web panel and after I didn't go directly to the reprap.htm page.
I thought I had all the old files re-installed but since you mention it, I did not re-install the old files in the folders that were upgraded, just in the /www directory itself. It now makes sense why I am getting what I am getting
Thank you !
-
@jens55 said in Duet3 upgrade - java error:
The javascript error went away after I upgraded to the new web panel and after I didn't go directly to the reprap.htm page.
What I meant was, when you were using the old Duet Web Control (version 1.22.6?) with RRF3, did the javascript error occur immediately, or only when you did something in particular? DWC 1.22.6 is working for me with RRF3.
-
The javascript error popped up immediately upon completion of loading the page.
Furthermore, now that I have all the files re-installed, when I go to the old web interface I get the javascript error again (but at least the page formatting is correct now)
Version: 1.22.6
Message: Type Error: lastStatusResponse.temps.current[heater] is undefined
URL: http://192.168.1.114/js/dwc.js
Line: 4468:8
Error object: {} -
@jens55 said in Duet3 upgrade - java error:
The javascript error popped up immediately upon completion of loading the page.
Furthermore, now that I have all the files re-installed, when I go to the old web interface I get the javascript error again (but at least the page formatting is correct now)
Version: 1.22.6
Message: Type Error: lastStatusResponse.temps.current[heater] is undefined
URL: http://192.168.1.114/js/dwc.js
Line: 4468:8
Error object: {}Thanks. This may be caused by a bug in RRF 3.0 that I have fixed since that release. Also, have you numbered the heaters consecutively? I'm not sure whether DWC 1.22.6 can handle gaps in the numbering.
-
No, the heaters are not numbered sequentially ... my second extruder, heater and sensor is on a duex5 board.
I should add that the setup worked fine under Duet2
-
@jens55 said in Duet3 upgrade - java error:
No, the heaters are not numbered sequentially ... my second extruder, heater and sensor is on a duex5 board.
That may be the problem then. In RRF2, all heaters existed even if you didn't use them. In RRF3, only heaters you create using M950 exist. If that's the problem, then a solution would be to renumber the heaters in your M950 and M563 commands so that there are no gaps in the numbering. So you would call the first heater on the DueX board heater 2 instead of heater 3.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 RRF3 is not yet configured at all so I don't expect anything to work BUT .... it makes no sense for the web control panel to break if there is an issue with the printer configuration. In other words, the new web panel handles things as it should but the old one has a programming error of some kind.
If the old web panel is still deemed 'supported' then that fix should be back-ported.
Of course it doesn't help that most users probably use the web panel to set up the printer configuration
Maybe this conversation will land on the right desk and a fix will happen ..... -
The old web interface isn't actively supported with RRF3, but I was interested to find out why it didn't work for you.
-
It is unfortunate that the old web interface is no longer supported.
Hopefully it will work once Duet3 is properly configured. -
We don't have enough resources to justify supporting 2 different web interfaces. But everything is open source, so anyone who wants to is free to do their own web interface, or adapt old versions to new RRF releases.
-
Of course .... and I understand .... but it is still unfortunate ....
-
I should add that I appreciate the support that you give even though your resources are very limited !
Also, thank you to all the other people that help in supporting the whole Duet system! I am sure that it wouldn't be half as successful without the effort of a lot of people!
Thank you !
