This post was taken from this comment, as the OP did not repost their deleted answer as a new question.

With respect to this question: Anet A8 reading 739°C from the extruder thermistor!

Having read the issue, it seems that this is a common problem for the ANET3D board. I'd like to ask two questions:

1. Is it possible to sever connections to the ATMEGA and use the hardware itself while controlled with the Raspberry Pi or some other dev board?

2. While waiting for a new board (seems to be the only cost/time effective choice), is there any way to use the other temperature circuit (likely having to do some work in Arduino IDE)?

My hot end decided to set itself to 265°C while my bed is reading the new thermistor on the new Hot End just fine. I need to get a few prints made while waiting on funds to replace the board for full functionality.

I figure #1 is too much to hope for, but I have to ask. So, if you swap the heater circuits, what do you have to modify in configuration.h to convince the firmware to accept the modified input?

• This post was taken from this comment, as the OP did not repost their deleted answer as a new question.

• See associated post on SE.Meta: Is it possible to attribute a wiki post to a user?

With respect to this question: Anet A8 reading 739°C from the extruder thermistor!

Having read the issue, it seems that this is a common problem for the ANET3D board. I'd like to ask two questions:

1. Is it possible to sever connections to the ATMEGA and use the hardware itself while controlled with the Raspberry Pi or some other dev board?

2. While waiting for a new board (seems to be the only cost/time effective choice), is there any way to use the other temperature circuit (likely having to do some work in Arduino IDE)?

My hot end decided to set itself to 265°C while my bed is reading the new thermistor on the new Hot End just fine. I need to get a few prints made while waiting on funds to replace the board for full functionality.

I figure #1 is too much to hope for, but I have to ask. So, if you swap the heater circuits, what do you have to modify in configuration.h to convince the firmware to accept the modified input?

With respect to this question: Anet A8 reading 739°C from the extruder thermistor!

Having read the issue, it seems that this is a common problem for the ANET3D board. I'd like to ask two questions:

1. Is it possible to sever connections to the ATMEGA and use the hardware itself while controlled with the Raspberry Pi or some other dev board?

2. While waiting for a new board (seems to be the only cost/time effective choice), is there any way to use the other temperature circuit (likely having to do some work in Arduino IDE)?

My hot end decided to set itself to 265°C while my bed is reading the new thermistor on the new Hot End just fine. I need to get a few prints made while waiting on funds to replace the board for full functionality.

I figure #1 is too much to hope for, but I have to ask. So, if you swap the heater circuits, what do you have to modify in configuration.h to convince the firmware to accept the modified input?

This post was taken from this comment, as the OP did not repost their deleted answer as a new question.

With respect to this question: Anet A8 reading 739°C from the extruder thermistor!

Having read the issue, it seems that this is a common problem for the ANET3D board. I'd like to ask two questions:

1. Is it possible to sever connections to the ATMEGA and use the hardware itself while controlled with the Raspberry Pi or some other dev board?

2. While waiting for a new board (seems to be the only cost/time effective choice), is there any way to use the other temperature circuit (likely having to do some work in Arduino IDE)?

My hot end decided to set itself to 265°C while my bed is reading the new thermistor on the new Hot End just fine. I need to get a few prints made while waiting on funds to replace the board for full functionality.

I figure #1 is too much to hope for, but I have to ask. So, if you swap the heater circuits, what do you have to modify in configuration.h to convince the firmware to accept the modified input?