@dc42 said in New board but no working WiFi.:
[ERROR] Printer is not online.
WiFi reported error: no known networks found
WiFi module is idle
But!!! It does not turn blue or blinking
The configuration is working! When I put the memory card in my first Duet2 WiFi it does connect to my WiFi and
If I put the memory card from my first Duet2 WiFi and put it in this one there is NO WiFi
When creating the GCode file in Simplify the last layers I created them with a very large plane that had never happened to me before.
By putting the GCode file generated from that piece and trying to enter the files on the board, I got the error. Using the M30 command and the file name was solved. (And luckily ...).
It allowed me to reconnect with the board (I have the wifi version) and enter the rest of the options, but once I tried to access the saved GCode files again, it was disconnected and the error came out again.
@jan-doubrava said in Web interface - shutting down during printing:
08:17:32.178 : Ran out of output buffers at ../src/Networking/HttpResponder.cpp(950)
Did you have just one browser connected to the Duet before that happened, or multiple browsers/devices? I'm trying to work out what provokes this situation.
I have made a change for 2.02RC6 to return a 503 status response to DWC if the firmware runs out of buffers. I hope this will allow the apparent deadlock to be broken.
I don't see anything wrong with that config.g file either. However, the config-override.g looks to me as though it was created by sending M500 after the Duet was booted without the SD card present, because all the values are default values and the delta parameters are not present.
Please delete that config-override.g file (you can do this in the System Editor of DWC), then press the Refresh button and verify that the file has gone. Then send M500 again, verify that config-override.g has been created, check its time stamp, and check whether it now contains the delta parameters.
In my opinion this is where a Duet powered CNC differs from other CNC machines in a good way.
Typically the other CNC machines are run from a different computer/device over USB (using some form of Gcode Sender software) - USB (or more specifically an older Serial connection) is slow, have delays and a few other factors making it less ideal to send a lot of small line segments in quick succession (this is why I don't like to 3D print over USB and also advise against it). For these machines to implement such an arc feature where the arc is sent as a single segment, then divided into smaller segments by the machine machine (in all 3 planes), makes a lot of sense (less data to send).
The Duet in comparison have high speed SPI to the microSD card, uses a much more capable processor and thus can read the line segments in quick succession without the delay of Serial over USB.
I have, with my Duet powered CNC cut wavy shapes and they came out smooth (without a noticeable stutter, using the Post side segmentation - having a powerful PC calculate them is more efficient than having to calculate them on an under powered processor as long as you can get all of the information transmitted/read fast enough).
@jgrouse said in resume.g and using a laser:
G1 R1 X Y Z30 S0 F9000
G1 R1 X0 Y0 Z30 S0 F9000
G1 R1 X0 Y0 Z0 S0 F9000
That should command the head to 30mm above the pause point, then down to the pause point, and then resume the laser.
Yes, for me G92 should behave exactly like G10 L20 i.e. it should as well handle the machine limits in a correct way. I don't see any reasons to allow G92 before the machine is homed.
My understanding regarding the different coordinate systems for CNC is the following:
Level 1: Machine coordinate systems
Are typically set only once and are rarely changed over the machines lifetime.
Using M208 in the config file makes sense for me here.
Level 2: Working Coordinate Systems (WCS) , G54...G59.3
They are more dynamic and mostly refer to setups that can be individual to a certain job, but can also refer e.g. to a corner of a vise or the center of 3-jaw chuck mounted.... They are typically set by the machine operator prior to running a program and only referred but not modified by the NC-program. (*)
Level 3: G92
The G92 command is typically used to set a WCS from within a program e.g. for machining a number of identically parts in a row (to do so you make a loop in the NC-code and at the end of the loop there is e.g. G92 X-50 for shifting the WCS by 50mm for the next iteration).
That at least is my take on it. Additionally there should be as well a command to cancel G92. Sometimes this is G92.1.
(*) PS: ...in that context for doing CNC with the Duet my biggest two wishes currently would be:
G53...G59.3 should be automatically stored like it is done for the bed-compensation
Same thing for tool-offsets: In the NC world the tools are not so static as in the printing world where you typically define them in the machine configuration. But it is also annoying to re-zero the tools anytime the control is restarted.
@mwinterm said in G53 command:
@dc42 : ...just noticed that there is already a built RC5 available... However I saw that in the release notes you refer to a modification of G54 instead of G53.... small typo but could be confusing as G54 (i.e. WCS) should for sure take tool offsets into account....
It should have read G53. I have corrected it.
That's one for chrishamm to answer, because he write the filament management and implemented the M701-M703 commands.
As with many other things, a check will be easy to implement when we have added support for conditional GCodes and the RRF object model.
@acqt said in M587: Bad or missing parameter:
M587 S“NETGEAR36” P”xxxxxxxxxxxx480”
Yes, your Mac has used smart quotes. It should look like this:
M587 S"NETGEAR36" P"xxxxxxxxxxxx480"
Can you see the difference?
Which program on the Mac did you use to send the commands? We need to put a warning in the documentation about this.
Your M665 line in config.g is not viable, because the R (delta radius) parameter is way too large for the L (rod length) parameter . Correct it, also delete the M664 and M665 lines in config-override.g, and try again.
Hint: delta radius is usually about half the rod length.
I looked print script. M84 is used at the very end.
M117 Layer end
M104 S0; turn off extruder
M140 S0; turn off bed
G91; Relative positioning
G1 Z20 F9000
G90; Absolute positioning
G1 X160 Y270 F9000
M84; disable motors
M300 S2000 P500
My mistake was at the beginning of printing.