Posts made by JA

@chrishamm Hello, I have compiled a new version of DWC with the changes you made and now it doesn't get stuck on "connecting", but there is still a problem, it doesnt say anything on the console.

It doesn't send any warning message and the faulty JSON file doesn't get fixed.
So now the JSON file doesn't work, for example, if i disable the appearance "dark theme" it changes to white but after recharging the page it continues to be in dark, if i start a plugin it works but when the page is recharged it isn't started.

I see that you put this line to send a warning to the console:
" console.warn('Failed to load settings: ' + e); "
but it doesn't do anything, i dont see any message in the console.

@chrishamm Thank you , it's by no mean a frequent problem, its the first time it hapened.

@chrishamm said in MB6HC+SBC inaccessible after emergency stop:

consider saving the settings in the localStorage object

You mean toggling this right??

,
,

did you look at this??

@ja said in MB6HC+SBC inaccessible after emergency stop:

While investigating this error I've found that there is a JSON file that i suspect it's named incorrectly.
The name in the folder "/opt/dsf/sd/sys" -> "dwc2settings.json"
The name in the code of DWC -> legacyDwcSettingsFile: '0:/sys/dwc2-settings.json',

For now i've fixed the problem but what should i do to make sure it doesn't keep happening??

We have a machine that has been working fine for months, it's a custom IDEX machine with the MB6HC in SBC mode (with a raspberry 4) running RRF 3.3. We have modified and compiled our own RRF and DWC versions but i don't think it has any relation with the problem. I've tried the same thing in RRF 3.4.0rc2 (SBC mode) and it does the same.

Yesterday while it was printing a file we turned off the machine (equivalent to unpluging the printer) without pausing or stopping the job. We have done this hundreds of times, but yesterday after this event there was no way to reconect to the machine, look at this screenshot:

We could not connect to the machine, you can see the "connecting..." message.
But the tool names were visible, even the temperatures were working fine (in this screenshot the sensors are disconnected ), the input voltage was also visible. So DWC was working, the problem being that we couldn't click anywhere.

After investigating the JSON files in the directory "/opt/dsf" I've found that the file "dwc-settings.json" is not a valid JSON.
After deleting this JSON and replacing it with a back up, everything has worked perfectly.

The bad JSON file ends exactly like this:
.....,"extruderFeedrates":[60,30,15,5,1],"temperatures":{"tool":{"active"
Here you have the file to look at it if you want (I've changed the extension from .json to ".txt") dwc-settings_WRONG.txt
,
,
,
,
While investigating this error I've found that there is a JSON file that i suspect it's named incorrectly.

The name in the folder "/opt/dsf/sd/sys" -> "dwc2settings.json"
The name in the code of DWC -> legacyDwcSettingsFile: '0:/sys/dwc2-settings.json',

I don't know if this naming mishap would affect our issue but i think it should be corrected.

@t3p3tony Thank you for changing to usb C

@maracmb said in Duet 6HC + 3HC + 3HC one expansion does not connect:

cabels are well made.

Since the board doesn't come with CAN cables, you had to make them. It could be that your cables are not well made.

When i had my cables wrong i saw this behaviour, the second board on the CAN network worked but the first one didn't.
The CAN cables were crossing the signal, and because the second device on the network has passed from 2 cables, it had the signal crossed twice, this is the same as having the cables straight, so the second device on the network worked fine.

It doesn't mather the CAN address you asing to that board, if you use the correct adderss when sending comands.

@maracmb said in Duet 6HC + 3HC + 3HC one expansion does not connect:

it only connects to second of my two 3HC expansion boards. The first one in row does not connect but second one does

I have the same board configuration (MB6HC + EXP3HC + EXP3HC). I had a problem where address number 1 never worked but address number 2 worked fine.

It was a problem with my CAN cables, you should try changing the boar order, put your first expansion in the second position to check if the board actually works.

@maracmb said in Duet 6HC + 3HC + 3HC one expansion does not connect:

Flashed the bootloader on the one that works .......The second one ........ No diagnostic indication

I think that even if your CAN cables are wrong the diagnostic led should blink.
Try uploading a new bootloader after changing the board order.

@cosmowave said in Using variables with M584 doesn't work:

Then you can write the commands in separate lines! Or not?

No.

@owend said in Using variables with M584 doesn't work:

I don't have multiple extruders

The problem is the way multiple extruders are configured, i think DSF doesn't understand well the "M92 E--:-- " way of configuring them.

I have the same issue and it's prior to variables, object model nodes also don't work
In standalone mode works as expected but not in SBC mode.

Example:

I think all you need is M99
Here you have a macro using variables, if someone doesn't want variables (to use with older firmware) just replace the values.

To download: Cool_Bed.g

;[Macro Cool_Bed.g]		; Needs RRF3.3 or later because uses variables

; Change these variables to suit your printer
var BedFan = 9				; Fan number
var ThresholdTemp = 50			; ºC
var CheckEvery = 1			; Seconds


if heat.heaters[0].current > {var.ThresholdTemp}
	M108						; Cancel Heating (just in case), Breaks out of an M109 or M190
	M140 S0						; Turn off bed heater (*)
	M106 P{var.BedFan} S1.0				; Turn on BedFan
	while  true
		G4 S{var.CheckEvery} 			; Wait 1 sec, to check temperature every second
		if heat.heaters[0].current <= {var.ThresholdTemp}
  			M106 P{var.BedFan} S0.0		; Turn off BedFan
   			M99				; Return from Macro/Subprogram
		;END if
	;END while
;END if

"*" in line 11, is there anything analogous to M568 A0 for tools but for the bed??

"Do I need to re-wire it?" Yes.

Maybe it's time they change the included cable because "Duet 3 Mini 5+ " also needs a "4-pin <-> 5-pin" cable

@fcwilt said in EXP3HC homing issues, sometimes the axis doesn't stop:

Hi,

Can you update the expansion boards to 3.1.1?

Frederick

My understanding was that there is no 3.1.1 for the expansions

Thank you @dc42,
Now works as is supposed to with

• MB6HC firmware version "3.2-beta" "2020-07-15b1"
• EXP3HC firmware 3.1.0

But seeing that this fix is implemented since 15 of july, almost a month ago, that the latest release of RRF 3 was on the 19 of May and that there have been a bunch of commits since then raises a new cuestion:

Is RRF3.2 close?? if not have you considered releasing a intermediate point like 3.1.2 for example??

Could you comment something about it ??

Hi, I am trying to configure a duet3 machine in standalone mode, my setup includes 2 expansion boards: MB6HC + EXP3HC + EXP3HC .
I am runing RRF3.1.1 and on the expansion boards 3.1.0

The machine works well, the problem only comes while homing
( i've found out later the problem ocurres while using the comand "G1 H1 ... " )

Since i could not find the issue i started with a simplified sistem, using the same electronics i configured a IDEX machine with 3 of the axes on the first expansion board.

After a bunch of tests this is what i found looking at the U axis, witch is on the first expansion board

" G1 H1 U-100 F2000" works ok.
" G1 H1 U-100 F3500 " does NOT work.

1. If i hit the endstop while the axis is moving it doesn't stop.
2. if i maintain the endstop with my hand and then send the G1 H1 comand, it works ok.

If i use the "homeu.g" file:

G91               	; relative positioning
G1 H2 Z5 	F2000   ; lift Z relative to current position

G1 H1 U-100	F3500 	; move quickly to U axis endstop and stop there (first pass)
G1 H2 U5 	F360 	; go back a few mm
G1 H1 U-10 	F360  	; move slowly to U axis endstop once more (second pass)

G1 H2 Z-5 	F2000   ; lower Z again
G90               	; absolute positioning

If the speed of the first "G1 H1" comand is inside the "bad speed" range , it doesn't stop when the endstop is hited, it doesn't execute "G1 H2" and ejecutes the next "G1 H1", since this is outside of the "bad speed" range the second one works ok.

This happens in a range off speeds, and if i change the U-100 to U-50 also changes the range. Seeing that i tried changing the acceleration of the axis, and this also changes the range off speeds.

• If i configure a acceleration of "M201 U500"
  G1 H1 U-100 -> [F3492 - F3512] Does not work "bad speed"
  G1 H1 U-50 -> [F1992 - F2005] "bad speed"
  G1 H1 U-20 -> [F1092 - F1201] "bad speed"

• "M201 U400":
  G1 H1 U-100 -> [F5053 - F5103] "bad speed"
  G1 H1 U-50 -> [F3292 - F3333] "bad speed"
  G1 H1 U-20 -> [F1675 - F1700] "bad speed"

This is completlty repeatable, every time i send a "G1 H1 with the right acceleration, distance , speed combination the endstop doesn't stop the axis.

The only posibility i see is that RRF 3.1.1 or expansion firmware 3.1.0 has some incompatibility.

( i have also tried the 3.1.0+ BETA version dc42 put here: https://forum.duet3d.com/topic/17285/hiccups-on-3hc-expansion-board/24)

Just in case, here it is my simplified versions config.g