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

    Eventlog not recording

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    4
    11
    411
    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.
    • jay_s_ukundefined
      jay_s_uk
      last edited by

      I don't think the event log is supported like that when in SBC mode.
      Most things are logged to syslog in /var/log/

      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
      • TypQxQundefined
        TypQxQ
        last edited by

        I did suspect something like that and did doublecheck the documentation and couldn't find anything about that. Would be great to somehow have access to it trough the web interface.

        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator
          last edited by

          https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional

          @TypQxQ said in Eventlog not recording:

          Would be great to somehow have access to it trough the web interface.

          Agreed.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • TypQxQundefined
            TypQxQ
            last edited by

            Maybe add to the documentation of M929 that although it seems to work, it doesn't.

            Phaedruxundefined 1 Reply Last reply Reply Quote 0
            • Phaedruxundefined
              Phaedrux Moderator @TypQxQ
              last edited by

              @TypQxQ The intention for 3.2 is to restore M929 functionality.

              Z-Bot CoreXY Build | Thingiverse Profile

              TypQxQundefined 1 Reply Last reply Reply Quote 1
              • TypQxQundefined
                TypQxQ @Phaedrux
                last edited by

                @Phaedrux I see that should have been fixed in DSF 3.2.0-b1:
                "Event logging via M929 was not working"

                Running 3.2RC2 and it still does not log anything usefull:

                2020-12-22 09:18:49 Event logging stopped
                2020-12-22 09:19:36 Event logging started
                2020-12-22 09:24:20 Event logging stopped
                2020-12-23 15:41:13 Event logging started
                2020-12-27 16:55:38 Event logging stopped
                2020-12-27 16:56:44 Event logging started
                2020-12-27 16:57:12 Event logging stopped
                2020-12-27 17:00:27 Event logging started
                
                1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator
                  last edited by

                  Can you try logging to a file name?

                  https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M929_Start_stop_event_logging_to_SD_card

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • TypQxQundefined
                    TypQxQ
                    last edited by TypQxQ

                    @Phaedrux I have it setup as "M929 P"eventlog.txt" S3" in my config file.
                    Apparently the S3 does not work and S1 and S2 are switched to what the documentation states.

                    2020-12-28 00:26:56	M929
                    Event logging is disabled
                    2020-12-28 00:26:52	M929 P"eventlog.txt" S0
                    2020-12-28 00:26:44	M929
                    Event logging is disabled
                    2020-12-28 00:26:40	M929 P"eventlog.txt" S3
                    2020-12-28 00:26:32	M929
                    Event logging is enabled at log level warn
                    2020-12-28 00:26:28	M929 P"eventlog.txt" S2
                    2020-12-28 00:26:03	M929
                    Event logging is enabled at log level info
                    2020-12-28 00:26:00	M929 P"eventlog.txt" S1
                    
                    1 Reply Last reply Reply Quote 0
                    • chrishammundefined
                      chrishamm administrators
                      last edited by

                      M929 S1 works without problems for me. Note that I entered M118 and accidentally hit return, so I got an error which went into the log. Then I sent M118 S"Hello" L1 and again it was logged:

                      2020-12-30 19:21:47 Event logging started
                      2020-12-30 19:22:09 Error: M118: missing parameter 'S'
                      2020-12-30 19:22:14 Hello
                      

                      But thanks for pointing out that M929 S3 isn't working, I'll fix that in the next build.

                      Duet software engineer

                      TypQxQundefined 1 Reply Last reply Reply Quote 0
                      • TypQxQundefined
                        TypQxQ @chrishamm
                        last edited by

                        @chrishamm Thank you!
                        Please also note that the log level of S1 and S2 are reversed to what is stated in Gcode documentation.

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