Posts made by Dan1990

I have fixed the problem.

My measurement was taken too quickly and the probe wasn't giving correct data.

Thank
Dan

@t3p3tony

Well, the probe gives me different values after when the chamber is heated, or sometimes I will even get a measurement error ( measurement inconsistent or something similar ).

I thought that the probe is the issue but I have changed a few of them already and always end up with the same issue.

The probe is OMRON MICROSWITCH (D2F-5L).

@T3P3Tony

M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 2624, free system stack 2762 words
Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.2%,115) CanAsync(notifyWait,0.0%,57) CanRecv(notifyWait,0.0%,74) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,2.8%,57) MAIN(running,92.0%,352) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
Last reset 01:01:59 ago, cause: software
Last software reset data not available
Driver 0: position 0, 422.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 23, reads 44706, writes 0, timeouts 0, DMA errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 0/7, peak Rx sync delay 214, resyncs 0/0, no step interrupt scheduled
VIN: 24.3V
MCU temperature: min 44.9C, current 58.0C, max 67.9C
Ticks since heat task active 245, ADC conversions started 3719987, completed 3719985, timed out 1, errs 0
Last sensors broadcast 0x00000002 found 1 0 ticks ago, loop time 0
CAN messages queued 39538, send timeouts 0, received 29562, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer detected: yes, status: 00
I2C bus errors 0, naks 0, other errors 0

Good evening,

I have an issue with TB v1.1. I think is overheating.

The printer is inside the chamber which heats up to 60C more less.

My question is, does TB can be affected by a temperature that high?

The reason for my question is that after proper heat up, the toolboard gives me different reading each time ( clicky probe - Z_probe based on microswitch)

Thanks
Dan

The Klipper firmware seems to work fine with the ERCF, so perhaps will be valuable to check their code? It wIll gives more understanding towards what oc'geek and many others trying to get. (The voron - duet community is big )

That is the link to the PCB for ERCF:

https://github.com/Tircown/ERCF-easy-brd

Link to the project:

https://github.com/EtteGit/EnragedRabbitProject

@dougal1957

Thank you,

Issue solved.

Good morning,

I have disabled HTTP on my Duet 3 6HC (SBC mode) and I cant not access it via a web browser. I have typed M586 P0 S0 and suddenly I have lost connection.

I can connect via terminal but nothing more.

The message what I am getting from a web browser is:

`
This site can’t be reachedduet3.local refused to connect.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
`

How can I fix it?

Thanks
Dan

Thank you for all your replies! Now I am sure Have a good weekend

@droftarts

The heated bed is powered from the mains.

Good evening,

I performed the calculation to figure out the power consumption of my printer and I am not sure if I am correct.

My PSU at the moment is 24V and 25 A non - name brand. I would like to change it to Meanwell and I wonder what size of PSU will be most suitable for me.

My setup:
Duet 3 HC
5 motors - e3d High Torque Motor - 1.62 A
1 motor - e3d compact but powerful - 1.62 A
Hot end - E3D V6 - 40W heater - 1.6 A
Hotend fan - no data for PC but so I assume is around 0.1A
Blower fan - no-name from Aliexpres - 0.1A

So, the sum of all current is 11.52A. Taking into consideration that the motors are not running on full power, therefore the PC will be lower.

I reckon that the Meanwell 350.4W 24V 14.6A LRS-350-24 will be enough but I will appreciate a second opinion.

Thanks
Dan

@Phaedrux

I think I have fixed the issue.

The SBC and Duet had external PSU 5v, the cable for SBC was going in the same path where the Bed cable is. Somehow, those two were interfering with each other (inducing current/voltage) and creating issues. Also, my ribbon cable was going under the duet which wasn't helping as well.

I have disconnected 5v PSU and now the Duet powers up the SBC. The ribbon cable is above the duet. I had a successful 2.5h print.

Those parts are very sensitive to be honest.

@camcamnz

Thanks,

I have the same issue as you, and I think I have found a lead to solve it. I disconnected the bed and for now, everything looks fine.

@camcamnz

how did u access the:

/varlog/syslog

I have the same problem but when I did connect it via duet->SBC still giving the same issue.

M122 code below:

24/01/2021, 09:31:36 M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6JTD4-3S06M-KV8GS
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 62932 of which 24 recycled
Never used RAM 146088, free system stack 200 words
Tasks: Linux(ready,77) HEAT(blocked,296) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,53) MAIN(running,1179) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:03:50 ago, cause: power up
Last software reset at 2021-01-24 08:51, reason: User, none spinning, available RAM 146088, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 25.4, current 31.1, max 31.3
Supply voltage: min 23.9, current 24.0, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
Driver 0: position 0, standstill, reads 45118, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 45118, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 45118, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 45118, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 45119, writes 14 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 45122, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-01-24 09:31:35
Slowest loop: 51.95ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 2 -1 -1 -1
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.2
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 834, send timeouts 1983, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 17
Last transfer: 1ms ago
RX/TX seq numbers: 5973/7561
SPI underruns 147, overruns 10
Number of disconnects: 1, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 36.91
Maximum length of RX/TX data transfers: 2564/48

Good morning,

I have run out into a problem that says:

Warning: Lost connection to Duet (Board is not available (no header)).

So, short story. Two days ago everything was fine, I was printing no issue. Today, I try to print something and that problem occurred.

I run diagnostics by M122 and for me everything looks fine:

For SBC I am using an SD card that was supplied with the Duet 3.

The duet was purchased a month ago so it's relatively new.

@Phaedrux

So, I have to announce that all the issues are solved now.

The problem with the bouncing was due to old firmware. The one which came with the board was 3.01. Somehow, that was interfering with the settings and doing all these strange things.

At the moment, I am able to do what I wanted. As I said before, the board and RRF are very well made and very complex. I reckon that the adventure with RRF and duet is begun.

I have messed up a few things and I am not sure if is better to erase the board and upload a new firmware.

To perform that I have to put a jumper over erase pins?

@jay_s_uk

Yes, it is like the homing file was in the loop.

Can that be related to M122?

When I do diagnostic it says M122 response too long, see the console.

M122 below:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later
Board ID: 08DJM-956BA-NA3TJ-6JTD4-3S06M-KV8GSUsed output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 154572
Dynamic ram: 162108 of which 52 recycled
Exception stack ram used: 216
Never used ram: 76268
Tasks: NETWORK(ready,2076) HEAT(blocked,1184) CanReceiv(suspended,3824) CanSender(suspended,1484) CanClock(blocked,1432) TMC(blocked,216) MAIN(running,4444) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:07:50 ago, cause: power up
Last software reset at 2021-01-05 17:38, reason: User, spinning module LinuxInterface, available RAM 76036 bytes (slot 3)
Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 28.5, current 28.8, max 28.9
Supply voltage: min 24.1, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Driver 0: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Driver 1: standstill, reads 57129, writes 0 timeouts 0, SG min/max not available
Driver 2: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Driver 3: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Driver 4: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Driver 5: standstill, reads 57130, writes 0 timeouts 0, SG min/max not available
Date/time: 2021-01-14 13:11:15
Slowest loop: 3.55ms; fastest: 0.21ms
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 2 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is ready with "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 0.46ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

• Ethernet -
  State: disabled
  Error counts: 0 0 0 0 0
  Socket states: 0 0 0 0 0 0 0 0
  === CAN ===
  Messages sent 258, longest wait 0ms for type 0
  === Linux interface ===
  State: 0, failed transfers: 1
  Last transfer: 17ms ago
  RX/TX seq numbers: 17840/17841
  SPI underruns 1, overruns 1
  Number of disconnects: 0
  Buffer RX/TX: 0/0-0
  === Duet Control Server ===
  Duet Control Server v3.2.0
  Code buffer space: 4096
  Configured SPI speed: 8000000 Hz
  Full transfers per second: 39.64
  Maximum length of RX/TX data transfers: 3140/624