Posts made by chrishamm

@davidjryan Thanks for reporting this. It will be fixed in the next version.

@umutduman It sounds a lot like you fried the MCU with your custom circuitry. The MCU should never get hot, but if you overload the pins or connect more than +3.3V to them, that will physically damage the processor. So I think a MCU replacement is your only option. I'd be quite surprised if you managed to damage the MCU only by configuring the SPI peripheral or DMA wrong.

@jltx You can access logs using journalctl (e.g. journalctl -u duetcontrolserver -e) but I doubt anything else will show up there. Do you have any other applications running on your SBC? The message you got means something blocked the main process on the SBC from performing a data transfer.

@jltx I'm sorry but DWC no longer supports old Safari or Internet Explorer versions.

@jltx M929 isn't really needed in SBC mode because journald already keeps track of most important messages. When did you flash your microSD card? Is it rated A1 or A2? Can you confirm that vcgencmd get_throttled via SSH/terminal outputs 0x0 (not throttled)?

If you are still using the Debian Buster-based image, it's time to upgrade: https://docs.duet3d.com/en/How_to_guides/SBC_Buster_to_Bookworm

@oozeBot We have some more background information about the cause of this problem; it appears to affect the 6HC/6XD only. @dc42 is going to improve the upgrade mechanism in 3.6.0 stable.

On behalf of the Duet3D team I am pleased to announce the availability of version 3.6.0-rc.2. This is likely to be the final release candidate before we release our software as 3.6.0 stable, so please do test this build to avoid unexpected complications. If you find any issues, please open a new thread with [3.6.0-rc.2] in the title.

As always, please check the release notes notes first for

• RepRapFirmware
• DuetSoftwareFramework
• DuetWebControl

This task can be simplified using the ReleaseMgr plugin, too.

Users in standalone mode can upgrade by uploading the firmware bundle from here.
Users in SBC mode may need to change to the unstable package feed before upgrading all packages (e.g. via M997 S2). Please note that M997 S2 does not work on deprecated Buster-based Debian/DuetPi images. See here in case you need to upgrade.

If you are happy with this release candidate, feedback in this thread is welcome!

@stuartofmt I wouldn't recommend Telnet in SBC mode, it's insecure. In SBC mode, the DuetPiManagementPlugin only tries to activate the Telnet server via xinetd.

If you need a TCP port to send/receive G-code data, you'll have to write a plugin for SBC mode or wrap it around the HTTP API.

PS: It might actually suffice to forward a TCP port to the CodeStream/CodeConsole application in /opt/dsf/bin. Those utilities use the Telnet G-code channel by default.

@Serbitar This is going to be fixed in the next release candidate.

@achrn said in dsf-python-3.6.0rc1 http endpoint not working for me:

await http_endpoint_connection.send_response(200, "so happy you asked for it!")

This call looks wrong to me. I think you need to specify a third parameter like HttpResponseType.PlainText to actually send out data. Otherwise you only return a status code.

@moth4017 The display precision is set by the number of decimal places to display for Z. If you increase it to three digits in the settings, your custom value should be displayed correctly.

@achrn It should be available via the package feeds as well now.

@achrn There were some errors in the previous 3.5 dsf-python client which renders parts of it unusable with 3.6. Hence I suggest you upgrade to dsf-python 3.6-rc.1, I expect that will fix your problems.

Closing as duplicate.

@Triet Did you upgrade the WiFi server firmware as well?

@Triet I don't think the Windows ftp utility supports that setting but I think WinSCP does, although it's been a while since I used it. AFAIR it's this bit in Options -> Preferences -> Transfer -> Background:

If that doesn't work, I suggest you try out FileZilla Client with the setting @droftarts mentioned.

@Triet Make sure to set the number of concurrent connections to 1. RRF in standalone mode cannot handle more.

@bdelia Thanks for the Wireshark dump. What I find odd is that your PC keeps aborting connections to the Duet, which shouldn't happen unless you set the number of AJAX retries in DWC -> Machine-Specific to a very high value. If that is the case, the effective timeout of regular requests becomes very low which may lead to complications. In doubt, perhaps delete dwc-settings.json from the System Files and reload DWC.

If that does not help, I suggest you try a different device (like a smartphone) to upload a bigger file. If that works, try to reset the TCP/IP stack of your Windows machine as outlined here: https://support.microsoft.com/en-us/topic/how-to-reset-tcp-ip-by-using-the-netshell-utility-d954430c-9b11-43f0-6081-0fc9235a8b4a That might help, too.

What kind of microSD card do you have? From the Wireshark dump I can see that RRF doesn't seem to accept more data within 15+ seconds so that does seem like an I/O issue to me. It might be worth to replace the SD card with a class 10 (possibly even A-rated) microSD card and to check if the problem persists then.

@omtek Thanks, I've got a fix ready. It might be possible to work-around this problem by setting an arbitrary update interval but that depends on the webcam server.

@Hotchef54 First of all, I suggest you upgrade to 3.5.4. We don't support outdated firmware versions.

You can find an in-depth guide for an Ender 3 conversion to the Duet 3 Mini 5+ here, which isn't too different from the Duet 2: https://docs.duet3d.com/en/How_to_guides/e3p_Mini5+_guide_part1_wiring

Also, you can use the legacy version of the configtool if you really need the template for the Ender 3 Pro: https://configtool.reprapfirmware.org/legacy/Start It's quite likely you need to make changes to the default tempate, though.