Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    RRF 3.1.1: M408 S0 R1's response

    Scheduled Pinned Locked Moved
    General Discussion
    2
    5
    217
    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.
    • illyundefined
      illy
      last edited by illy

      Hi everyone,

      This is the response I get after sending a M408 S0 R1 command in 3.1.1:

      {"status":"I","heaters":[23.9,24.1,24.2],"active":[0.0,0.0,0.0],"standby":[0.0,0.0,0.0],"hstat":[0,0,0],"pos":[294.000,27.000,5.194],"machine":[294.000,27.000,5.494],"sfactor":100.0,"efactor":[100.0,100.0],"babystep":0.300,"tool":-1,"probe":"0","fanPercent":[0.0,100,100,0,0,-1,-1,-1,-1,-1,-1,-1,-1],"fanRPM":[-1,-1,-1,-1],"homed":[1,1,1],"msgBox.mode":-1}<LF><LF>ok<LF>

      In RRF 3.0 there is still an information about our Wifi module ("resp":....), but now it's completely gone. This has an impact on my display software. I can not see the IP address anymore on the display.

      I've also tried with a M408 S0 command without R1, but I got the identic response as before (with R1).

      Maybe someone can help me. Thankyou!

      1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk
        last edited by

        M408 is slowly being replaced with M409 as the object model becomes the drivers.

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        1 Reply Last reply Reply Quote 0
        • illyundefined
          illy
          last edited by

          @jay_s_uk Thank you for your response, but I could not see any information about the Wifi module after sending a M409 command.

          {"key":"","flags":"","result":{"boards":[{}],"directories":{},"fans":[{},{},{},{}],"heat":{},"inputs":[{},{},{},{},{},{},{},null,null,{},null,{}],"job":{},"limits":{},"move":{},"network":{},"scanner":{},"sensors":{},"seqs":{},"spindles":[{},{},{},{}],"state":{},"tools":[{},{}],"volumes":[{},{}]}}<LF>ok<LF>

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @illy
            last edited by jay_s_uk

            @illy M409 by itself only shows the top level of the object model. It's possible to drill down further into the JSON output. Please see here for more info. https://duet3d.dozuki.com/Wiki/Object_Model_of_RepRapFirmware and here https://duet3d.dozuki.com/Wiki/Gcode#Section_M409_Query_object_model

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            illyundefined 1 Reply Last reply Reply Quote 1
            • illyundefined
              illy @jay_s_uk
              last edited by

              @jay_s_uk thank you for the information!

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