Hi. I’m having problems with the 32 bit marlin version. I’m using Ultratronics 1.0. The thermocouple ‘‘readings’’ are constantly 329.9 for both T0 and T1. Any ideas what might be the problem?
You have most probably selected the wrong thermistor in your config file.
Try
-1 and see if it’s better.
If not then -2 or -3
-3 : thermocouple with MAX31855 (only for sensor 0)
-
-2 : thermocouple with MAX6675 (only for sensor 0)
-
-1 : thermocouple with AD595
Some thermocouples will only with with sensor 0.
@Panayiotis_Savva ok i looked on the chip and it says 31855 so i changed to -3. now the readings are 20000. what do you mean with sensor 0?
Sensor 0 means T0
I will suggest that you open an issue on the Marlin GitHub page and try help further with the other devs.
@Panayiotis_Savva why would it only work with T0? the ultratronics board has 2 thermocouple chips.
i think there might be an issue with pin numbering in the firmware.
these are the current pin numbers in the firmware:
//###TEMPERATURE
#define ORIG_TEMP_0_PIN 0
#define ORIG_TEMP_1_PIN 2
#define ORIG_TEMP_2_PIN 3
#define ORIG_TEMP_3_PIN 4
#define ORIG_TEMP_BED_PIN 1
#define ORIG_TEMP_CHAMBER_PIN NoPin
#define ORIG_TEMP_COOLER_PIN NoPin
the picture shows the pin numbers from the board documentation,
I did submit an issue on github and i wrote the board manufacturer who also supplied the firmware. But i tried giving it a shot here also…
missing/deleted image from Google+
Just to confirm, did you compile Marlin 2.x latest? Maybe this week? Also can you share your config files?
This is the firmware i used. I used the marlin kimbra configurator suggested by the board manufacturer.
https://drive.google.com/open?id=16U3kKOwuOSuqTp2vH3pkzYzB8XqfOpNs
The official Marlin 2.x now supports the Ultratronics Pro 1.0
Link is here:
Give it a try.
If you want to use MarlinKimba which was the best known implementation for Marlin on the DUE and other Atmel chips, you’ll need to ask for support on this github page:
See which one works best for you.
It may be a real issue in the Firmware, so suggest to open a ticket based on which Marin you are using.
If you decide to use Marlin 2.x then you’ll need to do the config manually, and not with the MarlinKimba configuration tool.