Topics created by UnderDoneSushi

@underdonesushi said in Error:short-to-ground/over temp shutdown reported by driver 2:

I assume they don't need to match the other drivers that are on the DuetWifi 2.

correct

@UnderDoneSushi said in M111 Debug shows : Network(1) and not Wifi Module?:

I think I am confused because when I run M552, it doesn't give the status of the wifi module. I was thinking my DuetWifi was thinking it is a Duet with a network connection. I am just going to upgrade the firmware because it is pretty old at this point. I just don't think I can take the plunge into 3.0x yet....

ah, well, wifi is network module, its just not an ethernet network.

to see the status specifically related to the wifi module look at M122 and almost at the bottom there will be some wifi status (you might have to configure your terminal line ending as the output is very long over several lines separated by line feed (LF)

@UnderDoneSushi You should be able to use the PINDA probe without the thermistor in RRF2, and it's supported with the thermistor in RRF3. See these threads about how to wire it up and configure in RRF2:
https://forum.duet3d.com/topic/9045/pinda-v2-probe-wiring
https://forum.duet3d.com/topic/11838/z-probe-input-signal
https://forum.duet3d.com/topic/11866/pinda-z-probe-configuration

If you can report back if this works, I'll add it to the wiki.

Ian

The reason is that you have loaded a height map and you have specified a very low Z jerk value (12mm/minute) in M566. The firmware is slowing down movement so that it can apply bed compensation without having to exceed the Z jerk limit when it needs to change the rate at which it applies Z compensation. Try increasing the M566 Z value.

@UnderDoneSushi said in Mesh Bed Layout app:

just want a visual for seeing the layout.

You do get a visual of the heightmap after running a G29. 😊

A quick search of the source indicates "home.g" is not used by the firmware.

homedelta.g is used for Delta (and Rotary Delta and etc. ) kinematics.

homeall.g is used for all other kinematics.

home.g is not used.

I'd delete it.

@dc42 Thanks for your response DC42. Right that part is helpful, I forgot about that part of the RRF Config Tool. Sorry I wasn't specific enough, but something more along the lines of a window (live scrolling/updating config.g and etc below say if you were changing "stepper motor currents". The window would highlight the code that is currently being changed.

I know it is probably overly complicated, I was just wondering if it was in the works for the RRF Config Tool or add it to a wishlist?

@underdonesushi said in Config.g Library / Advisement:

I am just curious if there is any such source as a Config.g Library for sharing personal setups?

Yes, this forum.

Similar to that, is there a discord for personal advisement on coding your printer/Duetwifi?

Yes, this forum.

Not "required". You can delete it at any time, and/or ignore it by not having an M501 in config.g, or by executing an M502. Specifically:

M500 writes a subset of currently active settings to /sys/config-override.g. (Want to know which subset? Do an M500 and look in /sys/config-override.g).

M501 reads from /sys/config-override.g and executes the commands found there. Assuming they were written with an M500, this has the net effect of setting parameters to what was 'saved' with the M500.

M502 reads that same subset from /sys/config.g, effectively 'undoing' anything that was done with an M500/M501.

Those three commands are it... Therefore, if you want /sys/config-override.g to have any effect at printer boot, there MUST be an M501 in /sys/config.g, Preferably near the end. If you want to have it ignored, just don't have an M501 in /sys/config.g.

Officially I'm not saying it is good or bad. ☺

The screen is nice. But the firmware development is way behind... Way behind....

The disconnects are probably caused by low WiFi signal strength at the Duet and/or interference. See https://duet3d.dozuki.com/Wiki/WiFi_disconnections_and_AJAX_timeout_errors. Recent firmware versions to automatic reconnects.

@underdonesushi can you send M122 and M115 in the console and post the results?

When it disconnects is the wifi light illuminated on the Duet board?

@dc42 said in Calibrating the Z probe trigger height:

M564 S0

Yeah, the Mini Differential Sensor I assume is stopping it, I didn't know there was a behind the scenes limiting factor.
Thank you I will try it once I get home and report back!