Firmware installation

• 

  Flashing firmware on Mac OS X
  • droftarts  

  12
  4
  Votes
  12
  Posts
  307
  Views

  

  @droftarts said in Flashing firmware on Mac OS X: I think it’s the same problem, with the dependent dynamic library (libpng, libjpeg) missing from Bossa. bossac from the commandline shouldn't need them libraries? might be worth at try if bulding from source isn't an option
• 

  Hangprinter help on duet 3
  • Shinomori  

  23
  0
  Votes
  23
  Posts
  256
  Views

  

  I'm glad you got it working! I presume you used the RRF firmware fork from the creator of Hangprinter. We'd love to incorporate many of the improvements he has made to Hangprinter support in that fork into our standard build. Unfortunately, in that fork he repurposes the UARTs (to drive Mechaduinos in torque mode AFAIR), which makes it incompatible with normal use of RRF. Duet/RRF do support I2C, so I don't know why I2C wasn't used. However, i2C is generally a bad choice for connecting different devices because it has no noise immunity. It was designed for interconnecting ICs on the same board only.
• 

  Guide for posting requests for help
  • T3P3Tony  

  1
  0
  Votes
  1
  Posts
  535
  Views

  No one has replied

• 

  Wifi not connecting after firmware install. Duet2 Wifi
  • haydenkrause  

  19
  0
  Votes
  19
  Posts
  42
  Views

  

  @haydenkrause said in Wifi not connecting after firmware install. Duet2 Wifi: I am following a few posts on here with people having the same issues currently unsolved Which would those be? link? You could post your RRF3 config.g as well in case it's just a simple syntax error. What probe are you using specifically?
• 

  2 Component Fans
  • Heartleander81  

  35
  0
  Votes
  35
  Posts
  129
  Views

  

  @Phaedrux I have write T0 at custom settings are not defined and save the config.g. I am so happy.
• 

  calibration IR probe RRF3
  • Rudy2A  

  37
  0
  Votes
  37
  Posts
  92
  Views

  

  @Phaedrux Thank you, I'm testing ...
• 

  Dual Z Motors single Z Probe as end stop for each motor
  • Bluemalu  

  5
  0
  Votes
  5
  Posts
  14
  Views

  

  Perfect, bed is a piece of 6mm tooling aluminium with little flex so no point in over egging the pudding. Time to start printing as that was my last query from my upgrade.
• 

  Duet 2 Wifi stuck in diagnostic mode
  • firex726  

  3
  0
  Votes
  3
  Posts
  18
  Views

  

  Jumper should be removed before performing the flash operation, otherwise board will remain in bootloader. Some have issues with resetting the board after flashing, I prefer the command line version as it takes care of the reset in software. Recent topic about the same (adjust filename and COM port number to suit if you wanna give it a go)
• 

  Fan setup - Dual Extruders / Part Coolers - Duet 3
  • Bluemalu  

  7
  0
  Votes
  7
  Posts
  31
  Views

  

  That's correct. The Config tool cannot currently setup a dual z axis. That must be done manually in config.g. The config.json file is not editable either. It's simply used to bring the config from the tool back into the tool in case you wanted to make a change or use it as a base to modify from. For the part cooling fan you can click on the fan0/fan1 boxes for each tool to assign them, in case that wasn't clear.
• 

  Duet wifi 1.04 restarting when uploading config files
  • RodrigoRMaraujo  

  7
  0
  Votes
  7
  Posts
  36
  Views

  

  What does Bossa identify the CPU as? Maybe China took some liberties in the BOM department?
• 

  Duet 2 wifi heated bed heating when motherbord off
  • Dennisdaan2  

  7
  0
  Votes
  7
  Posts
  42
  Views

  

  @Dennisdaan2 said in Duet 2 wifi heated bed heating when motherbord off: M140 H0 S100 R80 Remove that entirely from your config.g You've misunderstood how M140 works. https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M140_Set_Bed_Temperature_Fast_or_Configure_Bed_Heater All you should have is M140 H0 that sets the H0 heater as a bed heater. Using S and R turns on the heater. The web interface isn't going to stop that. M140 S100 R80 will turn on the heater as soon as it's executed.
• 

  UNSOLVED E motor turns when Z motor is supposed to run
  • Ian Miller  

  3
  0
  Votes
  3
  Posts
  17
  Views

  

  @Phaedrux Thank you, this fixed my issue.
• 

  Duet2 update from v1.21 to v3.01 necessary?
  • DanL  

  3
  0
  Votes
  3
  Posts
  41
  Views

  

  Thank you....will try today.
• 

  incompatible firmware v on duet3?
  • Martin1454  

  11
  0
  Votes
  11
  Posts
  91
  Views

  

  @Martin1454 said in incompatible firmware v on duet3?: @dc42 said in incompatible firmware v on duet3?: Your best options are to upgrade the main firmware using Bossa, or to run the Duet in standalone mode with a USB connection and install the latest firmware from the SD card. Upgrading to 3.0 first isn't essential on the Duet 3. What would you reccomend to upgrade to then? 3.1.1 to bring it into line with the version of DSF on your Pi.
• 

  RRF3 & P0 to P1 must be in clockwise...
  • Rudy2A  

  3
  0
  Votes
  3
  Posts
  22
  Views

  

  @dc42 said in RRF3 & P0 to P1 must be in clockwise...: That means it has reverted to the old-style bed compensation. What is your G32 file used for? If it is for true bed levelling, check that the number of points declared in M671 is the same as the number of Z motors declared in M584. Solved, I just forgot to put my M671 back into my new Config.g file! Thanks for enlightening me.
• 

  Endstop problem DeltaWasp
  delta endstop • • goodchrhere  

  11
  0
  Votes
  11
  Posts
  72
  Views

  

  Hi ! I know you've solved the problem you initially asked about. I'm wondering it you could give my some info on how tricky putting a Duet board on a WASP delta was? I have a WASP 60100 (build 2017) and would love to upgrade it with a Duetboard and maybe a E3D Volcano hotend. But, I'm not really sure what I'm getting myself into Would you mind me asking a couple of newbie questions about your process?
• 

  SOLVED Homing issues on a Delta with Duet 2
  • Meki  

  12
  0
  Votes
  12
  Posts
  36
  Views

  

  @jay_s_uk, @Phaedrux, @Veti thanks for all the help! After quadruple checking, it turns out that the endstops were mixed up. Since then, everything is in working order!
• 

  UNSOLVED Formbot Troodon RRF 3.1.1 Update
  • InsanityAutomation  

  38
  1
  Votes
  38
  Posts
  319
  Views

  

  @tommyb This thread is for people having problems with the Formbot Troodon custom RRF compatible board. Please start a new thread for your issue with the Duet Wifi.
• 

  Help PID tuning Dyzend Pro
  • chris974M  

  72
  0
  Votes
  72
  Posts
  200
  Views

  

  @ejarmo said in Help PID tuning Dyzend Pro: would you be willing to locate the appropriate pins on a maestro for this process The Maestro does not have an expansion connector with thermistor inputs, so this process does not apply. You would need to desolder one of the existing 2K2 thermistor series resistors and replace it by a 27K resistor. There is just a chance that you may be able to get the thermistor working with the existing series resistor if you use the new semi-automatic calibration procedure that firmware 3.2beta1 supports. The calibration procedure is described at https://duet3d.dozuki.com/Wiki/Calibrating_thermistor_and_PT1000_readings. Caution, if you are currently running version 2.x firmware on your Maestro then upgrading to 3.x firmware requires significant changes to the config.g file.
• 

  Help! "Error: G30: Z probe 0 not found" upgrading RRF2 -> RRF3
  • BananaMuffin  

  4
  1
  Votes
  4
  Posts
  19
  Views

  

  What a great first post! It contained all the needed information to provide a quick and accurate solution. I wish they were all like this!
• 

  bltouch not responding to commands
  • dakingofhearts2003  

  8
  0
  Votes
  8
  Posts
  21
  Views

  

  Please verify your firmware version with M115. If you send M98 P"config.g" do you get any error messages? Your config is basically correct for a BLTouch connected to heater pin 3 on the expansion port provided you're actually using RRF3. M558 P9 C"^zprobe.in" H5 F6000 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X-39 Y14 Z5 ; set Z probe trigger value, offset and trigger height G31 Z5 is a very high trigger height. Be sure to do a calibration measurement once it's actually working. https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe M558 F6000 is very fast probing speed for the BLTouch. F120 is more appropriate. Your Z axis speed is currently limited to 180mm/min so it can't probe faster than that, but that's really slow for normal movement, might want to change to M203 Z600.
• 

  DWC/firmware mismatch
  • jumpedwithbothfeet  

  22
  0
  Votes
  22
  Posts
  53
  Views

  

  I've added some notes to the Duet3 documentation on powering the SBC. When in doubt, power it separately. https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Hardware_Overview?revisionid=HEAD#Section_Electronics_power_consumption
• 

  Error: M587: string too long
  • tkdirp  

  7
  0
  Votes
  7
  Posts
  33
  Views

  

  Can you try setting up the Duet in Access Point mode? This will have the Duet create its own wifi network that you can connect to from your device. If this works then we know the problem is with the router/configuration rather than the duet hardware. https://duet3d.dozuki.com/Wiki/Gcode#Section_M589_Configure_access_point_parameters
• 

  SOLVED Error: M106 : Fan 2 not found
  • rzi  

  6
  0
  Votes
  6
  Posts
  34
  Views

  

  @Phaedrux It was a user error. I have two CNC machines. On my old machine I also control the dust extractor. with the M106 command autogenerated from my postprocessor. My new machine has nothing connected so it hits an error, naturally. Still, you pushed me in the the right direction by mentioning other config files, so thanx.
• 

  Problem with setting my z-offset
  • Torin  

  9
  0
  Votes
  9
  Posts
  31
  Views

  

  I thought I did, I will double check that bit later and report my findings. Thanks!