The only time I've really seen corruption happen is when you loose power in the middle of a high I/O event. Unless your using a PI to build a NAS that you plan on hammering on, you will probably never see a corruption event.

@deckingman said in Can-o-Worms: Pi Shutdown vs Power Off:

Please excuse my ignorance because my RPi although fitted, remains unconnected so I have zero experience of using the thing. I assume that the reason why you have gone to these lengths is because a controlled shutdown is difficult to achieve, or has some other downsides compared with simply "pulling the plug" yes?

A Pi really isn't really any different than your desktop. If you suddenly loose power, you can corrupt the file system under the right conditions. Depending on how your system is configured and what its doing at the time of power loss, your odds of corruption could be anywhere from guaranteed to 1 in a trillion.

It really depends on how much you care about potentially loosing data.

For example if not loosing data is important to you, you could do something like this.
https://www.youtube.com/watch?v=m20o3P-S5s8

Is it possible to clear the console from gcode?

I use M118 in my gcode a lot so i can monitor a prints process, and it would be nice to be able to automatically clear out the console from a previous run in my start-up code.

I should add this is the Duet wifi that comes with an external antenna.

@bearer said in DWC randomly doesn't load:

The common issue would be wifi signal; if you could connect a usb cable and run M122as close to when it happens as possible it may help diagnose. (other issues as well as the wifi)

I can try that the next time it happens, but in the meantime attatched is an m122 output from right now while I am connected.m122.txt

@Danal said in DWC randomly doesn't load:

@bearer said in DWC randomly doesn't load:

The common issue would be wifi signal

He said it pings, even when the browser is hanging. If we absolutely verify that's true, it can't be wifi.

Thats correct when i can't get Chrome or FF to connect, I can ping the machine and always get a good response.

I've had my printer up and running for about 2 months now, and I have faced an issue since day one that is driving me crazy.

Some times when I power on the machine, or close out a browser window and leave the machine on for a few hours, when I try and load DWC, it just wont load, and the browser eventually times out.

Every time I've faced this issue I've pinged the machines ip and never lost any packets or had bad latency. The only thing that seems to fix the issue, is power cycling the machine, removing the SD card a few times or some times both.

Why does this happen and what do i need to do to fix it?

pertinent information:
Duet Web Control 2.0.4
Board: Duet WiFi 1.02 or later + DueX5
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05 (2019-12-13b1)
Duet WiFi Server Version: 1.23

@SnakeSP I feel your pain, as Ideamaker is the same way. It says i can put the seam anywhere, but it always puts it at a corner. I'm going to try this out with a large diameter cylinder instead of a square.

This question is mainly directed towards @dc42, but anyone should feel free to chime in.

I recently finished a railcore ii 300zl, and while researching how to minimize ringing I came across the M593 option.

In a different thread @dc42 mentioned this.

@dc42 said in M593 Dynamic Acceleration Adjustment no effect:
perimeter (frequency = speed/pitch). At low accelerations, the pitch of ringing will be compressed close to the corners because the head isn't up to speed yet, so ignore the pitch in that area.

One of the other things I found while doing research was this video (has some logic flaws imo) and it got me thinking.
https://www.youtube.com/watch?v=Ws1JfHl3Y0o

Would the following be a good/decent way of gathering and analyzing data?

• Secure a phone or any other devise with an accelerator and the ability to log data to the bed. A micro accelerometer attached directly to the hot end and wired to a raspberry pi (or similar) might give the best results.

• Write a macro that repeatedly moves the head back and forth across the machine at a constant velocity. For example starting at X0 Y0, it would be something like G1 X300 F9000 G1 X0 F9000. Repeat this several times to gather a decent amount of data. Move to a different Y position and repeat.

• Do the same thing in the Y direction.

• Potentially repeat the two previous steps at different Z positions.

• Use FFT and Spectrograms to fine the most appropriate frequencies for the M593 command.

Thoughts?