Please help us to test firmware 1.17RC3 and DWC 1.14
-
Since rolling back from DWC 1.14 to DWC 1.13 the connection problems and slow response issues that I reported on earlier seem to have gone away.
-
Found a bug with the DWC - when I enter in my webcam URL for the "Webcam Surveillance" preview, only every other "refresh" displays an image. For example, if I say update every 10 seconds, for 10 seconds a picture is displayed, then for ten seconds a broken image is displayed, then 10 seconds of a new correct image, then 10 seconds of a broken image…. etc. By broken image I mean an invalid JPEG, the browser won't display it.
-
Found a bug with the DWC - when I enter in my webcam URL for the "Webcam Surveillance" preview, only every other "refresh" displays an image. For example, if I say update every 10 seconds, for 10 seconds a picture is displayed, then for ten seconds a broken image is displayed, then 10 seconds of a new correct image, then 10 seconds of a broken image…. etc. By broken image I mean an invalid JPEG, the browser won't display it.
What browser are you using? What software do you use to output webcam to jpg?
-
All,
I think I found a small bug. The bed offset and max print bed size are not taken into account when doing the probing for minand max.
Example
I set my printer with[[language]] ; max travel and origin M208 X214 Y190 Z200 G31 P500 X8 Y-28 Z0.20 S60 ; set threshold and offsets (we were at 0.74 )Then, if I do a
G30 P1 X20 Y185 Z-99999I am finding my printer at 213, which is causing huge noise, as it can't go there.
-
The G30 command says you want to place the probe at Y=185 and this means putting the head at Y=213. The firmware assumes that you know what you are doing when you issue G30 commands, because they are completely under your control, unlike the gcode generated by a slicing program.
-
The G30 command says you want to place the probe at Y=185 and this means putting the head at Y=213. The firmware assumes that you know what you are doing when you issue G30 commands, because they are completely under your control, unlike the gcode generated by a slicing program.
Thanks, I thought the max and min were taken into account. This is exactly what I was doing anyway as a woraround.
Antoine
-
btw G29 probing is different because the points are generated automatically. The firmware checks that each point you want to probe is reachable by the probe, and skips any that are not.
-
not clear on how you display the grid visual.
Can I button in the web control be added to bring this up? -
Yes, go to Settings->Machine Properties and click "Load height map".
-
btw G29 probing is different because the points are generated automatically. The firmware checks that each point you want to probe is reachable by the probe, and skips any that are not.
Thanks
Does that mean that below command can go in config.gcode and bed.gcode would then only contain a HOME all and G29?
M557 X25:180 Y25:180 S20
Antoine -
i have updated to the latest firmware for both and I dont see that option.. to "Load height map"
-
nevermind.. it was download heightmap.. found it sorry
-
Does that mean that below command can go in config.gcode and bed.gcode would then only contain a HOME all and G29?
M557 X25:180 Y25:180 S20
AntoineYes, that's a good option for a non-delta printer.
-
I played again with the bed leveling today but I have problems loading or reloading the heightmap in the webif…
I started leveling from the PanelDue and when it was finished I loaded the 3D image on the webif and it seemed to be the result of the last operation. Then I did it again, but obviously the webif showed still the last result, the deviation and mean errors in the file didn't match the display...
So how can I force the webif to load the new heightmap file? I tried to reset the board, cleared my cache of the browser but I have no reliable sequence of steps to make it load the new generated heightmap file... -
The height map file is called heightmap.csv by default. It has a time stamp written into it. So you can open it in the system editor and check the time stamp. You can also use the P parameter of the G29 command to use a different file name if you wish.
-
Yeah that what I checked but I made a screen shooting the heights I display before and after. The file is different but not the rendering…
-
Could it be that the browser has cached the old height map file?
-
Happy New Year!
I'm having a problem in DWC 1.14-b4 with Webcam Integration. The working URL to acquire a snapshot from my cam is "http://192.168.1.128/webcapture.jpg?command=snap&channel=0". This URL works perfectly in Firefox, Chrome and IE. When I add this URL to the DWC interface, I am getting a dummy response appended to the end of the URL on the print status page, causing it to not display an image. As an example= "http://192.168.1.128/webcapture.jpg?command=snap&channel=0&dummy=0.3392961592542225". The dummy number changes every 5 seconds, and no image is displayed. It seems any "&…." placed after the end of the working URL causes the issue. Please take a look at the solution provided at this URL. https://github.com/Oitzu/pimatic-iframe/issues/8 -
The changing dummy= is to prevent your browser caching the image and just keep displaying an older version. It shouldn't stop the image from displaying. Do you see the image if you open that URL in its own tab?
-
The changing dummy= is to prevent your browser caching the image and just keep displaying an older version. It shouldn't stop the image from displaying. Do you see the image if you open that URL in its own tab?
I added this info in my post above….
It seems any "&…." placed after the end of the working URL causes the issue. Please take a look at the solution provided at this URL. https://github.com/Oitzu/pimatic-iframe/issues/8It appears they use a "?$variable" to update the URL and prevent the caching. So far, this does look like it works in a separate browser tab. But anytime I add the additional "&" to the URL, it fails with net::ERR_EMPTY_RESPONSE and no image is displayed in the DWC or in a separate browser tab.
