5

I have the same problem as this person but I don't have those lines in my RAMPS.h file as seen here.

I've recently burnt my potentiometer on E0 so the motor isn't working properly anymore. I want to use it on E1 instead. If you have any better idea how to fix this instead of changing code in firmware, feel free to share.

0scar
  • 32,029
  • 10
  • 59
  • 135
Ilya Smirnoff
  • 69
  • 1
  • 1
  • 5
  • Your link is sort of broken, as is the link in your post on [thingiverse](https://www.thingiverse.com/groups/tevo-tarantula-owners/forums/general/topic:29448). Instead of pointing to a particular post, your are pointing to a general forum, and it is hard to see to which post your are actually referring. Please edit your post(s) and fix the URL, as your question will probably be of more help someone else, with the correct link to the other person's issue. Do you mean to refer to _this_ post: [Switch E0 to E1](https://www.thingiverse.com/groups/tevo-tarantula-owners/forums/general/topic:27363)? – Greenonline Apr 19 '18 at 17:59
  • In addition, if you refer to an external website, please quote the relevant details of the issue [external post] here, as the external link could die (as most links tend to do), and then some/most of the information, that pertains to your question, will be lost. Thanks and welcome to SE 3D Printing... :-) – Greenonline Apr 19 '18 at 18:05
  • It is pretty easy ;) to adjust the pins in the firmware, I already described that for somebody that wanted to use the E1 as X, please look at my answer of https://3dprinting.stackexchange.com/questions/3925/how-to-switch-motor-outputs-and-use-e1-as-x-in-marlin-firmware/5786#5786". – 0scar Apr 19 '18 at 18:14
  • It is MKS, but mks file refers to ramps file so i use pins_ramps.h – Ilya Smirnoff Apr 20 '18 at 14:02
  • @0scar still can't get it to work properly :( I've made neccesary changes in code, but now there is some problem with AVRDUDE http://dl3.joxi.net/drive/2018/04/20/0015/0211/991443/43/a8bca32cbc.png – Ilya Smirnoff Apr 22 '18 at 15:13
  • As said before, this has nothing to do with the code changes, it has something to do with your computer or Arduino setup. Look up some instructions on the web to upload firmware to your board, there are loads to find. – 0scar Apr 22 '18 at 21:44
  • @0scar so it might be that my arduino is now "bricked"? I have another Uno and it works just fine, but not this one – Ilya Smirnoff Apr 23 '18 at 14:30
  • No, it's not working. The arduino that is working is arduino uno and it is not for printer – Ilya Smirnoff Apr 30 '18 at 06:56

3 Answers3

3

Another posting already discusses how you can change the pins to use spare stepper controllers for broken controllers by changing the pin layout. Assuming you are using a RAMPS board and using Marlin firmware, you should look at the pins_RAMPS.h file.

This file requires changes to address E1 to E0 and vice versa, please edit the file so that:

#define E0_STEP_PIN        26
#define E0_DIR_PIN         28
#define E0_ENABLE_PIN      24
#define E0_CS_PIN          42

is changed to:

#define E0_STEP_PIN        36
#define E0_DIR_PIN         34
#define E0_ENABLE_PIN      30
#define E0_CS_PIN          44

and also change:

#define E1_STEP_PIN        36
#define E1_DIR_PIN         34
#define E1_ENABLE_PIN      30
#define E1_CS_PIN          44

to:

#define E1_STEP_PIN        26
#define E1_DIR_PIN         28
#define E1_ENABLE_PIN      24
#define E1_CS_PIN          42

When the file is changed an saved, build and upload code to your board and plug the connector of the E0 stepper into the E1 header.

0scar
  • 32,029
  • 10
  • 59
  • 135
  • I've done that already. But now i have a new problem. The new firmware doesn't want to install and arduino IDE throws an error http://joxi.ru/J2b6n9whXpYy02.png – Ilya Smirnoff Apr 20 '18 at 05:35
  • That has nothing to do with the code changes: https://stackoverflow.com/questions/19645441/avrdude-stk500v2-receivemessage-timeout or https://arduino.stackexchange.com/questions/13060/avrdude-stk500v2-getsync-timeout-communicating-with-programmer-error – 0scar Apr 20 '18 at 06:15
1

I wanted to expand on the great comment by 0scar and explain what's the fastest way to change pins. I know this is an older topic, but for the sake of people looking for an answer, I figured I add this.

First of all it's easiest to change the pins in the pins file for your specific board by simply renaming E0 to E1 and vice versa. This is much simpler than copying and pasting the pin numbers per pin. Only do this when swapping entire driver pin lists as this gets quite confusing when switching around only certain pin numbers.

Second, and this is a big one: don't forget that when you use drivers that are capable of sensorless homing, and when you use that technique, you also have to change the _DIAG_PIN settings or else the sensorless homing won't work correctly.

Marinus
  • 11
  • 1
0

the fastest way is to slice using two extruders and assign all print work to E1. Set the head offsets to [0,0] and that shall do the job.

The harder is to edit pins file and do remapping.

profesor79
  • 1,922
  • 1
  • 6
  • 24