4. Repetier gets constant messages if Duet Web Control is connected

Repetier gets constant messages if Duet Web Control is connected

  • James

    Hi,

    If I have my printer connected in the Duet Web Control, my Repetier-Host log updates constantly, showing lines like this:

    =====================================
    10:20:09.914 : Request: status?type=1 fragment 2147483648
    10:20:09.914 : Resp 2147483648: 000100c8 0000019c {"st…s
    10:20:09.930 : Request: reply fragment 2147483648
    10:20:09.930 : Serving client 1 of 1
    10:20:09.930 : Resp 2147483648: 000000c8 00000079 FIRM...s
    10:20:10.194 : Request: status?type=2 fragment 2147483648
    10:20:10.195 : Resp 2147483648: 000100c8 00000327 {"st...s
    10:20:10.484 : Request: status?type=1 fragment 2147483648
    10:20:10.484 : Resp 2147483648: 000100c8 0000019c {"st...s
    10:20:10.763 : Request: status?type=1 fragment 2147483648
    10:20:10.763 : Resp 2147483648: 000100c8 0000019c {"st...s
    10:20:11.038 : Request: status?type=1 fragment 2147483648
    10:20:11.038 : Resp 2147483648: 000100c8 0000019c {"st...s

    This happened out of the box, so I updated to the latest versions of everything:

    Firmware: 1.17e
    WiFi Server Version: 1.03 (ch fork)
    Web Interface Version: 1.12-RC1

    But this did not change the behavior. Anyone know why this happens and if it can be fixed?

    Thanks,
    James

    0
  • Jackal

    Try updating to Duet Web Control 1.14a
    https://github.com/dc42/RepRapFirmware/blob/dev/Release/Duet-WiFi/Stable/DuetWebControl-1.14a.bin

    0
  • James

    Thanks – I didn't realize I didn't have the latest. But, I updated and it still does the same thing. Below is a new sample, in case these codes actually mean something to someone 🙂

    James

    =======================================
    11:08:37.146 : Resp 2147483648: 000100c8 00000039 {"er...s
    11:08:37.167 : Request: status?type=2 fragment 2147483648
    11:08:37.167 : Resp 2147483648: 000100c8 00000328 {"st...s
    11:08:37.178 : Request: config fragment 2147483648
    11:08:37.179 : Resp 2147483648: 000100c8 00000267 {"ax...s
    11:08:37.191 : Request: filelist?dir=0:/sys fragment 2147483648
    11:08:37.191 : Resp 2147483648: 000100c8 00000296 {"di...s
    11:08:37.200 : Request: reply fragment 2147483648
    11:08:37.200 : Resp 2147483648: 000000c8 00000000
    11:08:37.558 : Request: status?type=1 fragment 2147483648
    11:08:37.558 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:37.863 : Request: status?type=1 fragment 2147483648
    11:08:37.863 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:38.178 : Request: status?type=1 fragment 2147483648
    11:08:38.178 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:38.489 : Request: status?type=1 fragment 2147483648
    11:08:38.489 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:38.791 : Request: status?type=1 fragment 2147483648
    11:08:38.792 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:39.097 : Request: status?type=1 fragment 2147483648
    11:08:39.098 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:39.374 : Request: status?type=1 fragment 2147483648
    11:08:39.374 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:39.647 : Request: status?type=1 fragment 2147483648
    11:08:39.647 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:39.923 : Request: status?type=1 fragment 2147483648
    11:08:39.923 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:40.198 : Request: status?type=2 fragment 2147483648
    11:08:40.198 : Resp 2147483648: 000100c8 00000328 {"st...s
    11:08:40.486 : Request: status?type=1 fragment 2147483648
    11:08:40.486 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:40.757 : Request: status?type=1 fragment 2147483648
    11:08:40.758 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:41.045 : Request: status?type=1 fragment 2147483648
    11:08:41.045 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:41.319 : Request: status?type=1 fragment 2147483648
    11:08:41.319 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:41.592 : Request: status?type=1 fragment 2147483648
    11:08:41.592 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:41.865 : Request: status?type=1 fragment 2147483648
    11:08:41.865 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:42.137 : Request: status?type=1 fragment 2147483648
    11:08:42.137 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:42.408 : Request: status?type=1 fragment 2147483648
    11:08:42.409 : Resp 2147483648: 000100c8 0000019c {"st...s
    11:08:42.684 : Request: disconnect fragment 2147483648
    11:08:42.684 : Resp 2147483648: 000100c8 00000009 {"err":0}

    0
  • dc42
    administrators

    Repetier Host unfortunately turns on debug output by default. I don't know why, it seems a daft thing to do to me. You can turn it off by going to the console and pressing the Info and Errors buttons to turn them off.

    0
  • James

    Well, that's weird. I can turn everything off, and it still happens. No matter what combination I select of Commands, Infos, Warnings, Errors, or ACK, it still shows up. I'm using v1.6.2, which it says is the most current.

    What are these messages anyway?

    Thanks,
    James

    0
  • dc42
    administrators

    Those are summaries of the comments between the WiFi module and the main processor. Sending M111 S0 should stop them if Repetier doesn't intercept that command.

    0
  • James

    Sending M110 S0 from the Duet Web Control stops the messages in Repetier, until you send another command. E.g., after I saw that it stopped, I tried M114 and M115 from Repetier just to see if the log still worked, and then the messages start again.

    Anyway, not worth taking up more of your time – it doesn't hurt anything except the ability to see the logs, and if I want to I can always disconnect the Duet Web Control temporarily while in Repetier.

    Thanks,
    James

    0
Log in to reply
 
Unless otherwise noted, all forum content is licensed under CC-BY-SA