Custom MCU-module for UP! Mini...

Post improvements made for UP, and share ideas.
Post Reply
Tinyfab
Posts: 14
Joined: Tue Aug 09, 2016 12:31 pm

Re: Custom MCU-module for UP! Mini...

Post by Tinyfab » Tue Aug 09, 2016 3:26 pm

Hello I ve made the CPU running smoothieware so if anyone wants one check it out -> http://shop.tinyfab.xyz

arhi
Posts: 256
Joined: Sun Mar 08, 2015 10:51 pm

Re: Custom MCU-module for UP! Mini...

Post by arhi » Wed Aug 17, 2016 2:20 pm

Tinyfab wrote:Hello I ve made the CPU running smoothieware so if anyone wants one check it out -> http://shop.tinyfab.xyz
any chance of a schematic? I see you have some jumpers on the board, I don't see any documentation about it anywhere :( .. (waiting for it to arrive, ebay wrote it's "shipped", will maybe some documentation arrive with it?)

Tinyfab
Posts: 14
Joined: Tue Aug 09, 2016 12:31 pm

Re: Custom MCU-module for UP! Mini...

Post by Tinyfab » Thu Aug 18, 2016 4:45 pm

Hey you can find some useful info here to get you started :)

https://drive.google.com/file/d/0BxnykI ... ef=2&pli=1

arhi
Posts: 256
Joined: Sun Mar 08, 2015 10:51 pm

Re: Custom MCU-module for UP! Mini...

Post by arhi » Thu Aug 18, 2016 10:47 pm

nice, got the schematic too so more then enough .. now just to wait for the board to arrive :D :D :D

initially I was confused where did you put the eprom but then remembered that eprom goes on replicape not on smoothieboard :D getting old :(

thanks
b.

tel
Posts: 242
Joined: Tue Feb 09, 2016 1:35 pm
Location: Australia
Contact:

Re: Custom MCU-module for UP! Mini...

Post by tel » Thu Aug 18, 2016 11:44 pm

Anyone know whether the UP Box uses the same MCU as the mini? Wondering whether this can be used in the UP Box as well.

Tinyfab
Posts: 14
Joined: Tue Aug 09, 2016 12:31 pm

Re: Custom MCU-module for UP! Mini...

Post by Tinyfab » Sat Aug 20, 2016 10:22 am

arhi wrote:nice, got the schematic too so more then enough .. now just to wait for the board to arrive :D :D :D

initially I was confused where did you put the eprom but then remembered that eprom goes on replicape not on smoothieboard :D getting old :(

thanks
b.
LOL the program lives inside the chip now :)

Tinyfab
Posts: 14
Joined: Tue Aug 09, 2016 12:31 pm

Re: Custom MCU-module for UP! Mini...

Post by Tinyfab » Mon Aug 22, 2016 3:43 pm

tegregg wrote:Anyone know whether the UP Box uses the same MCU as the mini? Wondering whether this can be used in the UP Box as well.
can you post a photo of the mainboard and cpu of the up box?

tel
Posts: 242
Joined: Tue Feb 09, 2016 1:35 pm
Location: Australia
Contact:

Re: Custom MCU-module for UP! Mini...

Post by tel » Tue Aug 23, 2016 4:26 am

Here you go
Image

Image

Tinyfab
Posts: 14
Joined: Tue Aug 09, 2016 12:31 pm

Re: Custom MCU-module for UP! Mini...

Post by Tinyfab » Tue Aug 23, 2016 12:55 pm

The main board looks identical to the up mini. It would be likely that it will work for normal printing. But I think there are special function like auto bed level and the special button action may not work. It might also be a matter of changing the config file to get it to work probably.

arhi
Posts: 256
Joined: Sun Mar 08, 2015 10:51 pm

Re: Custom MCU-module for UP! Mini...

Post by arhi » Tue Aug 23, 2016 8:26 pm

there's connector on that board for autobedlevel but it's not soldered on ... I'd assume all boards are identical, difference is only the firmware .. and maybe few missing parts on board ..

(custom mcu arrived :D unfortunately no time to test it these days but can't wait :D )

slait90
Posts: 10
Joined: Thu Apr 10, 2014 8:32 am

Re: Custom MCU-module for UP! Mini...

Post by slait90 » Thu Sep 15, 2016 7:55 am

Hello!
Can anyone explain how to connect to arduino2560 UP?
Help me please!!!
download/file.php?mode=view&id=2463
Attachments
ard.jpg
ard.jpg (108.07 KiB) Viewed 15445 times

orthoa
Posts: 7
Joined: Tue May 31, 2016 5:42 am

Re: Custom MCU-module for UP! Mini...

Post by orthoa » Wed Sep 21, 2016 12:49 am

Got this setup and working nicely on the UP! Box without too many issues. I haven't found a way to print from the SD card yet which would be very useful as well as switching on the lights in the printer. Any help would be much appreciated.

One thing I did find is if you use any of the side buttons on the UP! Box it confuses the MCU and you have to reboot it to get it to do anything also had to unplug the Autoleveler as the MCU kept activating the motor to move it up and down constantly.

tel
Posts: 242
Joined: Tue Feb 09, 2016 1:35 pm
Location: Australia
Contact:

Re: Custom MCU-module for UP! Mini...

Post by tel » Wed Sep 21, 2016 6:12 am

orthoa wrote:Got this setup and working nicely on the UP! Box without too many issues. I haven't found a way to print from the SD card yet which would be very useful as well as switching on the lights in the printer. Any help would be much appreciated.

One thing I did find is if you use any of the side buttons on the UP! Box it confuses the MCU and you have to reboot it to get it to do anything also had to unplug the Autoleveler as the MCU kept activating the motor to move it up and down constantly.
Id be interested in anything else you needed to do to get the UpBox working. Any adjustment to height etc?

orthoa
Posts: 7
Joined: Tue May 31, 2016 5:42 am

Re: Custom MCU-module for UP! Mini...

Post by orthoa » Wed Sep 21, 2016 10:22 pm

tegregg wrote: Id be interested in anything else you needed to do to get the UpBox working. Any adjustment to height etc?
Here is my config file it is slightly different to the UP Mini. All I needed to do was unplug the automatic bed leveler and that was it.

You also need to add to the starting g-code script G92 Z238.50 (Z height being the height of your nozzle)

Code: Select all

# NOTE Lines must not exceed 132 characters
## Robot module configurations : general handling of movement G-codes and slicing into moves
default_feed_rate 4000 # Default rate ( mm/minute ) for G1/G2/G3 moves
default_seek_rate 4000 # Default rate ( mm/minute ) for G0 moves
mm_per_arc_segment 0.5 # Arcs are cut into segments ( lines ), this is the length for
# these segments. Smaller values mean more resolution,
# higher values mean faster computation
#mm_per_line_segment 5 # Lines can be cut into segments ( not usefull with cartesian
# coordinates robots ).

# Arm solution configuration : Cartesian robot. Translates mm positions into stepper positions
alpha_steps_per_mm 656.0 # Steps per mm for alpha stepper
beta_steps_per_mm 656.0 # Steps per mm for beta stepper
gamma_steps_per_mm 3220.12 # Steps per mm for gamma stepper

# Planner module configuration : Look-ahead and acceleration configuration
planner_queue_size 32 # DO NOT CHANGE THIS UNLESS YOU KNOW EXACTLY WHAT YOU ARE DOING
acceleration 3000 # Acceleration in mm/second/second.
#z_acceleration 500 # Acceleration for Z only moves in mm/s^2, 0 uses acceleration which is the default. DO NOT SET ON A DELTA
acceleration_ticks_per_second 1000 # Number of times per second the speed is updated
junction_deviation 0.05 # Similar to the old "max_jerk", in millimeters,
# see https://github.com/grbl/grbl/blob/master/planner.c
# and https://github.com/grbl/grbl/wiki/Configuring-Grbl-v0.8
# Lower values mean being more careful, higher values means being
# faster and have more jerk
#z_junction_deviation 0.0 # for Z only moves, -1 uses junction_deviation, zero disables junction_deviation on z moves DO NOT SET ON A DELTA
#minimum_planner_speed 0.0 # sets the minimum planner speed in mm/sec

# Stepper module configuration
microseconds_per_step_pulse 1 # Duration of step pulses to stepper drivers, in microseconds
base_stepping_frequency 100000 # Base frequency for stepping

# Cartesian axis speed limits
x_axis_max_speed 30000 # mm/min
y_axis_max_speed 30000 # mm/min
z_axis_max_speed 1200 # mm/min

# Stepper module pins ( ports, and pin numbers, appending "!" to the number will invert a pin )
alpha_step_pin 2.1 # Pin for alpha stepper step signal
alpha_dir_pin 0.11! # Pin for alpha stepper direction
alpha_en_pin 2.4! #0.10 # Pin for alpha enable pin
alpha_current 1.5 # X stepper motor current
alpha_max_rate 30000.0 # mm/min

beta_step_pin 2.0 # Pin for beta stepper step signal
beta_dir_pin 0.5! # Pin for beta stepper direction
beta_en_pin 2.4! #0.4 # Pin for beta enable
beta_current 1.5 # Y stepper motor current
beta_max_rate 30000.0 # mm/min

gamma_step_pin 2.2 # Pin for gamma stepper step signal
gamma_dir_pin 0.20 # Pin for gamma stepper direction
gamma_en_pin 2.4! #0.19 # Pin for gamma enable
gamma_current 1.5 # Z stepper motor current
gamma_max_rate 1200.0 # mm/min

## System configuration
# Serial communications configuration ( baud rate defaults to 9600 if undefined )
uart0.baud_rate 115200 # Baud rate for the default hardware serial port
second_usb_serial_enable false # This enables a second usb serial port (to have both pronterface
# and a terminal connected)
leds_disable true # disable using leds after config loaded
#play_led_disable true # disable the play led

# Kill button (used to be called pause) maybe assigned to a different pin, set to the onboard pin by default
kill_button_enable true # set to true to enable a kill button
kill_button_pin 2.12 # kill button pin. default is same as pause button 2.12 (2.11 is another good choice)

#msd_disable false # disable the MSD (USB SDCARD) when set to true (needs special binary)
#dfu_enable false # for linux developers, set to true to enable DFU
#watchdog_timeout 10 # watchdog timeout in seconds, default is 10, set to 0 to disable the watchdog

# Only needed on a smoothieboard
currentcontrol_module_enable false #

## Extruder module configuration
extruder.hotend.enable true # Whether to activate the extruder module at all. All configuration is ignored if false
extruder.hotend.steps_per_mm 960 # up 640*1.53 Steps per mm for extruder stepper
extruder.hotend.default_feed_rate 600 # Default rate ( mm/minute ) for moves where only the extruder moves
extruder.hotend.acceleration 500 # Acceleration for the stepper motor mm/sec²
extruder.hotend.max_speed 50 # mm/s

extruder.hotend.step_pin 2.3 # Pin for extruder step signal
extruder.hotend.dir_pin 0.22! # Pin for extruder dir signal
extruder.hotend.en_pin 2.4! #0.21 # Pin for extruder enable signal

# extruder offset
#extruder.hotend.x_offset 0 # x offset from origin in mm
#extruder.hotend.y_offset 0 # y offset from origin in mm
#extruder.hotend.z_offset 0 # z offset from origin in mm

# firmware retract settings when using G10/G11, these are the defaults if not defined, must be defined for each extruder if not using the defaults
#extruder.hotend.retract_length 3 # retract length in mm
#extruder.hotend.retract_feedrate 45 # retract feedrate in mm/sec
#extruder.hotend.retract_recover_length 0 # additional length for recover
#extruder.hotend.retract_recover_feedrate 8 # recover feedrate in mm/sec (should be less than retract feedrate)
#extruder.hotend.retract_zlift_length 0 # zlift on retract in mm, 0 disables
#extruder.hotend.retract_zlift_feedrate 6000 # zlift feedrate in mm/min (Note mm/min NOT mm/sec)

delta_current 1.5 # First extruder stepper motor current

# Second extruder module configuration
#extruder.hotend2.enable true # Whether to activate the extruder module at all. All configuration is ignored if false
#extruder.hotend2.steps_per_mm 140 # Steps per mm for extruder stepper
#extruder.hotend2.default_feed_rate 600 # Default rate ( mm/minute ) for moves where only the extruder moves
#extruder.hotend2.acceleration 500 # Acceleration for the stepper motor, as of 0.6, arbitrary ratio
#extruder.hotend2.max_speed 50 # mm/s

#extruder.hotend2.step_pin 2.8 # Pin for extruder step signal
#extruder.hotend2.dir_pin 2.13 # Pin for extruder dir signal
#extruder.hotend2.en_pin 4.29 # Pin for extruder enable signal

#extruder.hotend2.x_offset 0 # x offset from origin in mm
#extruder.hotend2.y_offset 25.0 # y offset from origin in mm
#extruder.hotend2.z_offset 0 # z offset from origin in mm
#epsilon_current 1.5 # Second extruder stepper motor current


## Laser module configuration
laser_module_enable false # Whether to activate the laser module at all. All configuration is
# ignored if false.
#laser_module_pin 2.5 # this pin will be PWMed to control the laser. Only P2.0 - P2.5, P1.18, P1.20, P1.21, P1.23, P1.24, P1.26, P3.25, P3.26
# can be used since laser requires hardware PWM
#laser_module_maximum_power 1.0 # this is the maximum duty cycle that will be applied to the laser
#laser_module_minimum_power 0.0 # This is a value just below the minimum duty cycle that keeps the laser
# active without actually burning.
#laser_module_default_power 0.8 # This is the default laser power that will be used for cuts if a power has not been specified. The value is a scale between
# the maximum and minimum power levels specified above
#laser_module_pwm_period 20 # this sets the pwm frequency as the period in microseconds

## Temperature control configuration
# First hotend configuration
temperature_control.hotend.enable true # Whether to activate this ( "hotend" ) module at all.
# All configuration is ignored if false.
temperature_control.hotend.thermistor_pin 0.23 # Pin for the thermistor to read
temperature_control.hotend.heater_pin 2.7 # Pin that controls the heater, set to nc if a readonly thermistor is being defined
temperature_control.hotend.thermistor EPCOS100K # see http://smoothieware.org/temperaturecontrol#toc5
#temperature_control.hotend.beta 4066 # or set the beta value
#temperature_control.hotend.r0 100
temperature_control.hotend.set_m_code 104 #
temperature_control.hotend.set_and_wait_m_code 109 #
temperature_control.hotend.designator T #
#temperature_control.hotend.max_temp 300 # Set maximum temperature - Will prevent heating above 300 by default
#temperature_control.hotend.min_temp 0 # Set minimum temperature - Will prevent heating below if set

#temperature_control.hotend.p_factor 13.7 # permanently set the PID values after an auto pid
#temperature_control.hotend.i_factor 0.097 #
#temperature_control.hotend.d_factor 24 #

#temperature_control.hotend.max_pwm 64 # max pwm, 64 is a good value if driving a 12v resistor with 24v.

# Second hotend configuration
#temperature_control.hotend2.enable true # Whether to activate this ( "hotend" ) module at all.
# All configuration is ignored if false.

#temperature_control.hotend2.thermistor_pin 0.25 # Pin for the thermistor to read
#temperature_control.hotend2.heater_pin 1.23 # Pin that controls the heater
#temperature_control.hotend2.thermistor EPCOS100K # see http://smoothieware.org/temperaturecontrol#toc5
##temperature_control.hotend2.beta 4066 # or set the beta value
#temperature_control.hotend2.set_m_code 104 #
#temperature_control.hotend2.set_and_wait_m_code 109 #
#temperature_control.hotend2.designator T1 #

#temperature_control.hotend2.p_factor 13.7 # permanently set the PID values after an auto pid
#temperature_control.hotend2.i_factor 0.097 #
#temperature_control.hotend2.d_factor 24 #

#temperature_control.hotend2.max_pwm 64 # max pwm, 64 is a good value if driving a 12v resistor with 24v.

temperature_control.bed.enable true #
temperature_control.bed.thermistor_pin 0.24 #
temperature_control.bed.heater_pin 2.5 #
temperature_control.bed.thermistor Honeywell100K # see http://smoothieware.org/temperaturecontrol#toc5
#temperature_control.bed.beta 3974 # or set the beta value

temperature_control.bed.set_m_code 140 #
temperature_control.bed.set_and_wait_m_code 190 #
temperature_control.bed.designator B #

#temperature_control.bed.bang_bang false # set to true to use bang bang control rather than PID
#temperature_control.bed.hysteresis 2.0 # set to the temperature in degrees C to use as hysteresis
# when using bang bang

## Switch module for fan control
switch.fan.enable true #
switch.fan.input_on_command M106 #
switch.fan.input_off_command M107 #
switch.fan.output_pin 2.6 #
switch.fan.output_type pwm # pwm output settable with S parameter in the input_on_comand
#switch.fan.max_pwm 255 # set max pwm for the pin default is 255

#switch.misc.enable true #
#switch.misc.input_on_command M42 #
#switch.misc.input_off_command M43 #
#switch.misc.output_pin 2.4 #
#switch.misc.output_type digital # just an on or off pin

# Switch module for spindle control
#switch.spindle.enable false #

## Temperatureswitch :
# automatically toggle a switch at a specified temperature. Different ones of these may be defined to monitor different temperatures and switch different swithxes
# useful to turn on a fan or water pump to cool the hotend
#temperatureswitch.hotend.enable true #
#temperatureswitch.hotend.designator T # first character of the temperature control designator to use as the temperature sensor to monitor
#temperatureswitch.hotend.switch misc # select which switch to use, matches the name of the defined switch
#temperatureswitch.hotend.threshold_temp 60.0 # temperature to turn on (if rising) or off the switch
#temperatureswitch.hotend.heatup_poll 15 # poll heatup at 15 sec intervals
#temperatureswitch.hotend.cooldown_poll 60 # poll cooldown at 60 sec intervals


## Endstops
endstops_enable true # the endstop module is enabled by default and can be disabled here
#corexy_homing false # set to true if homing on a hbot or corexy
alpha_min_endstop 1.26^ # add a ! to invert if endstop is NO connected to ground
alpha_max_endstop 1.26^ #1.24^ # NOTE set to nc if this is not installed
alpha_homing_direction home_to_min # or set to home_to_max and set alpha_max
alpha_min 0 # this gets loaded after homing when home_to_min is set
alpha_max 120 # this gets loaded after homing when home_to_max is set
beta_min_endstop 1.24^ #1.25^ #
beta_max_endstop 1.24^ #
beta_homing_direction home_to_min #
beta_min 0 #
beta_max 120 #
gamma_min_endstop 1.28^ #1.28^ #
gamma_max_endstop 1.28^ #
gamma_homing_direction home_to_max #
gamma_min 0 #
gamma_max 120 #

# optional order in which axis will home, default is they all home at the same time,
# if this is set it will force each axis to home one at a time in the specified order
#homing_order XYZ # x axis followed by y then z last
#move_to_origin_after_home false # move XY to 0,0 after homing

# optional enable limit switches, actions will stop if any enabled limit switch is triggered
#alpha_limit_enable true # set to true to enable X min and max limit switches
#beta_limit_enable true # set to true to enable Y min and max limit switches
#gamma_limit_enable true # set to true to enable Z min and max limit switches

alpha_fast_homing_rate_mm_s 50 # feedrates in mm/second
beta_fast_homing_rate_mm_s 50 # "
gamma_fast_homing_rate_mm_s 4 # "
alpha_slow_homing_rate_mm_s 25 # "
beta_slow_homing_rate_mm_s 25 # "
gamma_slow_homing_rate_mm_s 2 # "

alpha_homing_retract_mm 5 # distance in mm
beta_homing_retract_mm 5 # "
gamma_homing_retract_mm 1 # "

#endstop_debounce_count 100 # uncomment if you get noise on your endstops, default is 100

## Z-probe
zprobe.enable false # set to true to enable a zprobe
zprobe.probe_pin 1.28!^ # pin probe is attached to if NC remove the !
zprobe.slow_feedrate 5 # mm/sec probe feed rate
#zprobe.debounce_count 100 # set if noisy
zprobe.fast_feedrate 100 # move feedrate mm/sec
zprobe.probe_height 5 # how much above bed to start probe
#gamma_min_endstop nc # normally 1.28. Change to nc to prevent conflict,

# associated with zprobe the leveling strategy to use
#leveling-strategy.three-point-leveling.enable true # a leveling strategy that probes three points to define a plane and keeps the Z parallel to that plane
#leveling-strategy.three-point-leveling.point1 100.0,0.0 # the first probe point (x,y) optional may be defined with M557
#leveling-strategy.three-point-leveling.point2 200.0,200.0 # the second probe point (x,y)
#leveling-strategy.three-point-leveling.point3 0.0,200.0 # the third probe point (x,y)
#leveling-strategy.three-point-leveling.home_first true # home the XY axis before probing
#leveling-strategy.three-point-leveling.tolerance 0.03 # the probe tolerance in mm, anything less that this will be ignored, default is 0.03mm
#leveling-strategy.three-point-leveling.probe_offsets 0,0,0 # the probe offsets from nozzle, must be x,y,z, default is no offset
#leveling-strategy.three-point-leveling.save_plane false # set to true to allow the bed plane to be saved with M500 default is false

## Panel
panel.enable false # set to true to enable the panel code

# Example for reprap discount GLCD
# on glcd EXP1 is to left and EXP2 is to right, pin 1 is bottom left, pin 2 is top left etc.
# +5v is EXP1 pin 10, Gnd is EXP1 pin 9
#panel.lcd reprap_discount_glcd #
#panel.spi_channel 0 # spi channel to use ; GLCD EXP1 Pins 3,5 (MOSI, SCLK)
#panel.spi_cs_pin 0.16 # spi chip select ; GLCD EXP1 Pin 4
#panel.encoder_a_pin 3.25!^ # encoder pin ; GLCD EXP2 Pin 3
#panel.encoder_b_pin 3.26!^ # encoder pin ; GLCD EXP2 Pin 5
#panel.click_button_pin 1.30!^ # click button ; GLCD EXP1 Pin 2
#panel.buzz_pin 1.31 # pin for buzzer ; GLCD EXP1 Pin 1
#panel.back_button_pin 2.11!^ # back button ; GLCD EXP2 Pin 8

# pins used with other panels
#panel.up_button_pin 0.1! # up button if used
#panel.down_button_pin 0.0! # down button if used
#panel.click_button_pin 0.18! # click button if used

panel.menu_offset 0 # some panels will need 1 here

panel.alpha_jog_feedrate 6000 # x jogging feedrate in mm/min
panel.beta_jog_feedrate 6000 # y jogging feedrate in mm/min
panel.gamma_jog_feedrate 200 # z jogging feedrate in mm/min

panel.hotend_temperature 185 # temp to set hotend when preheat is selected
panel.bed_temperature 60 # temp to set bed when preheat is selected

## Custom menus : Example of a custom menu entry, which will show up in the Custom entry.
# NOTE _ gets converted to space in the menu and commands, | is used to separate multiple commands
custom_menu.power_on.enable true #
custom_menu.power_on.name Power_on #
custom_menu.power_on.command M80 #

custom_menu.power_off.enable true #
custom_menu.power_off.name Power_off #
custom_menu.power_off.command M81 #


## Network settings
network.enable false # enable the ethernet network services
network.webserver.enable true # enable the webserver
network.telnet.enable true # enable the telnet server
network.ip_address auto # use dhcp to get ip address
# uncomment the 3 below to manually setup ip address
#network.ip_address 192.168.3.222 # the IP address
#network.ip_mask 255.255.255.0 # the ip mask
#network.ip_gateway 192.168.3.1 # the gateway address
#network.mac_override xx.xx.xx.xx.xx.xx # override the mac address, only do this if you have a conflict

Kai
Posts: 26
Joined: Sat Aug 08, 2015 6:07 pm

Re: Custom MCU-module for UP! Mini...

Post by Kai » Fri Sep 23, 2016 10:55 pm

Early discussions on this thread were mostly about the idea to use a custom MCU in order to get fine grade settings and other slicers to work with the UP. Therefore I wanted to note here, that there is a transcoder project in order to use standard G-Code with the UP series of printers. With this little helper you are able to use Slic3er, Simplify3D and generate prints from G-Code.

The transcoder had some issues with internal precision resulting in sometimes badly aligned prints. I managed to catch this bug and there is a new version v0.7.1 available here: https://github.com/UP3D-gcode/UP3D/releases

I have tested this version with my UP mini running under OS X. You are welcome to give it a try. :)

-Kai

arhi
Posts: 256
Joined: Sun Mar 08, 2015 10:51 pm

Re: Custom MCU-module for UP! Mini...

Post by arhi » Sun Sep 25, 2016 9:15 pm

Tinyfab wrote:Hey you can find some useful info here to get you started :)

https://drive.google.com/file/d/0BxnykI ... ef=2&pli=1
I'm pressed with time and I could not find time to test this but since the original UP! electronics starts to get on my nerves big time, and today the firmware autfscked itself and TearTime for some reason removed all downloads for the firmware for the UP! Plus2 (I have 6.09 on my machine but its corrupted and I can't reflash it because that ROM file is now nowhere to be found ?! it was with one of the installations but I downloaded ALL installations avaialble on the site and none of them have the ROM file that wants to go into UP Plus2 :( ) so I had to push this board in.

for start smoothieware do not have support for PT100 so I added a new class pt100, included it as a new sensor type and it should work ok but then trying to figure out what are the values I'm getting and to tune the temp calculation I see I'm getting crap from the sensor :( ... looking at the board the two pins from CPU AMP_MOD_1 and AMP_MOD_2 are supplying voltage to the resistor network in the opamp input changing the behavior of the circuit. I also see that temp comes from the RTD trough relay ?! interesting design .. not really sure what's the point, neither for the temp readout nor the amp_mod_? thing... seems that it hopes to slowly increase the output of LM in case someone connected sensor to a 12V heater or soemthing like that .. dunno ... the RA30 is especially unclear to me :( ... anyhow, pretty weird setup I'd say, a simple 1mA source trough sensor would imo be cheaper and more precise solution but .. whatever..
Capture.JPG
Capture.JPG (54.8 KiB) Viewed 15317 times
now, in order for PT100 to be properly read you have to have AMP_MOD_? high otherwise you are getting crap on the output, but I don't see in the config file provided any mention of 1.20 and 1.21 pins?

to be honest I expected to see on this board more then mcu+psu, I expected some of these things to be resolved (for e.g. smoothieware don't support PT100, converting PT100 "custom" output of UP! board UA1 - both hotend and hotbed sensor outputs - in to curve that looks like a standard NTC curve ..)

Tinyfab
Posts: 14
Joined: Tue Aug 09, 2016 12:31 pm

Re: Custom MCU-module for UP! Mini...

Post by Tinyfab » Wed Sep 28, 2016 2:20 am

Hi arhi

nice circuit trace.

I did mod the smoothieware so that it will work on the PT100 but it is a very dirty hack. What I did was reading the analog pin value and measured the actual temperature and apply some maths to it. I assumed it has a linear relationship. The firmware installed on the CPU has already got the mod. it is hardcoded so you can change it regardless of the probe type you set in config. I can post the code up tonight if anyone needs. Ideally it should be in a new class of its own, but I never got the time to do it.

note: In the hacked rom you will need to turn the motor power on in order to get the correct reading. ( I presumed something to do with the weird design as you mentioned )

Jack

arhi
Posts: 256
Joined: Sun Mar 08, 2015 10:51 pm

Re: Custom MCU-module for UP! Mini...

Post by arhi » Wed Sep 28, 2016 3:31 am

Tinyfab wrote: I did mod the smoothieware so that it will work on the PT100 but it is a very dirty hack. What I did was reading the analog pin value and measured the actual temperature and apply some maths to it
were you turning AMP_MOD* pins on before you read ADC?
do you have the table? I was about to start doing the same :D (get temp, res value and adc value and create a table).
I created a proper pt100 plug for the smoothieware but I need to get the "adcraw to temp" function working :D
Tinyfab wrote: . I assumed it has a linear relationship.
pt100 is more/less linear, especially in the region we are interested in :)
Tinyfab wrote: The firmware installed on the CPU has already got the mod. it is hardcoded so you can change it regardless of the probe type you set in config. I can post the code up tonight if anyone needs. Ideally it should be in a new class of its own, but I never got the time to do it.
yes please :D share :) .. so you did hacked the temp to work ok... I was geting some weird temperatures originally, probably the config was nok attm.
anyhow the one that was on the board is long time gone, also the config.txt you sent is probably for the mini or box, on the up plus2 the X and Y are swapped.. I doubt you intentionally switched them :)

I'll finish the pt100 module plugin and share the code back (maybe even someone pulls it into the smoothieware base code, would be cool to not have to maintain the fork)
Tinyfab wrote: note: In the hacked rom you will need to turn the motor power on in order to get the correct reading. ( I presumed something to do with the weird design as you mentioned )
yes, the + from the RTD does not go directly to RA4 but goes to a relay, when you enable the board (motor on) the 2 small white relays on the board switch on, the first one switches RTD -> RA4 (before that it links RA4 with RA30 - I assume it's used for some calibration on power or who knows what.. the other relay is not related to the temperature, it short circuits the Z axis stepper..

Tinyfab
Posts: 14
Joined: Tue Aug 09, 2016 12:31 pm

Re: Custom MCU-module for UP! Mini...

Post by Tinyfab » Wed Sep 28, 2016 3:27 pm

here is what I have modified in thermistor.cpp, I find dividing the adc value by 50 gives a close enough real temperature

Code: Select all

float Thermistor::adc_value_to_temperature(uint32_t adc_value)
{
const uint32_t max_adc_value= THEKERNEL->adc->get_max_value();
if ((adc_value >= max_adc_value) || (adc_value == 0))
return infinityf();

// resistance of the thermistor in ohms
float r = r2 / (((float)max_adc_value / adc_value) - 1.0F);
if (r1 > 0.0F) r = (r1 * r) / (r1 - r);

if(r > this->r0 * 8) return infinityf(); // 800k is probably open circuit

float t;
if(this->use_steinhart_hart) {
float l = logf(r);
t= (1.0F / (this->c1 + this->c2 * l + this->c3 * powf(l,3))) - 273.15F;
}else{
// use Beta value
t= (1.0F / (k + (j * logf(r / r0)))) - 273.15F;
}

//jack return t;

return adc_value/50; //jack debug
}

arhi
Posts: 256
Joined: Sun Mar 08, 2015 10:51 pm

Re: Custom MCU-module for UP! Mini...

Post by arhi » Wed Sep 28, 2016 8:32 pm

thanks, I made the table in the meantime :D

Code: Select all


R	C	ADC
100 0 94
104.95 12.67 644
109.93 25.48 1210
115.02 38.63 1777
120.02 51.6 2342
129.9 77.37 3440
140.27 104.65 4592
150.61 132.07 5728
160.37 158.16 6796
170.09 184.36 7853
180.04 211.4 8926
190.17 239.17 10012
199.95 266.21 11052
210.01 294.28 12120
220.04 322.51 13177
230.1 351.09 14220
239.9 379.2 15236

Post Reply