Difference between revisions of "OpenFlexure"

From Microwiki
Jump to: navigation, search
Line 7: Line 7:
 
Travel range
 
Travel range
  
* Block stage: 2x2x2mm
+
*Block stage: 2x2x2mm
* Delta stage: 12x12x4mm
+
*Delta stage: 12x12x4mm
  
 +
<br />
 
==Reception==
 
==Reception==
 
BreakingTaps
 
BreakingTaps

Revision as of 22:55, 25 August 2022

Material?

  • PLA is more standard, PETG is more flexible
  • McMaster: printing in PLA since its what I have


Travel range

  • Block stage: 2x2x2mm
  • Delta stage: 12x12x4mm


Reception

BreakingTaps


gekkio

  • I don't mind being named, but my comments should have a disclaimer that my setup is pretty poor and some problems might be self-caused instead of being OpenFlexure's fault 😅
  • my main goal is to get it working well with a 40x objective, but it has proven to be quite challenging:
  • - my setup is pretty poor and cheap, and the stage and the sample are always tilted slightly. Calibration can alleviate this problem, but it's annoying how much this affects focus when using that 40x objective
  • - the stage O-rings break quite often...there was a thread on the OF forums about O-ring sizing and material choices, and I bought some alternatives that I just haven't yet had time to test
  • - repeatability seems poor and drift seem quite high, at least with that 40x objective. I was hoping that going bipolar and using a better driver board would fix this, but I'm still not seeing great results. Maybe the stage itself is the limiting factor now. Or maybe I've just been unlucky with O-rings and have always had at least one broken 😅 it's not immediately obvious when an O-ring is breaks, so this is actually a plausible explanation
  • - temperature seems to affect things too. When the motors heat up, it seems like the plastic is affected, which is probably the cause for some of the problems
  • oh yeah, and one thing about repeatability: it depends on the move directions. If I move back and forth using just one motor as a test, I get better repeatability than if I choose every time a random direction and move back and forth to/from it. In practice this means every move will slightly affect the next one...I'm not sure if this is just about backlash, or if the stage itself has something to do with it


F

  • it was a size problem. The whole thing would fit on my first Amscope if I removed the bottom illumination lens, but then I never found a proper way to hold it in place at the right height. I'm limited to 3D printing (no tools to make aluminum parts), so I just gave up and went for the ready-made aliexpress stages.


onilink_

  • Yeah I got some bad returns too about openflexure (vibration, slow, not precise enough). I had bought all the parts and was planning to build one but I stopped.

Motor control

GRBL

Can convert the motors from unipolar to bipolar to be compatible with more standard motor controllers

Procedure

  • Gently pop off blue cover
  • Cut middle PCB trace
    • https://twitter.com/johndmcmaster/status/1562535251968045057?s=20&t=PJqUpSjrx6IMwXh-XUHDFw
  • Unsolder all 5 leads and remove the connector
  • Solder GRBL controller compatible wires onto the 4 outer termianls
    • Keep the cable order


Testing via pyuscope

  • ./test/grbl/g1.py 'G91 Z5.0 F100'
    • ok
  • ./test/grbl/g1.py 'G91 Z5.0 F200'
    • missing steps

Block Stage

https://openflexure.gitlab.io/openflexure-block-stage/

McMaster BOM


General notes

  • Printing
  • Using Arduino shield: Electreim 28BYJ-48 5V ULN2003A JST Stepper Motor Driver Shield for Arduino Nano
    • Basically compatible with Sangaboard. Motor direction might be reversed
    • More info here: https://openflexure.discourse.group/t/is-this-like-the-sangaboard/776/12


Compiling / flashing software

  • https://kitspace.org/boards/gitlab.com/bath_open_instrumentation_group/sangaboard/sangaboard_v0.4/
  • Open Arduino sketch
    • .ino file
  • Select Arduino Nano Every board (under second board menu)
  • Build
    • You'll get warnings about emulated instruction set, ignore
  • Flashing using Arduino ISP
    • "avrdude: jtagmkII_initialize(): Cannot locate "flash" and "boot" memories in description" essentially means success


Test software

  • Open serial port
    • ex: screen /dev/ttyACM0 115200
  • type "help" and press enter


Sample output:

Sangaboard Firmware v0.5.1
Type 'help' for a list of commands.
Type 'help' for a list of commands.

Board: Sangaboard v0.2

Sangaboard Firmware v0.5.1

Commands (terminated by a newline character):
mrx <d>                        - relative move in x
mry <d>                        - relative move in y
mrz <d>                        - relative move in z
mr <d> <d> <d>                 - relative move in all 3 axes
release                        - de-energise all motors
p?                             - print position (3 space-separated integers
ramp_time <d>                  - set the time taken to accelerate/decelerate in us
min_step_delay <d>             - set the minimum time between steps in us.
dt <d>                         - set the minimum time between steps in us.
ramp_time?                     - get the time taken to accelerate/decelerate in us
min_step_delay?                - get the minimum time between steps in us.
zero                           - set the current position to zero.
test_mode <s>                  - set test_mode <on> <off>
version                        - get firmware version string

Input Key:
<d>                            - a decimal integer.

--END--

Ran command "mrx 10" to start testing movement

Motor test: https://www.youtube.com/watch?v=kvwJRnc8nQo