I am not sure if this is the correct place to post this, but I had a print fail today. It seems it just stopped and reset mid print

Here are the M122 results.

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02RC2(RTOS) running on Duet WiFi 1.02 or later + DueX2
Board ID: 08DDM-9FAM2-LW4S4-6JKF0-3S86N-TLSVX
Used output buffers: 1 of 20 (8 max)
=== RTOS ===
Static ram: 28460
Dynamic ram: 98348 of which 0 recycled
Exception stack ram used: 328
Never used ram: 3936
Tasks: NETWORK(ready,328) HEAT(blocked,1232) MAIN(running,3540)
Owned mutexes:
=== Platform ===
Last reset 00:54:08 ago, cause: software
Last software reset time unknown, reason: Stuck in spin loop, spinning module GCodes, available RAM 3560 bytes (slot 1)
Software reset code 0x4043 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20001eec Task 0x5754454e
Stack: 00440817 004441f8 21000000 46a4e609 411a3b87 00000000 00000000 3e25e354 447a0000 447a0000 00000000 00000000 420fcdbe 450df418 3f96d506 40a00000 46adb5d4 c0000000 00005273 20000010 00000004 00000000 00000004
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 32.6, current 37.7, max 38.1
Supply voltage: min 23.8, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Expansion motor(s) stall indication: yes
Date/time: 2018-10-06 20:25:21
Slowest loop: 12.22ms; fastest: 0.07ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 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 ready with "M122 " 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 ===
Slowest loop: 214.07ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21
WiFi MAC address 5c:cf:7f:a4:03:d9
WiFi Vcc 3.41, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 17152
WiFi IP address 192.168.1.156
WiFi signal strength -55dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===
DueX I2C errors 0

@dc42

Thanks.

It looks like this is still in the early stages. It states that the "following commands will be supported", is the number command currently support? If so, how is the identifier determined?

What I am currently interested in is the current and active temps for tool0 and bed heaters. Maybe the fraction printed.

I installed a maestro on a printer with a 12864 display. With previous versions of the firmware the display would have the name and a number. Turning the encoder knob would increase or decrease the number.

With the latest version I get the following:

Error Loading menu
File Main
Can't open menu file

However, pressing the button on the display causes an emergency stop and the SD card reader works as well.

From the information that I have found I know it's not something that is fully featured or supported, but what is the current expected behaviour?

I probably missed something in the documentation, but I can't find anything about how to use the servo pin on the Duet Maestro.

What I am trying to do is use the servo pin to control a BLTouch. I tried the M280 command with various P values, but nothing has worked so far. All return a invalid servo index error.

If I disable a heater then I can get a M280 command to complete without error, but none of the heaters seem to be associated with the servo pin.

I suppose I could attempt to just use heater 2, but I don't think I would be able to connect the BLTouch to either of the connections for heater 2.

Any help would be appreciated.

Thanks in advance.

When I tried heater 3 the first time I was still using I1 instead of I0, so I tested this again and I was able to get it working with heater 3 and PWM1

I tried heater 7 and PWM5 again, that still isn't working. I may test some of the other configurations just to see if this is isolated to that connector, but I don't have any plans to use heater 3, so I might just call it good as long as everything is working.

Thanks!

Thank you!

Making the configuration changes seems to have solved the motor direction issue, I will test this more once I can home Z.

I was still using I1 in the M280 command, but after changing it I am still having the same issue. Here is the relevant configuration.

config

; Endstops
M574 Z0 S0 ; Define active low and unused microswitches
M574 X1 Y1 S1 ; Define active high microswitches

;  BL Touch
M307 H7 A-1 C-1 D-1 ;Disable heater 7 since it's being used to drive the bltouch servo. 
M558 P5 X0 Y0 Z1 H5 F160 T6000 ; Set Z probe type to switch 
G31 P25 X30 Y0 Z1.7 ; Set Z probe trigger value 

deploy probe

M280 P7 S10 I0

retract probe

M280 P7 S90 I0

I also tried using heater 3 by replacing the 7 with 3 in the M307 and M280 commands.

When deploying the probe I noticed that the LED indicator for the heater turns on and VIN is measurable across the heater output. Should that be the case?

Hi,

I purchased a Duex2 a while back that I am just getting around to using and I am having a couple of issues.

1. BLTouch isn't working when connected to the PWM connector.

   I had the BLTouch before the duex2. It was set up using the exact settings found in the guide here with the wires connected directly to the expansion header.

   I thought I would be able to plug the header into the PWM_5 and everything would continue to work, but that is not the case.

   I have checked the wiring multiple times and everything is correct. I checked for continuity between the PWM_5 signal pin and expansion pin 31 on the duex2 board. There was none, but I am not sure if there should be.

   I have tested connecting the wires back to the expansion header, and everything still works that way.

2. Direction issues with Drive 6.

   I setup Bed levelling using multiple independent Z motors. The motors for Z1 and Z2 always spin the correct direction. The Z3 motor, which is connected to drive 6, will sometime spin in the opposite direction. When this happens the axis moves the correct distance, just in the wrong direction.

   This was tested by entering G1 S2 Z5 F10 into the gcode console. However, I haven't fully investigated this issue, I have not yet tried with a different cable, motor, or any other firmware configuration, but I thought it would be worth mentioning.

Any help would be appreciated.

Thank you