Welcome
Username or Email:

Password:


Missing Code




[ ]
[ ]
Online
  • Guests: 83
  • Members: 0
  • Newest Member: omjtest
  • Most ever online: 396
    Guests: 396, Members: 0 on 12 Jan : 12:51
Members Birthdays:
No birthdays today

Next birthdays
05/14 hvguy (42)
05/14 thehappyelectron (15)
05/14 Justin (2025)
Contact
If you need assistance, please send an email to forum at 4hv dot org. To ensure your email is not marked as spam, please include the phrase "4hv help" in the subject line. You can also find assistance via IRC, at irc.shadowworld.net, room #hvcomm.
Support 4hv.org!
Donate:
4hv.org is hosted on a dedicated server. Unfortunately, this server costs and we rely on the help of site members to keep 4hv.org running. Please consider donating. We will place your name on the thanks list and you'll be helping to keep 4hv.org alive and free for everyone. Members whose names appear in red bold have donated recently. Green bold denotes those who have recently donated to keep the server carbon neutral.


Special Thanks To:
  • Aaron Holmes
  • Aaron Wheeler
  • Adam Horden
  • Alan Scrimgeour
  • Andre
  • Andrew Haynes
  • Anonymous000
  • asabase
  • Austin Weil
  • barney
  • Barry
  • Bert Hickman
  • Bill Kukowski
  • Blitzorn
  • Brandon Paradelas
  • Bruce Bowling
  • BubeeMike
  • Byong Park
  • Cesiumsponge
  • Chris F.
  • Chris Hooper
  • Corey Worthington
  • Derek Woodroffe
  • Dalus
  • Dan Strother
  • Daniel Davis
  • Daniel Uhrenholt
  • datasheetarchive
  • Dave Billington
  • Dave Marshall
  • David F.
  • Dennis Rogers
  • drelectrix
  • Dr. John Gudenas
  • Dr. Spark
  • E.TexasTesla
  • eastvoltresearch
  • Eirik Taylor
  • Erik Dyakov
  • Erlend^SE
  • Finn Hammer
  • Firebug24k
  • GalliumMan
  • Gary Peterson
  • George Slade
  • GhostNull
  • Gordon Mcknight
  • Graham Armitage
  • Grant
  • GreySoul
  • Henry H
  • IamSmooth
  • In memory of Leo Powning
  • Jacob Cash
  • James Howells
  • James Pawson
  • Jeff Greenfield
  • Jeff Thomas
  • Jesse Frost
  • Jim Mitchell
  • jlr134
  • Joe Mastroianni
  • John Forcina
  • John Oberg
  • John Willcutt
  • Jon Newcomb
  • klugesmith
  • Leslie Wright
  • Lutz Hoffman
  • Mads Barnkob
  • Martin King
  • Mats Karlsson
  • Matt Gibson
  • Matthew Guidry
  • mbd
  • Michael D'Angelo
  • Mikkel
  • mileswaldron
  • mister_rf
  • Neil Foster
  • Nick de Smith
  • Nick Soroka
  • nicklenorp
  • Nik
  • Norman Stanley
  • Patrick Coleman
  • Paul Brodie
  • Paul Jordan
  • Paul Montgomery
  • Ped
  • Peter Krogen
  • Peter Terren
  • PhilGood
  • Richard Feldman
  • Robert Bush
  • Royce Bailey
  • Scott Fusare
  • Scott Newman
  • smiffy
  • Stella
  • Steven Busic
  • Steve Conner
  • Steve Jones
  • Steve Ward
  • Sulaiman
  • Thomas Coyle
  • Thomas A. Wallace
  • Thomas W
  • Timo
  • Torch
  • Ulf Jonsson
  • vasil
  • Vaxian
  • vladi mazzilli
  • wastehl
  • Weston
  • William Kim
  • William N.
  • William Stehl
  • Wesley Venis
The aforementioned have contributed financially to the continuing triumph of 4hv.org. They are deserving of my most heartfelt thanks.
Forums
4hv.org :: Forums :: General Chatting
« Previous topic | Next topic »   

(Help) PCB etcher

Move Thread LAN_403
Conundrum
Thu Jun 24 2010, 07:26PM Print
Conundrum Registered Member #96 Joined: Thu Feb 09 2006, 05:37PM
Location: CI, Earth
Posts: 4062
Hi all.

Currently trying to get this pcb etcher working.

At the moment the main problem I am running into is the memory.
The current setup was a cd mechanism (for Y positioning) but this turned out to be too slow and noisy as well as having no easy way to fine tune the focus.

Now looking into using one of my (5 or so) laser printer mechanisms with the spinning mirror, and a second inline PS3 servo assembly to control the focus, with an LM317 as the constant current driver and a "current mirror" to keep the burner diode below threshold except when it is writing.

So far the plan is to detect the beam start/stop positions by using two blue LEDs then use this information to control the PWM which clocks the memory, writing 1/4 of the stored data at a time corresponding to successive lines.

Writing the data into the 23K256 occurs once on each rotation of the mirror at the start of the FG pulse so the overall worst case duty cycle is 50/50 and reduces the strain on the burner diode.

Simple in theory but the chip isn't reading or writing no matter what I send to it.
Its a 3.3V IC but in principle a simple resistive divider should work.

any ideas?

-Andre
(have a pile of ps3 blocks here if anyone has a use)

Back to top
hboy007
Thu Jun 24 2010, 09:47PM
hboy007 Registered Member #1667 Joined: Sat Aug 30 2008, 09:57PM
Location:
Posts: 374
ideas? I had this idea a year ago, now a 405nm laser diode, a laser printer assembly and some dichroitic beam splitter cubes are lying in the "paused projects" box because I can't find the time to finish this neat toy. My plan was to use a red pilot laser for pcb position detection (pre-scan the whole board for alignment, this makes double-sided boards very nice and simple once autopan/autorotate is implemented). The per-pixel line scan image information is recorded using a photodiode connected to the beam splitter cubes (I hope the reflections won't make this option impossible) and a segmented photodiode from a CD drive in combination with a long focal length (50mm f/8) triplet lens assembly outside to monitor a part of the beam to adjust the height.

Focussing isn't critical here, torerance is about +/-200µm for 20mil structures.

I use an ATMega32 with 512kB of external SRAM and ethernet connection (ENC28J60), the scanner unit slows down if the cached data runs out and resumes once the buffer is refilled. Just use a bigger parallel SRAM instead, many of them are 5V types. Keep the PS3 sleds for the cubes!

>>So far the plan is to detect the beam start/stop positions by using two blue LEDs

I do not understand what this would look like. The original design of the transfer drum scanner included a slit and a photodiode that generates both a time marker and a frequency feedback to check the polygon mirror operation - the photodiode is struck six times per revolution of the polygonal mirror. The polygon mirror driver phase-locks onto a given clock signal and the inertia of the rotor keeps the anglular velocity nice and smooth, the only downside with this would be that you'd have to stream the pixel data quite rapidly. Serial SRAMs are not the optimum for this task, I prefer parallel SRAM in combination with shift registers, this leaves more time for intermediate memory access.

as to the 23x256... did you get the access sequence right as described in the datasheet? Resistors for 5V->3V will work but better add some capacitors, too. Otherwise I'm not so sure if you can reach the desired clock speeds.

!Hold = HI?
!CS set correctly?
Back to top
Conundrum
Fri Jun 25 2010, 08:54PM
Conundrum Registered Member #96 Joined: Thu Feb 09 2006, 05:37PM
Location: CI, Earth
Posts: 4062
aaaugh!!!! no i did not add any capacitors.

Interesting to see you are working along the same lines, i will have to see if this approach will work with a PS3 laser block (it has a neat focus and fine tuning servo to boot)

as for measuring the height, one way might be a spot imager using an optical mouse sensor (the adns2051) or small cmos camera.. this is used on some printers to allow ultra-fine images to be printed.

re. access sequence, i will check. i know about hold but this might not be the only problem.
Confirmed it wasn't unstable power by using a lifepo4 cell.
Back to top

Moderator(s): Chris Russell, Noelle, Alex, Tesladownunder, Dave Marshall, Dave Billington, Bjørn, Steve Conner, Wolfram, Kizmo, Mads Barnkob

Go to:

Powered by e107 Forum System
 
Legal Information
This site is powered by e107, which is released under the GNU GPL License. All work on this site, except where otherwise noted, is licensed under a Creative Commons Attribution-ShareAlike 2.5 License. By submitting any information to this site, you agree that anything submitted will be so licensed. Please read our Disclaimer and Policies page for information on your rights and responsibilities regarding this site.