SOLVED - Cable
The cable used was a traditional RJ11 phone extension cable. The ends are not the same, which created the confusion of the wires being associated with L & H.
I've switched to a twisted pair cable and all is working as designed.
Thanks for the input and time, as I worked through this speed-bump.
For reference see the pics and notice the flipping of the cable.
Posts made by tmreith
-
RE: 1LC CAN-FD connection to 6HC - Reversed???
-
RE: 1LC CAN-FD connection to 6HC - Reversed???
@dc42 Yes, the cable is a standard RJ11 phone cable - flat RED/GREEN inner 2 with YELLOW/BLACK outer. Also purchased from Filastruder.
-
RE: 1LC CAN-FD connection to 6HC - Reversed???
@droftarts The 1LC is version 1.3 and the 6HC is version 1.02. Both components were purchased through Filastruder in the USA.
-
1LC CAN-FD connection to 6HC - Reversed???
I have spent two days trying to understand why I had to reverse the wiring of the CAN-FD cable from the 6HC board to the 1LC board. If I follow the posted instructions the 1LC does not connect. Has anyone else seen this behavior?
The 1LC has been soldered to enable the termination 120R circuit. I am currently connected via CAN1_H to CAN_L and CAN1_L to CAN_H - see pics below.
Any comments or suggestions are welcomed.
The following post mentions a similar behavior:
https://forum.duet3d.com/topic/23871/wiring-diagram-between-duet3-6hc-and-1lcSee attached images below.
-
RE: Gcode "Look Ahead" Limit for Variable Setting
@chrishamm SOLVED - Thanks
M400 did the trick. -
Gcode "Look Ahead" Limit for Variable Setting
Is there some form of "look ahead" with the Duet control interpreting the Gcode? I am using global variables to set values based on conditional events that occur in specific points within the gcode. For example after a specific layer is completed and a desired temperature is set.
However, I notice the variable is set before the linear motion has occurred. Is there a way to wait until a linear motion has completed before setting a variable?
For example - HAAS machine tools use G103 - see below
-
RE: Custom Status Response via MCODE?
@T3P3Tony Works great! Thanks for the suggestions.
-
RE: Custom Status Response via MCODE?
@dc42 Thanks David.
Would the global variable value be visible within the JSON response? -
Custom Status Response via MCODE?
Hello,
The machine status returns the following based on the current machine state.status: I=idle, P=printing from SD card, S=stopped (i.e. needs a reset), C=running config file (i.e starting up), A=paused, D=pausing, R=resuming from a pause, B=busy (e.g. running a macro), F=performing firmware update
Is there a method to provide a custom state based on a MCODE? or can we change the status to a different state using a MCODE?
I am pulling data from a JSON request and when the code steps through subsequent MACROS, I'd like to be able to identify based on the MACRO running. The "P" status is too generic to know what is running.
-
RE: File Updates lost after Reboot
@chrishamm Yes, microSD card damaged and was in forced ready-only mode. I replaced with a new microSD A1 and back to normal. Thanks!
-
File Updates lost after Reboot
Hello,
After updating system files and or adding new gcode files, the system recognizes the changes or additions. However, after rebooting the system, the file system reverts to an older date. Note, I have 4 machines with the identical setup, but I am only seeing this behavior on the one machine. Possible file corruption???Currently running:
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.3.0
Firmware: RepRapFirmware for Duet 3 MB6HC 3.3 (2021-06-15) -
RE: Layer tracking with variable layer heights
@tmreith
Works on a Duet 2 Wifi running 3.4.1.Added the following to the last line in gcode file.
; num_layers: 64
-
RE: Layer tracking with variable layer heights
@phaedrux
I added the following to the end of the gcode file, and there was no effect.; num_layers=64
I looked at the source code for FileInfoParser.cpp and it definitely has a routine to parse "num_layers" keyword. I am not sure why the DWC doesn't seem to see the value.
I have another machine running 3.4.1, so I'll give it a try on that machine over the weekend.
-
RE: Layer tracking with variable layer heights
@phaedrux
unfortunately not. The machines are validated to 3.3 and would require a re-validation effort if I updated the firmware.Is there a layer count keyword that is still being used in the g-code? I can insert what ever DWC needs to establish a value vs trying to calculate from a Z height and the layer height value.
-
RE: Layer tracking with variable layer heights
@phaedrux
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.3.0
Firmware: RepRapFirmware for Duet 3 MB6HC 3.3 (2021-06-15)
Duet Web Control 3.3.0I thought there was a keyword like "layer count" or "num_layers" that was being read in past before DWC would try to calculate based on a layer_height value and the max Z value.
The mixed layer heights are definitely messing with the layer calculation.
I have full control over the gcode, so I can add in the required commented value to drive the DWC.
-
RE: Layer tracking with variable layer heights
R = (1-4) : 4 layers - raft mix
A = (5-19) : 15 layers at 0.100mm
B= (20-76) : 57 layers at 0.150mmTotal 76 layers
I have uploaded a sample file for the above cube with variable layer heights to show the effect.
-
RE: Layer tracking with variable layer heights
@tmreith Note: the first 15 layers are at 0.100mm in height, the remaining layers are at 0.150mm. The error in the total amount of layers is due to a calculation within DWC looking possibly at the total height and dividing by 0.150mm which is giving the error of the missing 5 layers.
15 layers @ 0.100mm vs 10 layers @0.150mm
-
RE: Layer tracking with variable layer heights
@norder thanks for the reference. My support layers are in-sync with the print layers.
The first 15 layers post raft, are at 0.100mm and the remaining layers are at 0.150mm
64 is the correct of amount of total layers. It appears to be the 59 that is under calculating layers. The target amount of layers is incorrect.
-
Layer tracking with variable layer heights
Within my gcode, I have the following per layer. The current layer and the current Z value.
; layer 1, Z = 0.499 ... ; layer 64, Z = 9.249
However DWC seems to be calculating layers from a perceived Z height and layer heights.
My code mixes layer heights at 0.100mm to 0.150mm depending on the feature.
What is the best way to instruct DWC to report the correct amount of layers?
It is currently reporting 64 of 59 layers at the end of the print.