Dual X carriage printer - cooling fan

Comments

• Repetier

  May 2018

  I know what you mean. In fact only fan 1 is supposed to be a cooling fan and Fan 2 should be used for other uses. That is also why we have only one field for fan with exact timings.
  
  So a better solution would be to have a pin definition for each extruder for the filament cooling fan and P0/no P should always address the associated fan mapped for the extruder. With the current design this would require some ugly solutions. In the next big release V2 the configuration is much more modular and should give a better solution for this problem. It already supports unlimited pwm outputs and with a extra class it would be easy to solve this problem to multiplex signals to active extruder, so i have planned this in V2. For V1 we only plan bug fixes and small improvements.
• MatYay

  May 2018

  Ok. Then I will make the ugly solution myself and wait for stable release of the V2 firmware.
• dukeneukam

  January 2019

  I have also built a printer with dual x carriages and have the same problem.  If you have a solution, would you mind sharing it?
  
• Repetier

  January 2019

  V2 has solved it meanwhile. If you use M106/M107 without P it is mapped to the active extruder.
• dukeneukam

  January 2019

  I would like to try v2 firmware, but I'm waiting for support for the 2004 reprapdiscount display. I had been unable to get a graphic display working with my ramps-fd. Maybe I should just swap in an 8 bit board...
• Repetier

  January 2019

  Currently only RADDS/Graphic display is tested and configured in V2. See in boards/radds.j near end you have
  
  

  // Controller related default pins

  
  

  #ifndef CUSTOM_CONTROLLER_PINS

  #if FEATURE_CONTROLLER == CONTROLLER_SPARKLCD

  
  

  #define UI_DISPLAY_RS_PIN 25

  #define UI_DISPLAY_RW_PIN -1

  #define UI_DISPLAY_ENABLE_PIN 27

  #define UI_DISPLAY_D4_PIN 29

  #define UI_DISPLAY_D5_PIN -1

  #define UI_ENCODER_A 35

  #define UI_ENCODER_B 33

  #define UI_ENCODER_CLICK 37

  #define UI_RESET_PIN -1

  #define UI_BACK_PIN -1

  
  

  #elif FEATURE_CONTROLLER == CONTROLLER_SPARKLCD_ADAPTER || FEATURE_CONTROLLER == CONTROLLER_ORCABOTXXLPRO2

  
  

  #define UI_DISPLAY_RS_PIN 44

  #define UI_DISPLAY_RW_PIN -1

  #define UI_DISPLAY_ENABLE_PIN 45

  #define UI_DISPLAY_D4_PIN 46

  #define UI_DISPLAY_D5_PIN -1

  #define UI_ENCODER_A 50

  #define UI_ENCODER_B 52

  #define UI_ENCODER_CLICK 48

  #define UI_RESET_PIN -1

  #define UI_BACK_PIN -1

  
  

  #else

  
  

  // This is for offcial display port usage

  
  

  #define BEEPER_PIN 41

  #define UI_DISPLAY_RS_PIN 42

  #define UI_DISPLAY_RW_PIN -1

  #define UI_DISPLAY_ENABLE_PIN 43

  #define UI_DISPLAY_D0_PIN 44

  #define UI_DISPLAY_D1_PIN 45

  #define UI_DISPLAY_D2_PIN 46

  #define UI_DISPLAY_D3_PIN 47

  #define UI_DISPLAY_D4_PIN 44

  #define UI_DISPLAY_D5_PIN 45

  #define UI_DISPLAY_D6_PIN 46

  #define UI_DISPLAY_D7_PIN 47

  #define UI_ENCODER_A 50

  #define UI_ENCODER_B 52

  #define UI_ENCODER_CLICK 48

  #define UI_RESET_PIN -1

  #define UI_BACK_PIN 71

  
  

  #endif

  #endif

  
  So in contrast to V1 we now move the display pin assignments to the boards. I still have to move them from DisplayList.h in V1 to the boards and merge identical pins into groups. But you can easily do that for your board and it should work.
• dukeneukam

  January 2019

  I appreciate your response, however I have been unable to get a graphic display working with any firmware.  All I get is garbage on the display.  I believe it to be a hardware problem, possibly with the level shifter on the display adapter board.  I've given up on trying to make the RAMPS-FD work with a graphic display, but 2004 displays work, which I think is kind of weird that one type works and not the other.  Last night I attempted to compile V2 for a Rumba board, using the Orcabot XXL example config and got the following errors
  
  io_analog.h
      'analogEnabled' was not declared in this scope (36,5)
  tools.h
      statement-expressions are not allowed outside functions nor in template-argument lists (49,121)
      statement-expressions are not allowed outside functions nor in template-argument lists (49,140)
  
  Are AVR boards supported at this time?
• Repetier

  January 2019

  V2 does currently have no support for 8 bit hardware. Need to write the drivers for hat.
• dukeneukam

  January 2019

  Thank you for your support and for all your hard work.