Duex4 v0.2a (with Duet 0.6)

sylvaindc

I'll be having some fun with these documents. I'll document my findings here in case some archeologist ever stumbles over the 3rd known Duex4

Quick question that remains is a hardware one, can I just hook up the 24v fan to the heater pins, or do I need to add a cap in parallel or something to ensure proper PWM?

droftarts

@sylvaindc said in Duex4 v0.2a (with Duet 0.6):

I'll document my findings here in case some archeologist ever stumbles over the 3rd known Duex4

Ha! Think a Duex4 is rare? How about a 'Duet Shield'! There is some documentation: http://reprapltd.com/reprappro/documentation/multi-materials/electronics/index.html and an old post on the RepRap forums where @dc42 posted the schematic https://reprap.org/forum/read.php?4,822811 and board files here https://github.com/reprappro/Duet/tree/dev/Archive_Files/Shield-0.3 (the 0.3 version was the production version, I think, the 0.4 version never made it into production). Posted here for the same archaeologists...

I'm not sure how many multimaterial upgrades RepRapPro sold, but I don't think it was many. But I have a Duet Shield! Found it yesterday when wiring up a Duet06 to see if RRF1.22.6 works with DWC 3.2beta2 (it does! However, DWC 3.2 will be the last version that will work with non-Object Model versions of RRF, ie everything before RRF 3.0).

Ian

sylvaindc

Ok, small update.

From: https://reprap.org/wiki/Duet_pinout
- I localized the pins I should use: Pin: 23, Label: PC21, DuePin: D9, RepRapFirmwareUsage: heat[5] / E4_PWM.
From: https://duet3d.dozuki.com/Wiki/Using_servos_and_controlling_unused_IO_pins#Section_Logical_pin_numbers
- Although it doesnt mention Duex4 explicitly, the info on Duex2 and Duex5 I guess E4_PWM is logical pin number 6:
  - 3-7 seem to be available for heaters on expansion board
  - this is the 4th one (so 3 + (4 -1) = 6)

Does this make sense ?

dc42

@sylvaindc said in Duex4 v0.2a (with Duet 0.6):

Thanks @Phaedrux and @dc42!

I'll be having some fun with these documents. I'll document my findings here in case some archeologist ever stumbles over the 3rd known Duex4

Quick question that remains is a hardware one, can I just hook up the 24v fan to the heater pins, or do I need to add a cap in parallel or something to ensure proper PWM?

Just hook it up.

sylvaindc

@dc42 said in Duex4 v0.2a (with Duet 0.6):

@sylvaindc said in Duex4 v0.2a (with Duet 0.6):

I have @dc42's IR leveling meter hooked up to my Duet 0.6, using a pin on the expansion header https://miscsolutions.files.wordpress.com/2015/05/duet0-6-brd_0-781.png (Pin AD12 if I'm not mistaken). Does that just loop through to AD12 on the J7 EXPANSION1 header of the Duex4?, or should I find an other solution?

AFAIR, it just loops through.
Update: according to http://blog.think3dprint3d.com/2015/04/duex4-v02a-minor-updates.html AD12 does not loop through ( I guess it used to on the previous board). It is now exposed via the J16, which is the same jumper as we connect the ground wire to.

I can confirm that the IR sensor works as it should via the Duex4 board.

sylvaindc

@dc42 said in Duex4 v0.2a (with Duet 0.6):

@sylvaindc said in Duex4 v0.2a (with Duet 0.6):

Thanks @Phaedrux and @dc42!

I'll be having some fun with these documents. I'll document my findings here in case some archeologist ever stumbles over the 3rd known Duex4

Quick question that remains is a hardware one, can I just hook up the 24v fan to the heater pins, or do I need to add a cap in parallel or something to ensure proper PWM?

Just hook it up.
Sadly the 24v fans are still in the mail, but I went ahead and set it up in config.g:

M106 P0 T45 H1 S255 L1.0	; Existing fan on main Duet0.6 board
M307 H6 A-1 C-1 D-1	        ; Disable Heater 6 
M106 P1 H1 S255 L0 A6	        ; Reuse Pin: 23, Label: PC21, DuePin: D9, RepRapFirmwareUsage: heat[5] / E4_PWM as Fan

Sadly I dont see any change to the web frontend. I can only see one fan, and only if I select Tool 0.

Is there a way to see all fans in the web front-end?

Phaedrux

You won't see thermostatically controlled fans on the web interface.

sylvaindc

@Phaedrux said in Duex4 v0.2a (with Duet 0.6):

You won't see thermostatically controlled fans on the web interface.
Cool, that explains it!

sylvaindc

The plot thickens...
I hooked up the Duex4, IR probe work, but the Stepper on E1 doesnt.

So I decided to do a M115:

m115
FIRMWARE_NAME: RepRapFirmware for Duet FIRMWARE_VERSION: 1.26.1 ELECTRONICS: Duet 0.6 FIRMWARE_DATE: 2020-02-09b1

My Google-fu showed a few people who had the same issue, but I cant find a solution... Does anyone have an idea, am I doing something wrong, or is the Duex4 just no longer supported in 1.26?

Phaedrux

Can you pos the results of M122?

sylvaindc

@Phaedrux said in Duex4 v0.2a (with Duet 0.6):

Can you pos the results of M122?

Sure thing!

M122
=== Diagnostics ===
RepRapFirmware for Duet version 1.26.1 running on Duet 0.6
Used output buffers: 1 of 16 (16 max)
=== System ===
Static ram: 44212
Dynamic ram: 42732 of which 3168 recycled
Stack ram used: 1080 current, 2564 maximum
Never used ram: 5628
=== Platform ===
Last reset 00:09:12 ago, cause: power up
Last software reset at 2020-10-22 23:03, reason: User, spinning module GCodes, available RAM 5004 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0xffffffff
Error status: 4
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 12.3ms, max retries 0
MCU temperature: min 10.0, current 26.8, max 27.3
Date/time: 2020-10-22 23:23:27
Slowest loop: 69.21ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 100, MinFreeDm: 100, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 1 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 ===
Free connections: 15 of 16
Free transactions: 23 of 24
Locked: 0, state: 4, listening: 20071bf4, 0, 20071bd8

Phaedrux

So the IR probe is connected to the duex4 and works? But the stepper doesn't?

sylvaindc

@Phaedrux said in Duex4 v0.2a (with Duet 0.6):

So the IR probe is connected to the duex4 and works? But the stepper doesn't?

Yea, but that is not so strange given that AD12 just physically loops to the J16 connector.

I'm starting to think I need to tell the board or the firmware that the Duex4 is connected

dc42

There have been no intentional changes to the DueX4 support, but it hasn't been tested for many versions. Have you tried the other motor outputs on the DueX4?

RRF does not detect the DueX4 the way that it detects a DueX5, so you will not see it reported in the M115 response.

sylvaindc

@dc42 Thanks for your response, let me try the other ports