Heightmap load regression



  • I'm having this problem, https://forum.duet3d.com/topic/998/problems-loading-height-map?_=1613850296859

    I removed all of the 0 from the 0.xyz offsets and the file loaded. So it looks like there's a line length problem again?

    Here's my file before mangling

    RepRapFirmware height map file v2 generated at 2021-02-21 11:22, min error -0.315, max error 0.057, mean -0.130, deviation 0.073
    xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
    0.00,260.00,0.00,300.00,-1.00,17.33,20.00,15,16
    0.034,0.012,-0.009,-0.054,-0.089,-0.121,-0.165,-0.179,-0.158,-0.145,-0.132,-0.116,-0.105,-0.055,0.057
    -0.002,-0.039,-0.039,-0.066,-0.095,-0.125,-0.159,-0.198,-0.177,-0.141,-0.099,-0.138,-0.141,-0.120,-0.067
    -0.315,-0.068,-0.063,-0.069,-0.078,-0.084,-0.116,-0.129,-0.130,-0.110,-0.125,-0.113,-0.108,-0.124,-0.122
    -0.070,-0.101,-0.118,-0.103,-0.080,-0.100,-0.084,-0.112,-0.102,-0.118,-0.110,-0.092,-0.116,-0.083,-0.105
    -0.061,-0.103,-0.116,-0.110,-0.125,-0.134,-0.106,-0.105,-0.110,-0.121,-0.119,-0.067,-0.063,-0.088,-0.108
    -0.038,-0.093,-0.082,-0.113,-0.133,-0.149,-0.139,-0.154,-0.168,-0.157,-0.129,-0.066,-0.020,-0.064,-0.138
    -0.019,-0.059,-0.058,-0.082,-0.136,-0.152,-0.170,-0.188,-0.162,-0.180,-0.192,-0.149,-0.101,-0.108,-0.122
    -0.018,-0.045,-0.064,-0.092,-0.131,-0.146,-0.172,-0.202,-0.213,-0.211,-0.219,-0.202,-0.185,-0.164,-0.128
    0.006,-0.001,-0.060,-0.085,-0.095,-0.142,-0.177,-0.223,-0.233,-0.242,-0.221,-0.227,-0.223,-0.202,-0.168
    -0.013,-0.033,-0.058,-0.082,-0.102,-0.147,-0.145,-0.205,-0.212,-0.234,-0.228,-0.240,-0.230,-0.226,-0.205
    -0.027,-0.025,-0.052,-0.093,-0.094,-0.095,-0.140,-0.181,-0.213,-0.243,-0.257,-0.259,-0.269,-0.252,-0.241
    -0.017,-0.027,-0.060,-0.068,-0.049,-0.020,-0.079,-0.190,-0.204,-0.217,-0.250,-0.262,-0.253,-0.255,-0.262
    -0.280,-0.019,-0.050,-0.076,-0.094,-0.073,-0.125,-0.172,-0.148,-0.137,-0.126,-0.165,-0.220,-0.262,-0.237
    0.003,-0.020,-0.052,-0.082,-0.115,-0.129,-0.160,-0.155,-0.124,-0.041,-0.023,-0.143,-0.230,-0.262,-0.239
    -0.018,-0.052,-0.053,-0.107,-0.112,-0.108,-0.158,-0.167,-0.155,-0.116,-0.094,-0.178,-0.262,-0.271,-0.257
    0.006,-0.053,-0.087,-0.114,-0.116,-0.150,-0.166,-0.190,-0.217,-0.168,-0.209,-0.273,-0.260,-0.252,-0.205
    

  • Moderator

    fw version?



  • @Phaedrux

    
    Firmware Name:	RepRapFirmware for Duet 2 WiFi/Ethernet
    Firmware Electronics:	Duet Ethernet 1.02 or later + DueX5
    Firmware Version:	3.2 (2021-01-05)
    Web Interface Version:	1.22.6
    

  • Moderator

    @gnydick said in Heightmap load regression:

    Web Interface Version: 1.22.6

    Is it really 1.22.6? Not sure how well that will work with 3.2.

    What is the exact error you're getting when loading the heightmap and how are you trying to load it?

    The thread you linked to from 2017 says

    When I try to load a height map using G29 S1 , I get the following error
    Error: Failed to load height map from file heightmap.csv: number expected at line 3 column 201

    Is that what you're getting?



  • @Phaedrux

    Sorry to say, I'm not going to use the current DWC, it's garbage. I had a whole long argument with the creator back when he was soliciting feedback while it was under development and I described exactly why it's a step backwards; all flash, no usability.

    that's exactly what i'm getting.

    failed to load heightmap.png



  • @gnydick said in Heightmap load regression:

    Sorry to say, I'm not going to use the current DWC, it's garbage.

    Garbage? I guess I must have a real fondness for garbage. I find DWC extremely useful - there is little I would change.

    Frederick



  • @gnydick said in Heightmap load regression:

    that's exactly what i'm getting.

    failed to load heightmap.png

    Did you create a less dense grid to see if it was a buffer length issue?

    Frederick


  • administrators

    Maximum line length is 330, so I don't think it can be that.


  • administrators

    @gnydick, we think there is a rounding error happening somewhere. That height map has an X range of 260 and X spacing of 17.33, so there should be (260/17.33+1) probe points per row, which is 16.002 so 16. But there are only 15 point in each row.

    How did you generate that height map?



  • @dc42 the usual way. clicked it from the drop down



  • @fcwilt happy to have a side conversation about it. But here's a link to the old thread
    https://forum.duet3d.com/topic/8293/duet-web-control-2-0-0-rc3-is-ready/115?_=1614147801425


  • administrators

    @gnydick, please provide the M557 command that you used when you used the drop down to probe the bed and create the height map.



  • @dc42
    M557 X0:260 Y0:300 P16:16 ; mesh def



  • @dc42 still happening

    M557 Grid: X0.0:260.0, Y0.0:290.0, radius -1.0, X spacing 17.3, Y spacing 19.3, 225 points

    RepRapFirmware height map file v2 generated at 2021-03-06 12:26, min error -0.234, max error 0.100, mean -0.098, deviation 0.048
    xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
    0.00,260.00,0.00,290.00,-1.00,17.33,19.33,15,15
     -0.006, -0.010, -0.048, -0.073, -0.082, -0.113, -0.142, -0.135, -0.129, -0.070, -0.064, -0.062, -0.054,  0.018,  0.100
     -0.066, -0.052, -0.058, -0.069, -0.071, -0.096, -0.156, -0.159, -0.138, -0.081, -0.061, -0.066, -0.121, -0.086, -0.055
     -0.178, -0.102, -0.086, -0.085, -0.073, -0.076, -0.082, -0.115, -0.094, -0.091, -0.054, -0.052, -0.050, -0.054, -0.043
     -0.140, -0.119, -0.162, -0.136, -0.120, -0.066, -0.079, -0.069, -0.075, -0.060, -0.047, -0.051, -0.057, -0.066, -0.047
     -0.140, -0.148, -0.095, -0.135, -0.129, -0.111, -0.107, -0.093, -0.065, -0.084, -0.071, -0.039, -0.024, -0.039, -0.046
     -0.068, -0.110, -0.136, -0.138, -0.156, -0.123, -0.128, -0.141, -0.109, -0.100, -0.078, -0.033,  0.026, -0.038, -0.035
     -0.079, -0.079, -0.105, -0.121, -0.134, -0.133, -0.155, -0.168, -0.134, -0.151, -0.127, -0.084,  0.024,  0.014, -0.049
     -0.056, -0.065, -0.085, -0.104, -0.131, -0.153, -0.159, -0.178, -0.172, -0.154, -0.155, -0.141, -0.084, -0.081, -0.052
     -0.021, -0.061, -0.093, -0.112, -0.122, -0.149, -0.158, -0.169, -0.189, -0.185, -0.198, -0.178, -0.123, -0.084, -0.047
     -0.058, -0.060, -0.096, -0.106, -0.108, -0.140, -0.164, -0.176, -0.166, -0.180, -0.174, -0.179, -0.144, -0.105, -0.069
     -0.034, -0.074, -0.055, -0.071, -0.102, -0.135, -0.136, -0.158, -0.114, -0.147, -0.163, -0.153, -0.163, -0.148, -0.126
     -0.017, -0.051, -0.070, -0.096, -0.104, -0.123, -0.140, -0.139, -0.151, -0.145, -0.147, -0.121, -0.142, -0.113, -0.110
     -0.234, -0.046, -0.050, -0.086, -0.072, -0.117, -0.127, -0.122, -0.118, -0.112, -0.134, -0.142, -0.141, -0.144, -0.129
     -0.023, -0.019, -0.019, -0.052, -0.061, -0.084, -0.083, -0.108, -0.086, -0.094, -0.111, -0.078, -0.100, -0.069, -0.072
     -0.031, -0.044, -0.015, -0.071, -0.051, -0.073, -0.087, -0.108, -0.074, -0.104, -0.117, -0.111, -0.121, -0.113, -0.083
    

  • Moderator

    Thanks for the reminder. Will take another look.



  • I'll shamelessly plug in here. Is it possible the problem I am seeing is somehow related to this?
    https://forum.duet3d.com/topic/21963/rrf-3-2-2-can-t-figure-out-the-offset-between-z0-and-mesh


Log in to reply