3D GCode Viewer integrated with DWC

[Sindarius]

@PCR It's possible/probable they are developing their own 3d viewer for the DWC. The drive for my original development was that I needed the ability to see the model but also be able to see a color mixing approximation based on color mixing gcode on my M3D Crane Quad mixing head. I also use it when I have a print that just has several tools for my set of extruders, so it should work great for something like a tool changer. Not sure what they have worked on but I am sure it'll be good.

by simply changing the colors loaded into the extruder I get a nice approximation of what the gradients / colors will look like.

[Sindarius]

Did some poking around at the 3.2 development baseline and it looks like they are using this package for their upcoming viewer.

https://gcode-preview.web.app/

[PCR]

@Sindarius The SBC Version do not work ;( it "hangs" at downloading Gcode

[Sindarius]

@PCR I don’t have a duet 3 nor a pi setup to test. Is there any message in the console? I wonder if it is the issue where you had to upload the web client twice for it to take.

[PCR]

@Sindarius i think i found the problem.
The SBC Version want to download the file via the
GET http://192.168.178.36/rr_download?name=0:/gcodes/lpc_adapter_case_bottom_0.2mm_PLA_MK3S_2h6m.gcode
command.

For the Duet SBC it should be

GET http://192.168.178.36/machine/file/0:/gcodes/lpc_adapter_case_bottom_0.2mm_PLA_MK3S_2h6m.gcode

In the browser it will download the file via the last command

More Info here : https://github.com/Duet3D/DuetSoftwareFramework#get-machinefilefilename

[smoki3]

@Sindarius

Very cool. I like the multi color implementation. Looks better than the visualizer on 3.2

So would be cool if this will also be available as an Plug In for 3.2. On my 3.2 build from yesterday, christian got the plugin system to work.

[Sindarius]

@PCR Thanks for looking into this. I will start looking at what it takes to make sure that the URL is correct for the SBC version. Hopefully I will have some time today/tomorrow to make the changes to it.

[PCR]

Thank you! honestly like your ones more than the one from 3.2

[PCR]

made this change to the fork of you!

https://github.com/P-C-R/DuetWebControl/commit/32c2e5279333cae02d4a80a39c5828be06b4ef5d

it works now on the SBC. But i cannot say it its "enough"

0 P-C-R committed 3 Sept 2020, 15:04 to P-C-R/DuetWebControl

Update viewer.js

[Sindarius]

@PCR That'll work for the SBC but then it will break the SD. I am looking at a way to detect if the DWC is SBC or SD and use that as a parameter in the viewer so both will work.

[Sindarius]

@PCR

If you could give this a shot and let me know. I added some code that will hopefully help determine if the DWC is SBC or SD and set an appropriate parameter for the viewer.

https://github.com/Sindarius/DuetWebControl/releases/tag/3.1.1-SBCFix

[PCR]

@Sindarius

not working;(

[PCR]

 def __init__(self,base_url):
        self._base_url = base_url
        try:
            URL=(f'{self._base_url}'+'/rr_status?type=1')
            r = self.requests.get(URL,timeout=(2,60))
            j = self.json.loads(r.text)
            _=j['coords']
            self.pt = 2
            return
        except:
            try:
                URL=(f'{self._base_url}'+'/machine/status')
                r = self.requests.get(URL,timeout=(2,60))
                j = self.json.loads(r.text)
                _=j['result']
                self.pt = 3
                return
            except:
                print(self._base_url," does not appear to be a RRF2 or RRF3 printer", file=self.sys.stderr)
                return 
 

This was the logic @Danal code. RIP

[Sindarius]

@PCR I was trying to avoid having to query both paths but that may be unavoidable for now.

[Sindarius]

@PCR https://github.com/Sindarius/DuetWebControl/releases/tag/3.1.1-SBCFixV2

Give this one a go if you get a chance.

[danym21]

@Sindarius
like I said in github it is working with the FixV2 on my SBC for me.
many thx for the great work.

[Sindarius]

@danym21 I saw your message, thanks for the feedback and I am glad that it going for you guys

[PCR]

Works perfectly now as a Plugin in 3.2 ;)))

[Sindarius]

@PCR Once 3.2 is finalized and out in the wild that's the plan. I'll plan to test it in the DWC page itself like an unreleased original version I did. However, there was issues with VueJS trying to attach itself to the viewer's resources which would cause the viewer to be unstable and crash the page and would also limit the max size of model to be viewed.

[chrishamm]

@Sindarius I had some similiar problems with the charts + heightmap but got around it by storing my own stuff in the JS file based on the machine name . Be aware that we'll add multi-machine support at some point and the backend has already been prepared for that.

The new event API from v3.2 should be easier to handle, too.