Posts made by MarMed

Looks like it was still disabled from when accelerometers only worked in standalone mode, I built RRF with it enabled and it works!

@Phaedrux
It is a duetwifi to support SBC

FIRMWARE_NAME: RepRapFirmware for Duet 2 SBC FIRMWARE_VERSION: 3.4.4 ELECTRONICS: Duet 2 + SBC 1.0 or 1.01 FIRMWARE_DATE: 2022-10-20 16:17:59

Hi,

I'm gettting M955: Command is not supported when trying to enter any M955 command on my duet2wifi in SBC mode.

is accelerometer support on Duet 2 + SBC not supported?

Thanks,

Hey everyone,

I'd appreciate some help with this, I'm experiencing skipped steps during un-retraction after upgrading my Duet Maestro to 3.4.1, I've confirmed this by downgrading back to 3.3.

Did I miss something in the release notes?

@dc42
This is on beta4.1

Warning: Auto tune of heater 2 failed due to bad curve fit (R=0.030, C=0.001:0.000, D=2.3)

I think the problem may be a combination of a very low power heater(250w), and the situation that the heated bed gets the chamber close to the target temperature already, around 50C and I then use the the chamber heater to reach a stable 60C.

I've tried many combinations when tuning, with hotend and bed heater off, with hotend and bed heater on, and setting the ambient temperature. Each tuning takes 5h+ before it fails.

Any idea why my old heater parameters is giving me an error now?

M307 H2 B1 A29.9 C1151.3 D55
Error: M307: bad model parameters

is there manual parameters that might work with my setup in 3.2?

Help is appreciated.

With beta3.2 I am getting the following error from setting the model parameters for my chamber heater

M307 H2 B1 A29.9 C1151.3 D55
Error: M307: bad model parameters

on previous versions the parameters would set correctly.

11/19/2020, 11:37:31 AM	M307 H2
Heater 2 model: gain 29.9, time constant 1151.3, dead time 55.0, max PWM 1.00, calibration voltage 0.0, mode bang-bang
11/19/2020, 11:37:28 AM	M307 H2 B1 A29.9 C1151.3 D55

just to note, the parameters used is from previous RRF3.2 betas, but with the bad curve error, due to dead time being negative I used the recommendation here to measure and set the dead time manually.

Additionally I receive a bad curve fit using the new tuning algorithm, is there a similar workaround using the new tuning?

RRF3.2 Beta3.2 on LPC

Thanks

@arhi these photos were taken before I knew the issue, and I already soldered the pad, so I apologize for the poor photo quality.

So after receiving the boards from JLCPCB($36.37) to avoid turning your hairs gray troubleshooting, check for lifted pads on the buffer ICs. I happened to have 1 board out of 10 where the TFR pin was not soldered.

This is my homez.g

; homez.g
; called to home the Z axis
;
G91

; Lift Z
G1 Z5 F6000 H2
G90
; Go to first bed probe point and home the Z axis
G1 X100 Y138 F6200
G30

; Uncomment the following lines to lift Z after probing
G91
;G1 Z3 F1000
G90

@dc42:

I have taken a look. It appears to have got stuck in the SD card driver because a command failed to complete. I have seen at least one other occurrence of this.

I have it in mind to add a timeout to that function to avoid the reset happening.

Thank you for taking the time to look into it, I forgot to include that I had tried to load the duet web control page to check on the printer's progress when the reset happened.

Just had a reset mid print, not sure whats going on.

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.20 (2017-12-23)
WiFi Server Version: 1.20
Web Interface Version: 1.20

M122
=== Diagnostics ===
Used output buffers: 3 of 32 (9 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20 running on Duet WiFi 1.0
Board ID: 08DAM-999TL-MQ4S4-6J1F2-3S86L-94GHZ
Static ram used: 15448
Dynamic ram used: 98976
Recycled dynamic ram: 264
Stack ram used: 1392 current, 4384 maximum
Never used ram: 12000
Last reset 00:01:37 ago, cause: software
Last software reset at 2018-01-14 05:27, reason: Stuck in spin loop, spinning module Network, available RAM 3848 bytes (slot 2)
Software reset code 0x4041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f80f, BFAR 0xe000ed38, SP 0x2001f9ac
Stack: 0042c995 00008196 0043c277 00008196 ffffffe9 00001000 00081111 40080000 00008196 20002d8c 00437273 0043ab86 210b0200 3e1aa000 3e24de00 00000009 00000009 3e178897 45870070 438ff91a 44fc01bd 00000000 4964e1c0 44841fba
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 28.4, current 29.7, max 31.4
Supply voltage: min 0.8, current 0.9, max 4.0, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2018-01-14 05:29:51
Cache data hit count 354749734
Slowest main loop (seconds): 0.014096; fastest: 0.000035
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.20
WiFi MAC address 60:01:94:09:18:33
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 17232
WiFi IP address 192.168.0.218
WiFi signal strength -65dBm, reconnections 0, sleep mode modem
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

So thankful for this release! Wait for thermostatic fans on power off, adjustable PWM frequency, and so much more!

Thanks!

This is what my section of the config.g file looks like, nothing is immediately screaming out to me as wrong, but maybe give it a try.

But your motor currents are a bit high, assuming your motors are similar, particularly the Z axis motors are extremely high, I initially based my configuration off of the config on GitHub but have since then changed quite a bit of it, I had a big improvement on Z stepper motor noise once I lowered the values. Check your stepper motor model numbers to be sure.

M350 X16 Y16 Z16 E16 I1 ; set 16x microstepping with interpolation
M92 X80 Y80 Z400 U400 E96 ; set axis steps/mm
M566 X480 Y480 Z12 U12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z1200 U1200 E3000 ; Set maximum speeds (mm/min)
M201 X800 Y800 Z100 U100 E5000 ; Set accelerations (mm/s^2)
M906 X700 Y700 Z351 E918 I30
M84 S30 ; Set idle timeout

I have the same printer, please post your config.g and I'll take a look.

Starting with Beta11, with the M584 changes, with the U axis hidden if I run G29 the printer starts probing, but after the first row the U drive, which is my second Z motor starts moving up rather than down.

@dc42:

M307 now accepts an F parameter to allow the PWM frequency to be set. Caution: do not use excessively high PWM frequencies, especially with the bed heater, because you may overheat the mosfets.

This feature I am especially excited to try out, I've had to use bang-bang for my heated bed because with PID a couple nearby lights in my house would visibly flicker.