Please help us to test firmware 1.17RC3 and DWC 1.14
-
Thanks, I'll check it out.
-
My guess is that you have varying Z probe trigger height with XY position, caused by effector tilt or other factors.
OK, that is probably the case, but how to check what is causing it. The normal calibration does give consistent results and gives me a good first layer. So it does not feel as if the thing is out of whack, but I agree it is the most likely answer. Any suggestions as to how I can figure out where the issue(s) reside?
-
@dc42 - is Chrishamm's code available anywhere? He hasn't updated his repository with the 1.14-b4 stuff yet. I'd like to create a free-standing heightmap visualizer using his code to make it easy to compare and look at archived heightmaps.
Hi,
I'm also interested in having access to the source of DWC 1.14 , I'd like to test some changes as well.
for now I'm using https://github.com/igrr/mkspiffs (./mkspiffs -b 8192 -p 256 -s 3125248 ) to extract the files. but the css/js stuff has been yui-compressed so it's not relly straightfoward to work with… -
After still having strange grid calibration results, I switched arms around. On the theory that if the geometry of the arms is not correct I should see it in the calibrated shape. No change, what so ever. No change if I switch one arm, or all the arms. So I am guessing that the length of my arms is pretty identical.
So I put everything back the way it was and then rotated the effector. No change, same pattern.
It dips deeply between the left and back column and towards the right column. In the middle it is highest.
So that would point to the right column, yes? But in what way? I'll have to think about it.I think I will start a separate thread about this. No need to clutter up the 1.17 thread
-
the macro I provided was enclosed by M120 & M121. I read RRP does add them, no need to write them in the macro.
So it's all my fault
(it wasn't complaining about that with 1.16 but hey it's now ok)I found the problem. If M120 succeeds then execution of the current file stops. So it never gets to do the M121 and after running the macro a few times, the stack for that input channel reaches its maximum depth of 5. Will be fixed in next release.
only thing left is: a macro named Z-0.01 in the macro editor (dwc) appears as Z-0 in the machine control tab. (ultra minor bug)
Yes, I see that too. I'll alert chrishamm to it.
-
Lykle, what probing technology are you using? If the HE280 accelerometer, send me an email.
-
Anyone having an issue with files not showing up in uploaded list after upgrading to current edge firmware and DWC. I have uploaded a couple of jobs with printing them and i can not find them in the list. This is the first time I have seen this. Running the 1.17RC3 and the 1.14-b4 DWC. Thought I would ask if anyone else is seeing this.
-
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.
