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

Eventlog not recording

Scheduled Pinned Locked Moved Solved
Beta Firmware
4
11
389
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.
  • undefined
    TypQxQ
    last edited by 16 Dec 2020, 22:07

    I haven't had my log file log anything for ages. Unsure if it ever logged anything other than "Event logging started".
    Using RRF 3.2-beta3.2 (I've made some mechanical changes I want to see work before upgrading to b4.1) on a 6HC+3HC+SBC.

    M929 P"eventlog.txt" S3
    M118 S"Hello Logfile- deb" L3
    M118 S"Hello Logfile- info" L2
    M118 S"Hello Logfile- warn" L1

    Nothing logged.

    I tried, disabling log, delete and enable logging but still nothing gets logged.

    1 Reply Last reply Reply Quote 0
    • undefined
      jay_s_uk
      last edited by 16 Dec 2020, 22:35

      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
      • undefined
        TypQxQ
        last edited by 16 Dec 2020, 22:43

        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
        • undefined
          Phaedrux Moderator
          last edited by 17 Dec 2020, 03:04

          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
          • undefined
            TypQxQ
            last edited by 17 Dec 2020, 13:29

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

            undefined 1 Reply Last reply 17 Dec 2020, 18:25 Reply Quote 0
            • undefined
              Phaedrux Moderator @TypQxQ
              last edited by 17 Dec 2020, 18:25

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

              Z-Bot CoreXY Build | Thingiverse Profile

              undefined 1 Reply Last reply 27 Dec 2020, 23:17 Reply Quote 1
              • undefined
                TypQxQ @Phaedrux
                last edited by 27 Dec 2020, 23:17

                @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
                • undefined
                  Phaedrux Moderator
                  last edited by 27 Dec 2020, 23:19

                  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
                  • undefined
                    TypQxQ
                    last edited by TypQxQ 27 Dec 2020, 23:30

                    @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
                    • undefined
                      chrishamm administrators
                      last edited by 30 Dec 2020, 19:25

                      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

                      undefined 1 Reply Last reply 30 Dec 2020, 21:42 Reply Quote 0
                      • undefined
                        TypQxQ @chrishamm
                        last edited by 30 Dec 2020, 21:42

                        @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