Welcome
Username or Email:

Password:


Missing Code




[ ]
[ ]
Online
  • Guests: 79
  • Members: 0
  • Newest Member: omjtest
  • Most ever online: 396
    Guests: 396, Members: 0 on 12 Jan : 12:51
Members Birthdays:
All today's birthdays', congrats!
Mathias (41)
slash128v6 (52)


Next birthdays
02/01 Barry (70)
02/01 Snowcat (37)
02/01 wylie (43)
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 :: Tesla Coils
« Previous topic | Next topic »   

Reliable, stable, Toslink RX problem.

Move Thread LAN_403
Dylan
Fri Aug 01 2008, 04:30AM Print
Dylan Registered Member #1024 Joined: Sun Sept 23 2007, 10:56AM
Location: Northern NSW, Australia
Posts: 95
I am currently tacking this problem, and have a question, but first some background.

I am using a TORX177 reciever, the state of which is undefined when no pulse train is incoming.
Whilst the RX does seem stable at low with a stable (high or low) dc input, it does let out a 20us pulse high approx 20us after the end of any pulse train 'burst'.
I currently am driving the RX with a 3.6Mhz modulated pulse for my interrupter ontime burst.
I am therefore simply using a re-triggerable monostable set to a pulse out time of approx 30us to reliably square up the signal, and cover this spurious pulse.
This however means the minimum burst time is close to 90us once other delays are added (won't go into it in too much detail).
What I really want is a minimum burst time of about 20us.

So it seems a constant pulse train is the way to drive the TORX177, thereby giving you down to approx 4Mhz burst resolution (not sure the max RX frequency of the TORX177).

Therefore my intention is to send it a constant pulse train , alternating between approx 1.8Mhz (for logic low), and 3.6Mhz (for logic high). And decode these two pulse trains somehow.

This setup should also make the RX less succeptable to noise, at least noise below 3.6Mhz., whereas currently ANY noise during burst off time will cause a minimum 30us high signal.

My question is :
What would be the simplest , fastestest , most reliable way to detect a minimum frequency (approx 3.6Mhz)?
A simple frequency to voltage RC circuit seems unlikely to be stable and reliable.
A PLL chip detector circuit seems like overkill.
Perhaps someone knows of a small , simple , frequency to volatge chip?

Basically I need a simple circuit that will go high when fed with a minimum (say 3.6Mhz) signal, and otherwise be low.

All ideas welcome!

============= EDIT ==============
May have answered my own question:
Keep my retriggerable monostable, set it to a pulse duration of just over 8 cycles at 3.6mhz , use this pulse to drive the reset of a decade counter (clocked with the Toslink signal) and take output from counter at 8th count pin.
I've got the parts so looks like I'll do this , but any other suggestions still welcome.


============= EDIT ============
Nope , that idea is rubbish it would need to be a non-retriggerable monostable. smile
Back to top
Steve Conner
Fri Aug 01 2008, 11:39AM
Steve Conner Registered Member #30 Joined: Fri Feb 03 2006, 10:52AM
Location: Glasgow, Scotland
Posts: 6706
Answer: Use a different Toslink receiver Link2 according to Reaching in this thread, some have a defined output in the absence of an input
Back to top
Dylan
Sat Aug 02 2008, 06:52AM
Dylan Registered Member #1024 Joined: Sun Sept 23 2007, 10:56AM
Location: Northern NSW, Australia
Posts: 95
Well Blow me down!
Thanks, I had not read my datasheets properly before ordering!
To quote from the TORX173 datasheet:
"High level output when optical flux is received. Low level output when optical flux is not received"

Simple.

To quote from the TORX177 datasheet:
"When modulated optical high level signal is received, output signal is high.
When modulated optical low level signal is received, output signal is low.
When non- modulated signal (optical all high or all low level signal) is inputted, output signal is not stable."

Mmm , not so simple.

I guess the moral is read the datasheets smile

And for interrupter signal sending , BUY THE TORX173 .

Excellent , thanks for pointing that out Dr C , I had read that thread , but had overlooked that small and vital portion.
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.