Posts made by _santiserrano

@dc42 Thanks! Love my duet, you make a great job. Continue like this, I will continue supporting you buying your products. When will the DUET 3 be available?

@phaedrux said in Can't upload gcode files - Duet Web Control:

together

Ok, so you think it is for that reason? The printer is a bit far from the modem, yes. I will try relocating it, thanks for all. But it is normal that all works good but the files upload only? Thanks

Hi, thanks! I will read the troubleshooting guide. The M122 command gives me the following results:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6J9F4-3SJ6N-9LZRY
Used output buffers: 3 of 20 (9 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98624 of which 0 recycled
Exception stack ram used: 280
Never used ram: 6644
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3788) IDLE(ready,200)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:48:52 ago, cause: software
Last software reset at 2019-02-07 20:46, reason: User, spinning module GCodes, available RAM 6500 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 10.4ms, max retries 0
MCU temperature: min 37.1, current 38.3, max 38.5
Supply voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
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
Date/time: 2019-02-07 21:35:36
Cache data hit count 4294967295
Slowest loop: 20.37ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== 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
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle 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: 39.10ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(1) 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.22
  WiFi MAC address 60:01:94:34:37:ff
  WiFi Vcc 3.37, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 26136
  WiFi IP address 192.168.0.104
  WiFi signal strength -70dBm, reconnections 0, sleep mode modem
  Socket states: 0 2 0 0 0 0 0 0

Hi, when I try to upload gcode files it gives me an error, the speed is reduced to about 7.4 KiB/s and it gives me an error message. I don't think it is the wifi connection nor the SD card. Any idea? It is the first time using this DUET wifi board, I am using 2.02 release with duet web control 1.22.6 and duet wifi server 1.22. I can't control the machine via the DWC but the only thing I can't do is upload gcode files. Any help? Thanks in advance.

I think it is all explained in my comments. The settings on the configurator are "switch" and trigger value 1000. And the two cables connected to the Z probe header, on Z PROBE IN and GND pins. And finally, you will have to add "I1" after the M558 command in the config.g file.

@dc42 trigger threshold is the same as trigger value? Or what is it?

I solved it! I have to add I1 after the M558 in the config.g file. Thanks for the great documentation, I leave this thread here for helping people solve this. Bye!

I forgot to say that I am using the "switch" option in the probe type of the configurator tool, and the trigger value in 1000.

Well, I changed the two cables from the E0 endstop to the Z probe header (Z PROBE IN and GND) and now the static test works, when I place my finger below the sensor it goes from 1000 to 0, but when I try to home all the axes the Z axis will not do it, and the DWC gives me a message saying the Z endstop is triggered. I try inverting the position of the two cables but the problem continues. Any idea? Thanks

If anyone needs me to measure some voltage please let me know and explain me how to do it because I am not so experienced with electronics. Here I leave an image of the board between the sensor and the Duet also.

Hi, does anyone installed the EZABL Z-probe with success? I think it is a capacitive sensor, sold by TH3D. I've been using it with my CR-10 S4 but I can't configure it right with the Duet WiFi board, I don't know what type of probe I have to select in the configurator tool nor if I need to connect it to the Z probe heater or to the E0 endstop. If anyone can help me I would really appreciate it, I saw some threads about this but none of them have a solution. I have the direct wire version of the sensor and here I leave some information distributed only to customers by the manufacturer:
Wiring the sensor Connect power to the EZABL Module ○ If you are using the direct wire version then you will need to connect the module to the 12V OR 24V power that is on your printer. The top pin is positive (+) and bottom pin is negative (-). We recommend connecting direct to the power supply. Contact support with pictures if you are unsure if you wired it correctly. Click here for PSU wiring info. POLARITY MATTERS. BOARD WILL SHORT IF WIRED BACKWARDS ON V1 and V2 BOARDS. V3 BOARDS HAVE REVERSE VOLTAGE PROTECTION STANDARD. WIRING TO AC WILL KILL ALL KITS ○ If you are using the EZ-Connect version then simply plug in the power adapter and the other end into the DC jack on the EZABL module Connect your Z endstop to the EZABL Module ○ If you are using the direct wire version then cut the leads going to your current Z endstop switch and connect them to the EZABL port labeled ZMIN ○ If you have the EZ-Connect version then unplug the 2/3 pin connector from your Z endstop and plug it into the EZABL port labeled ZMIN – DO NOT USE JUMPER WIRES FOR THIS AS THEY DO NOT MAKE PROPER CONNECTION AND CAN DAMAGE OUR BOARD. If you printer has 3 wires going to the Z endstop connection, please contact our support BEFORE connecting. You can contact us at Support@TH3DStudio.com. For the Geeetech A10 with a 3 wire endstop see page 30 for wiring the Z endstop. Test the sensor for detection Power on your printer and verify that the sensor is working by touching the sensor with your finger. The LED light on the Sensor AND the module should light up. If they do not light up adjust the screw clockwise on the sensor (top on EZABL, white on the side of the EZABL Mini) until it lights up when you touch it. V1.8.1 – 12/18/2018 Need help? Email: Support@TH3DStudio.com TH3D EZABL Installation Guide - Copyright 2018 TH3D Studio LLC – ALL RIGHTS RESERVED 8 Firmware Setup – CLOSE ALL SLICERS BEFORE FLASHING If you have the CR-10 (all sizes), CR-10S (all sizes), Tornado, TAZ5, Anet (A2, A6, A8, E10 or E12), Ender 2, Ender 3, Wanhao (i3, i3 Mini, D6), Geeetech A10 we have already done all the firmware work for you. The pre-configured firmware is on our website here: https://www.th3dstudio.com/knowledge-base/th3d-unified-firmware/ If you have a printer that needs a bootloader this must be flashed. See the Unified Firmware page for details on this. Select Arduino as ISP for the programmer. In the Unified Firmware uncomment the printer model you have and the probe mount you are using. Probe mount STL files are included in the Unified Firmware package for every model we support. Set the EZABL_PROBE_EDGE setting to 45-50mm for larger printer beds (300mm+ size beds) and 10-20mm for smaller printer beds. Check to make sure the probe is not probing over any binder clips and/or screw heads in the bed as this can affect the reading. If you have a custom machine we can assist with setting up the firmware as long as you have the current firmware for the machine and it is working 100% without the EZABL installed already. We will need the full source code used to do these changes.

Thank you in advance.

I made some research and I think I will use the expansion header breakout because if I use the LCD port to connect the drivers (MA860H) it gives me 3v and I need 5v.

In resume, I will connect the 6 X, Y and Z nema 23 2.8A to the Duet wifi, using the E0 and E1 inputs. The two extruders nema 34 will be driven through the expansion header breakout board. And the Panel Due I bought will be connected through the LCD port.

And I will not be using the Duex 5, so I will sell it or save it for another project.

If I am missing something please let me know.

Thank you for the help, I really appreciate it.

@elmoret Thank you man! You saved my day! Greetings from Argentina

@elmoret said in Duex and expansion header breakout:

These go on the Duet Wifi.

Thank you for your reply. The Duet wifi has only 5 stepper drivers, so I need one more to drive the 6 steppers of the X, Y and Z axis. I was planning to take the driver from duex 5.

Talking about the second part of your answer... I didn't know the biggest stepper drivers can be connected to the LCD port. I will investigate that. Do I need to use the expansion header breakout then? Thank you

I need to use: two Z steppers, two Y steppers, two X steppers (IDEX) and two bigger steppers with external drivers for the two extruders. I have duet WIFI; the expansion header breakout board and DUEX5. Do I have any way to connect it all?

Hi, is there any way of using the Duex5 and the expansion header breakout together? I bought both for a project and I noticed now that both boards use the same duet wifi's pins for being connected. Thank you.

I've been thinking and I decided to make two custom heater blocks and I'll be using 4 or 3 heater cartridges in each. In this way I'll be capable of control the 8 or 6 heater cartridges with the duet wifi and duex5 (the heated bed will have a SSR). And I will contact E3D to know their opinion.

@T3P3Tony:

As Ian says e3d will have a better idea about this.

You may find that having only two preheat zones rather than three per input is acceptable. Also why complicate it with the cyclops? is that to get a higher flow rate? better to use a larger single extruder. with a 4mm nozzle you are printing thicker than the input filament (3mm or 1.75mm) so designs to look at could be pellet extruders / filament extruders like filastruder:

https://www.filastruder.com/products/filastruder-kit

The area of two 2.85mm diameter filament is 4mm, that's why i'm using cyclops and two extruders. I'll be using a couple of filastruder kits but I prefer to produce the filament first, because the filastruder extrusion speed is too low and so it would be the printer if I use it directly.

Here is a drawing of what I'm thinking.

http://i63.tinypic.com/2r5bwaw.jpg

I will use two systems like the picture. That's why I need 14 heater cartridges. It is important to me to say that the machine is intended to print with a 4mm nozzle diameter and the material that will be used is ABS, that's why I need a long and hot way for the filament to melt and let me print at high speeds. What do you think? Any help?

I will be using 2 print heads. Each print head will have 2 extruders (e3d titan) and 7 heater cartridges. So I will need only 4 extruders motors, there is no problem with that. My only problem now is how to control the heater cartridges. I need to know if there is a way to connect them to de duet wifi + duex5 or if it is another way to control their temperatures. Thank you!