@gloomyandy oh ok, yeah I was expecting an actual temperature. Thanks.

@chrishamm Thanks for that .....could I ask a stupid question, I am new to python and the Duet. I am trying to write a function that will return a queried result of the object model back to the caller. I am adding the function to my copy of DuetWbAPI.py. I would like to pass the function a string like 'sensors.probes' and have it return just that portion of the object model. for my machine, a duet 3 w/o SBC it uses the rr_model/key='sensors.probes' and that works fine. I want this to be one function for either type of client so they need to share the passed parameters. So far I have
def getModelQuery(self, key):

def getModelQuery(self, key): if (self.pt == 2): logger.info('in non sbc') if not self._rrf2: #RRF 3 on a Duet Ethernet/Wifi board, apply buffer checking sessionURL = (f'{self._base_url}'+'/rr_connect?password=reprap') r = self.requests.get(sessionURL,timeout=2) if not r.ok: logger.warning('Error in isIdle: ' + str(r)) buffer_size = 0 while buffer_size < 150: bufferURL = (f'{self._base_url}'+'/rr_gcode') buffer_request = self.requests.get(bufferURL,timeout=2) try: buffer_response = buffer_request.json() buffer_size = int(buffer_response['buff']) except: buffer_size = 149 replyURL = (f'{self._base_url}'+'/rr_reply') reply = self.requests.get(replyURL,timeout=2) if buffer_size < 150: logger.debug('Buffer low - adding 0.6s delay before next call: ' + str(buffer_size)) time.sleep(0.6) URL=(f'{self._base_url}'+'/rr_model?key=' + str(key)) try: r = self.requests.get(URL,timeout=2) j = self.json.loads(r.text) except Exception as c1: logger.info('bad JuJu' + ' ' + str(c1)) return ('failed') if not self._rrf2: #RRF 3 on a Duet Ethernet/Wifi board, apply buffer checking endsessionURL = (f'{self._base_url}'+'/rr_disconnect') r2 = self.requests.get(endsessionURL,timeout=2) return (j) if (self.pt == 3): logger.info('in sbc') URL=(f'{self._base_url}'+'/machine/status') r = self.requests.get(URL,timeout=2) j = self.json.loads(r.text) if 'result' in j: j = j['result'] thing = key.split(".") ja=j[thing[0]][thing[1]] return (ja)

This works but does not allow me to expand the number of indices so it isn't very flexible. Is there an easy way to take the input string and use it to query the whole object down to what I want and allow for flexibility in the number of indices? Or is there a completely different way of doing this that I am ignorant of? Thanks.

@gnydick that sounds great! I've sent you a DM so we can arrange something.

@dc42 That makes sense. PrusaSlicer can put it in at the beginning using custom g-code (which is what I was doing), but it doesn't by default. So I agree it's better to check just the end. Thanks for your reply!

@vcapra1 said in Uploads not working:

cluster size 4kb

That seems like an odd cluster size. 32 or 64kb is recommended.

I suggest you take the SD card out of the Duet and use your PC to back up the contents by copying the files. Then use the SD card formatter tool to wipe and format it. It will choose the most appropriate format based on the card.

https://www.sdcard.org/downloads/formatter/

Then copy the files back onto the card and test it out with M39 again and try and upload a file.

@phaedrux Oneplus 8 Pro (doesn't matter if I run it at FHD or 4k) on chrome and brave. DWC 3.3.0

Well I did find something that works
{ip address of printer}/rr_model?key=sensors.probes

@jay_s_uk Thanks, I'll add it back in RC2:

e2801dee-6412-44fa-94b2-604d97599aae-image.png

@achrn you will need to make those files available to us somehow (e.g. via Dropbox or Google Drive) if you want us to look into this issue.

Yes it's possible to go back and forth, though you probably won't want to.

@deonholt said in Please help me update Duet Web Control:

Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

SeeMeeCNC is an authorized reseller and would be able to swap the board under warranty. I'm not sure what the warranty is on their complete machines, but the Duet itself would have a 1 year warranty serviced by Duet3D.

That ended up not working. I am assuming a faulty raspberry pi. I am running in standalone mode now until the 8gb Pi 4's are back in stock.

@phaedrux Awesome! Thank you for the quick and detailed response.

I know thanks does not respond well the command compared to before now they are both activated simultaneously. there is something wrong. if I go from the dual panel it works for example but we will see thanks. I did not quite understand if the developer of the firmware is only Mr. Dozuki or beyond people.

@adamfilip this is a fault with 3.4b7. either update to 3.4b7+7 or the new 3.4RC1

@azaelaguirre said in Your Duet rejected the HTTP request: page not found:

Check that the SD card is mounted and has the correct files in its /www folder

Did you check the files in the /www folder? What do you see?

final update:
I had my organization purchase a new Ethernet module off of ebay, installed said module and everything is running as expected again.
Many thanks for all your help 🙂

@chrishamm

Still getting DCS Error...

"Does the DIAG LED on the Duet blink or is it dimmed?"

Not sure which one that is, looking at the wiring diagram LED V FUSED and LED 12V are the only ones active and showing a solid light. All other lights LED ACT, LED STATUS, LED +5V, and LED +3.3V do not turn on even during powering on the PSU Again Pi is powered by an independent 5V PSU and Mini is powered by a 24 PSU

"Do you have firmware 3.3 installed on the board?"

Yes checked with M115 Reflashed using Fallback procedure #1 and Fallback procedure #2 SD Card was removed after confirming again with YAT RRF is up to date

"If you have a multimeter, you can also check continuity between pin 22 of the Pi and Duet. When you're at it, you could check pin 17 as well, because that signal is required for SPI comms, too."

Checked with a multimeter and continuity is fine for both pins

Trying terminal again

Feb 06 22:19:30 duet3 DuetControlServer[4022]: Duet Control Server v3.3.0 Feb 06 22:19:30 duet3 DuetControlServer[4022]: Written by Christian Hammacher for Duet3D Feb 06 22:19:30 duet3 DuetControlServer[4022]: Licensed under the terms of the GNU Public License Version 3 Feb 06 22:19:30 duet3 DuetControlServer[4022]: [info] Settings loaded Feb 06 22:19:31 duet3 DuetControlServer[4022]: [info] Environment initialized Feb 06 22:19:31 duet3 DuetControlServer[4022]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin) Feb 06 22:19:31 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'. Feb 06 22:19:31 duet3 systemd[1]: Failed to start Duet Control Server. Feb 06 22:19:32 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart. Feb 06 22:19:32 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 87. Feb 06 22:19:32 duet3 systemd[1]: Stopped Duet Control Server. Feb 06 22:19:32 duet3 systemd[1]: Starting Duet Control Server... ----------------------------------------------------------------------------------- pi@duet3:~ $ gpioinfo gpiochip0 - 58 lines: line 0: "ID_SDA" unused input active-high line 1: "ID_SCL" unused input active-high line 2: "SDA1" unused input active-high line 3: "SCL1" unused input active-high line 4: "GPIO_GCLK" unused input active-high line 5: "GPIO5" unused input active-high line 6: "GPIO6" unused input active-high line 7: "SPI_CE1_N" "spi0 CS1" output active-low [used] line 8: "SPI_CE0_N" "spi0 CS0" output active-low [used] line 9: "SPI_MISO" unused input active-high line 10: "SPI_MOSI" unused input active-high line 11: "SPI_SCLK" unused input active-high line 12: "GPIO12" unused input active-high line 13: "GPIO13" unused input active-high line 14: "TXD1" unused input active-high line 15: "RXD1" unused input active-high line 16: "GPIO16" unused input active-high line 17: "GPIO17" unused input active-high line 18: "GPIO18" unused input active-high line 19: "GPIO19" unused input active-high line 20: "GPIO20" unused input active-high line 21: "GPIO21" unused input active-high line 22: "GPIO22" unused input active-high line 23: "GPIO23" unused input active-high line 24: "GPIO24" unused input active-high line 25: "GPIO25" unused input active-high line 26: "GPIO26" unused input active-high line 27: "GPIO27" unused input active-high line 28: "RGMII_MDIO" unused input active-high line 29: "RGMIO_MDC" unused input active-high line 30: "CTS0" unused input active-high line 31: "RTS0" unused input active-high line 32: "TXD0" unused input active-high line 33: "RXD0" unused input active-high line 34: "SD1_CLK" unused input active-high line 35: "SD1_CMD" unused input active-high line 36: "SD1_DATA0" unused input active-high line 37: "SD1_DATA1" unused input active-high line 38: "SD1_DATA2" unused input active-high line 39: "SD1_DATA3" unused input active-high line 40: "PWM0_MISO" unused input active-high line 41: "PWM1_MOSI" unused input active-high line 42: "STATUS_LED_G_CLK" "led0" output active-high [used] line 43: "SPIFLASH_CE_N" unused input active-high line 44: "SDA0" unused input active-high line 45: "SCL0" unused input active-high line 46: "RGMII_RXCLK" unused input active-high line 47: "RGMII_RXCTL" unused input active-high line 48: "RGMII_RXD0" unused input active-high line 49: "RGMII_RXD1" unused input active-high line 50: "RGMII_RXD2" unused input active-high line 51: "RGMII_RXD3" unused input active-high line 52: "RGMII_TXCLK" unused input active-high line 53: "RGMII_TXCTL" unused input active-high line 54: "RGMII_TXD0" unused input active-high line 55: "RGMII_TXD1" unused input active-high line 56: "RGMII_TXD2" unused input active-high line 57: "RGMII_TXD3" unused input active-high gpiochip1 - 8 lines: line 0: "BT_ON" unused output active-high line 1: "WL_ON" unused output active-high line 2: "PWR_LED_OFF" "led1" output active-low [used] line 3: "GLOBAL_RESET" unused output active-high line 4: "VDD_SD_IO_SEL" "vdd-sd-io" output active-high [used] line 5: "CAM_GPIO" unused output active-high line 6: "SD_PWR_ON" "sd_vcc_reg" output active-high [used] line 7: "SD_OC_N" unused input active-high -------------------------------------------------------------------------