Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    N539/N538 not working in 3.4

    Beta Firmware
    maestro sdcard rff3.4rc2 string handling
    2
    3
    159
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • 3discnc
      3discnc last edited by

      1. I was using N539 in RFF3.3 on the 12864 LCD; in 3.4 it shows 0.

      2. I am designing a replacement G29 grid scanner and run into the limited string space of RFF. I cannot find any means to truncate a float and so cannot pack enough floats (17+?) into this limited 120 byte string space. Any advice on this?

      3. Since there are no arrays I had to resort to 20 variables. Apparently these are not directly addressed or looked-up but searched for at each access, this makes them very slow. The further down, the slower. Perhaps something to look into. I've shortened the var's to two characters, that helped a bit

      4. I also have no clue how to use '#' to get a stringlen value. How is this supposed to work?

      5. My Maestro manages to erase the CD card from time to time. I've seen this happen on several crashes into the X endstop and a (probably) non ending loop.

      dc42 1 Reply Last reply Reply Quote 0
      • dc42
        dc42 administrators @3discnc last edited by dc42

        @3discnc said in N539/N538 not working in 3.4:

        1. I was using N539 in RFF3.3 on the 12864 LCD; in 3.4 it shows 0.

        Thanks for reporting this. I have now fixed it. The fix will be in 3.4.0 stable.

        1. I am designing a replacement G29 grid scanner and run into the limited string space of RFF. I cannot find any means to truncate a float and so cannot pack enough floats (17+?) into this limited 120 byte string space. Any advice on this?

        Perhaps you could use multiple strings with fewer floats in each?

        1. Since there are no arrays I had to resort to 20 variables. Apparently these are not directly addressed or looked-up but searched for at each access, this makes them very slow. The further down, the slower. Perhaps something to look into. I've shortened the var's to two characters, that helped a bit

        We will probably support array-valued variables in RRF 3.5.

        1. I also have no clue how to use '#' to get a stringlen value. How is this supposed to work?

        Trivial example:

        echo #("hello"^"world")
        10
        
        1. My Maestro manages to erase the CD card from time to time. I've seen this happen on several crashes into the X endstop and a (probably) non ending loop.

        Does this happen while your macros are writing to the SD card?

        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

        3discnc 1 Reply Last reply Reply Quote 0
        • 3discnc
          3discnc @dc42 last edited by

          @dc42 said in N539/N538 not working in 3.4:

          Sorry about the late response. I took the machine apart a month ago for some modifications and it took a month+ to receive the parts. I'm in the process of putting it together again and some reprogramming will be needed too.

          @3discnc said in N539/N538 not working in 3.4:

          1. I was using N539 in RFF3.3 on the 12864 LCD; in 3.4 it shows 0.

          Thanks for reporting this. I have now fixed it. The fix will be in 3.4.0 stable.

          1. I am designing a replacement G29 grid scanner and run into the limited string space of RFF. I cannot find any means to truncate a float and so cannot pack enough floats (17+?) into this limited 120 byte string space. Any advice on this?

          Perhaps you could use multiple strings with fewer floats in each?

          Already tried that but how do I put the two strings in the height map as a single sting (i.e. no CR/LF)?

          1. Since there are no arrays I had to resort to 20 variables. Apparently these are not directly addressed or looked-up but searched for at each access, this makes them very slow. The further down, the slower. Perhaps something to look into. I've shortened the var's to two characters, that helped a bit

          We will probably support array-valued variables in RRF 3.5.

          Those will be welcomed with open arms!

          1. I also have no clue how to use '#' to get a stringlen value. How is this supposed to work?

          Trivial example:

          echo #("hello"^"world")
          10
          

          That takes care of strlen() but, it would greatly help if I could truncate strings since I don't need fractional nanometre resolution (yet). ;o)

          1. My Maestro manages to erase the CD card from time to time. I've seen this happen on several crashes into the X end-stop and a (probably) non ending loop.

          Does this happen while your macros are writing to the SD card?

          Don't really know and also it does not happen every 5 minutes. I home (or some process) the machine and it crashes as soon as X-stop is hit. The LCD is emptied and the Maesto does not respond of even reboot. On my PC the card is not recognized (Windows asks Reformat Y/N?). I reformat and copy a backup onto the card and all is well. How well depends on the amount of work lost. I was intensively modifying the system macros over the network, with the accompanying reboots and whatnot.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA