@T3P3Tony V4 says "Filament Length:" at the bottom. V5 says "Material Length:" at the bottom
![](/assets/uploads/system/avatar-default.png?v=1521803371351)
GeneRisi
@GeneRisi
Former IBM engineer (35 years), retired and doing volunteer work and playing. I am into Amateur Radio and 3d printing.
Best posts made by GeneRisi
-
RE: Simplify3d and Filament Timings
-
RE: Dumbfounded ! Firmware bug in 3.4 beta 6?
@dc42 I found the problem.
When tool T1 was being returned, the Y "parking" coordinate was off by 1 mm. The tool parking location didn't budge but the firmware thought that the tool location was 1mm beyond where it actually was. The machine is a corexy (E3D), so even though only the Y coordinate was off, I suspect it affected both the x and y location from the the firmware's perspective.
-
RE: Best IDEX nozzle wipe mechanisms?
@oliof I have the pebble wiper design installed and it works very well once you have it set up properly. Does it do more than any other purge and wipe tool? Maybe not.
I have an e3d tool changer with a couple of home made Orbiter / v6 hot end tools and a Hemera. The version I use is on a linear rail so that it can accommodate different size tools.
-
RE: Extruder parameter format question
I just created SeqTest.g which contains this:
M584 X0
M350 X16
M584 Y1
M350 Y16It runs fine. Did it do the right thing? I don't know yet.
-
RE: Accelerometer Usage
FWIW, twisted pair wiring is designed to use both wires in the pair. The signals we are carryng are not differential, so try connecting the "other" wire in the pair to ground at both ends of the wiring. You might find that it cleans up the signal quite a bit. I am using CAT5 unshielded cable for both the accelerometer and the Paneldue serial link without any issues (as far as I can tell)
-
RE: PanelDue 3.4.0-pre2 released
@mfs12 Has anyone mentioned a problem on the 5i where using the extrusion control (with tool 1) the extrusion length and speed do not remain highlighted after being selected? What would I provide for you to check this out if it is a new issue? I am using 3.4.0 b4.
On another note, could DWC report which version of firmware the Paneldue is running? It would be nice to have.
-
RE: All of a sudden, my corexy steppers aren't working
@generisi I found errors that make me wonder how it ever worked... It is fixed now - thank you!
-
RE: Dumbfounded ! Firmware bug in 3.4 beta 6?
@t3p3tony Here is a simple print file that demonstrates T1,T0,T1,T0:
G90 M83 M117 Preheat & Level G28 G10 P0 S242 R200; set extruder 0 active and standby temps G10 P1 S242 R200; set extruder 1 active and standby temps M190 S85 ; wait for bed temperature ;mesh gcode G29 Q0 T1 G1 E-0.8000 F3000 ; feature skirt ; tool H0.200 W0.400 G1 Z0.200 F360 G1 X145.575 Y112.700 F9000 G1 E0.8000 F3000 G1 X139.600 Y106.725 E0.2810 F90 G1 X137.300 Y104.425 E0.1082 G1 X137.300 Y95.575 E0.2944 G1 X145.575 Y87.300 E0.3892 G1 X154.425 Y87.300 E0.2944 G1 X156.725 Y89.600 E0.1082 G1 X162.700 Y95.575 E0.2810 G1 X162.700 Y104.425 E0.2944 G1 X154.425 Y112.700 E0.3892 G1 X145.575 Y112.700 E0.2944 G1 E-0.8000 F3000 ; feature cross - external single extrusion ; tool H0.200 W0.400 G1 Z0.400 F360 G1 X147.738 Y100.000 F9000 G1 Z0.200 F360 G1 E0.8000 F3000 G1 X149.641 Y100.000 E0.0633 F45 G1 X150.000 Y99.641 F9000 G1 X150.000 Y97.738 E0.0633 F45 G1 E-0.8000 F3000 G1 Z0.400 F360 G1 X152.262 Y100.000 F9000 G1 Z0.200 F360 G1 E0.8000 F3000 G1 X150.279 Y100.000 E0.0659 F45 G1 X150.200 Y100.000 E0.0026 ; tool H0.200 W0.416 G1 X150.117 Y100.000 E0.0029 ; tool H0.200 W0.499 G1 X150.000 Y100.000 E0.0049 G1 X150.000 Y100.117 E0.0049 ; tool H0.200 W0.416 G1 X150.000 Y100.200 E0.0029 ; tool H0.200 W0.400 G1 X150.000 Y100.279 E0.0026 G1 X150.000 Y102.262 E0.0659 G1 E-0.8000 F3000 ; layer end T0; G1 E-0.8000 F3000 ; feature skirt ; tool H0.200 W0.400 G1 Z0.200 F360 G1 X145.575 Y112.700 F9000 G1 E0.8000 F3000 G1 X139.600 Y106.725 E0.2810 F90 G1 X137.300 Y104.425 E0.1082 G1 X137.300 Y95.575 E0.2944 G1 X145.575 Y87.300 E0.3892 G1 X154.425 Y87.300 E0.2944 G1 X156.725 Y89.600 E0.1082 G1 X162.700 Y95.575 E0.2810 G1 X162.700 Y104.425 E0.2944 G1 X154.425 Y112.700 E0.3892 G1 X145.575 Y112.700 E0.2944 G1 E-0.8000 F3000 ; feature cross - external single extrusion ; tool H0.200 W0.400 G1 Z0.400 F360 G1 X147.738 Y100.000 F9000 G1 Z0.200 F360 G1 E0.8000 F3000 G1 X149.641 Y100.000 E0.0633 F45 G1 X150.000 Y99.641 F9000 G1 X150.000 Y97.738 E0.0633 F45 G1 E-0.8000 F3000 G1 Z0.400 F360 G1 X152.262 Y100.000 F9000 G1 Z0.200 F360 G1 E0.8000 F3000 G1 X150.279 Y100.000 E0.0659 F45 G1 X150.200 Y100.000 E0.0026 ; tool H0.200 W0.416 G1 X150.117 Y100.000 E0.0029 ; tool H0.200 W0.499 G1 X150.000 Y100.000 E0.0049 G1 X150.000 Y100.117 E0.0049 ; tool H0.200 W0.416 G1 X150.000 Y100.200 E0.0029 ; tool H0.200 W0.400 G1 X150.000 Y100.279 E0.0026 G1 X150.000 Y102.262 E0.0659 G1 E-0.8000 F3000 ; layer end ; pass 2 T1 G1 E-0.8000 F3000 ; feature skirt ; tool H0.200 W0.400 G1 Z0.200 F360 G1 X145.575 Y112.700 F9000 G1 E0.8000 F3000 G1 X139.600 Y106.725 E0.2810 F90 G1 X137.300 Y104.425 E0.1082 G1 X137.300 Y95.575 E0.2944 G1 X145.575 Y87.300 E0.3892 G1 X154.425 Y87.300 E0.2944 G1 X156.725 Y89.600 E0.1082 G1 X162.700 Y95.575 E0.2810 G1 X162.700 Y104.425 E0.2944 G1 X154.425 Y112.700 E0.3892 G1 X145.575 Y112.700 E0.2944 G1 E-0.8000 F3000 ; feature cross - external single extrusion ; tool H0.200 W0.400 G1 Z0.400 F360 G1 X147.738 Y100.000 F9000 G1 Z0.200 F360 G1 E0.8000 F3000 G1 X149.641 Y100.000 E0.0633 F45 G1 X150.000 Y99.641 F9000 G1 X150.000 Y97.738 E0.0633 F45 G1 E-0.8000 F3000 G1 Z0.400 F360 G1 X152.262 Y100.000 F9000 G1 Z0.200 F360 G1 E0.8000 F3000 G1 X150.279 Y100.000 E0.0659 F45 G1 X150.200 Y100.000 E0.0026 ; tool H0.200 W0.416 G1 X150.117 Y100.000 E0.0029 ; tool H0.200 W0.499 G1 X150.000 Y100.000 E0.0049 G1 X150.000 Y100.117 E0.0049 ; tool H0.200 W0.416 G1 X150.000 Y100.200 E0.0029 ; tool H0.200 W0.400 G1 X150.000 Y100.279 E0.0026 G1 X150.000 Y102.262 E0.0659 G1 E-0.8000 F3000 ; layer end T0; G1 E-0.8000 F3000 ; feature skirt ; tool H0.200 W0.400 G1 Z0.200 F360 G1 X145.575 Y112.700 F9000 G1 E0.8000 F3000 G1 X139.600 Y106.725 E0.2810 F90 G1 X137.300 Y104.425 E0.1082 G1 X137.300 Y95.575 E0.2944 G1 X145.575 Y87.300 E0.3892 G1 X154.425 Y87.300 E0.2944 G1 X156.725 Y89.600 E0.1082 G1 X162.700 Y95.575 E0.2810 G1 X162.700 Y104.425 E0.2944 G1 X154.425 Y112.700 E0.3892 G1 X145.575 Y112.700 E0.2944 G1 E-0.8000 F3000 ; feature cross - external single extrusion ; tool H0.200 W0.400 G1 Z0.400 F360 G1 X147.738 Y100.000 F9000 G1 Z0.200 F360 G1 E0.8000 F3000 G1 X149.641 Y100.000 E0.0633 F45 G1 X150.000 Y99.641 F9000 G1 X150.000 Y97.738 E0.0633 F45 G1 E-0.8000 F3000 G1 Z0.400 F360 G1 X152.262 Y100.000 F9000 G1 Z0.200 F360 G1 E0.8000 F3000 G1 X150.279 Y100.000 E0.0659 F45 G1 X150.200 Y100.000 E0.0026 ; tool H0.200 W0.416 G1 X150.117 Y100.000 E0.0029 ; tool H0.200 W0.499 G1 X150.000 Y100.000 E0.0049 G1 X150.000 Y100.117 E0.0049 ; tool H0.200 W0.416 G1 X150.000 Y100.200 E0.0029 ; tool H0.200 W0.400 G1 X150.000 Y100.279 E0.0026 G1 X150.000 Y102.262 E0.0659 G1 E-0.8000 F3000 ; layer end M117 Print Complete ! T-1 M999
-
[Feature request] add sort options to file list
@mfs12 It would be great to have an option in setup where the file name sorting could be specified. I would like "sort by date, most recent first" because I do a lot of test runs and find myself wanting to use the web interface to start the job because I can have it sort the files names by date. Thanks for considering my suggestion!
-
RE: different milling results dispite same G10 Offset
@cmp I wish I had better insight to help you out... what firmware version are you running? If the experiments below don't provide insight, would you please post the Tool1 and Tool4 pre,.g , post.g and free.g macros?
Please try typing M999 (this will force the firmware to do a reset) just before you start your print. Make sure that you don't execute any additional gcode before starting your print. See if running the normal "print, then mill" sequence a couple of times give the same offsets or different offsets.
Another variation of this experiment is to home the machine, then pick up the milling tool, then put it back, then pick up the print tool, then print the object, then return the print tool, pick up the milling tool and then mill the object. Try this sequence at least twice to see if the offsets are the same or different.
One more variation: Print the object, then pick up the milling tool but don't use it, then put the milling tool back, then pick up the printing tool and add layers on top. Do the additional layers line up with the original layers?
Latest posts made by GeneRisi
-
RE: Building 3.5(.2) and CoreTypes.h not found
@chrishamm I discovered the solution. After loading all of the projects, then do a full clean and then quit Eclipse. Restart Eclipse and now the board build options should be available under the Hammer icon.
-
RE: Building 3.5(.2) and CoreTypes.h not found
I was forced to re-install Eclipse. After loading the individual projects, my screen looks like this. I no longer have the Hammer drop down menu. What am I missing?
Gene
-
RE: Building 3.5(.2) and CoreTypes.h not found
@chrishamm Somehow I got the right config file when building 3.5.1 but don't have it for 3.5.2. What is it called? I am not finding it with a quick scan.
Thanks, Chris!
-
RE: Building 3.5(.2) and CoreTypes.h not found
@chrishamm I still get the missing include file error even when using SAME4E_RTOS for the CANlib build (which I guess makes sense). Do you know where the include file should be located?
Gere
11:04:37 **** Incremental Build of configuration SAM4E_RTOS for project CANlib-3.5-dev **** make all Building file: ../src/CanMessageBuffer.cpp Invoking: Cross G++ Compiler arm-none-eabi-g++ -std=gnu++17 -D__SAM4E8E__ -DRTOS -Os -Wall -c -mcpu=cortex-m4 -mthumb -fno-math-errno -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mfp16-format=ieee -ffunction-sections -fdata-sections -fno-threadsafe-statics -fno-rtti -fno-exceptions -nostdlib -Wundef -Wdouble-promotion -Werror=return-type -fsingle-precision-constant "-Wa,-ahl=CanMessageBuffer.s" -MMD -MP -MF"src/CanMessageBuffer.d" -MT"src/CanMessageBuffer.o" -o "src/CanMessageBuffer.o" "../src/CanMessageBuffer.cpp" In file included from ../src/CanMessageBuffer.h:15, from ../src/CanMessageBuffer.cpp:8: ../src/CanId.h:12:10: fatal error: CoreTypes.h: No such file or directory 12 | #include <CoreTypes.h> // for CanAddress | ^~~~~~~~~~~~~ compilation terminated. make: *** [src/CanMessageBuffer.o] Error 1 "make all" terminated with exit code 2. Build might be incomplete. 11:04:37 Build Failed. 2 errors, 0 warnings. (took 141ms)
-
Building 3.5(.2) and CoreTypes.h not found
For the default selection of "SAME70_RTOS" I am getting an error message
09:58:25 **** Build of configuration SAME70_RTOS for project CANlib-3.5-dev **** make all Building file: ../src/CanMessageBuffer.cpp Invoking: Cross G++ Compiler arm-none-eabi-g++ -std=gnu++17 -D__SAME70Q20B__ -DRTOS -O2 -Wall -c -mcpu=cortex-m7 -mthumb -fno-math-errno -mfpu=fpv5-d16 -mfloat-abi=hard -mfp16-format=ieee -mno-unaligned-access -ffunction-sections -fdata-sections -fno-threadsafe-statics -fno-rtti -fno-exceptions -nostdlib -Wundef -Wdouble-promotion -Werror=return-type -fsingle-precision-constant "-Wa,-ahl=CanMessageBuffer.s" -MMD -MP -MF"src/CanMessageBuffer.d" -MT"src/CanMessageBuffer.o" -o "src/CanMessageBuffer.o" "../src/CanMessageBuffer.cpp" In file included from ../src/CanMessageBuffer.h:15, from ../src/CanMessageBuffer.cpp:8: ../src/CanId.h:12:10: fatal error: CoreTypes.h: No such file or directory 12 | #include <CoreTypes.h> // for CanAddress | ^~~~~~~~~~~~~ compilation terminated. make: *** [src/CanMessageBuffer.o] Error 1 "make all" terminated with exit code 2. Build might be incomplete. 09:58:26 Build Failed. 2 errors, 0 warnings. (took 141ms)
I am building for a Duet2 system so I don't know if I even need CANlib.
How do I fix the error?
Thanks!Gene
-
RE: Unable to configure MQTT when active on an interface
@droftarts Hi Ian, the daemon.g file was just a work around because initializing MQTT in config.g doesn't work in the current release. The patch mentioned above works for my and @rechrtb systems and with the patch, it isn't necessary to use the daemon.g approach.
Gene
-
RE: Unable to configure MQTT when active on an interface
@rechrtb First, I will try adding the delay after rearranging the gcode such that configuration happens first. I'll post what happens here. Then I will add the patch and try it out.
Gene- Adding delay between
M586.4 C"ToolChanger" ; Set client ID M586.4 U"TC" K"xxxxxxx" ; Set authentication credentials M586.4 S"printing3d" O2 ; Subscribe to topic M586 P4 R1883 H10.0.0.103 T0 S1
and
M118 P6 S"MQTT message from ToolChanger" T"printing3d"
works !
And using the new MqttClient.cpp also works !
Thank you!
Gene
-
RE: Unable to configure MQTT when active on an interface
@rechrtb I figured it out. The port has to be activated first (using M586) and then the initialization (M586.4) steps should occur, and then a message (M118) can be sent.
-
RE: Unable to configure MQTT when active on an interface
@rechrtb Now, I get this in my trace file:
2024-05-10 21:55:14 [debug] starting mqtt.g ... 2024-05-10 21:55:14 [debug] Configuring MQTT; responder state: 0 2024-05-10 21:55:14 [debug] Configuring MQTT; responder state: 0 2024-05-10 21:55:14 [debug] Configuring MQTT; responder state: 0 2024-05-10 21:55:14 [debug] MQTT is enabled on port 1884 2024-05-10 21:55:14 [debug] Failed to publish MQTT message, client not active 2024-05-10 21:55:14 [debug] Starting MQTT on ToolChanger 2024-05-10 21:55:14 [debug] ... ending mqtt.g
from this gcode:
M929 P"eventlog.txt" S3 ; start logging warnings to file eventlog.txt ; M111 P1 S1 ; traces turned on M111 P2 S1 ; M118 P1 S"starting mqtt.g ..." ; M586.4 C"ToolChanger" ; Set client ID M586.4 U"TC" K"wHg@tc" ; Set authentication credentials M586.4 S"printing3d" O2 ; Subscribe to topic ; M586 P4 R1884 H10.0.0.103 S1 ; this should initialize the responder ; M118 P6 S"Starting MQTT on ToolChanger" T"printing3d" ; Publish message (See M118 for more details) ; M118 P1 S"... ending mqtt.g" ; M111 P1 S0 ; traces turned off M111 P2 S0 ; M929 S0 ; tracing truned off ; ; finis
What does "client not active" mean in this case? Is "client" the Duet3d firmware?
Gene
-
RE: Unable to configure MQTT when active on an interface
@rechrtb Thanks for your help!
I think a small change to your config.g suggestion works slightly better. If instead, I use
if !exists(global.mqttInited) global mqttInited = false
then config.g can be run without a machine reset preceding it (which is possible if config.g is edited)