Are they the same part number? Same manufacturer?
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
why on these 2 blocks and not the other 26? baffled
greg - Philadelphia & Reading / Reading
It could be that the bridge rectifiers are not fast enough to deal with DCC frequency. Instead of a canned bridge, you might have to use a set of fast switching diodes and make your own, although there are fast enough bridges out there.
adding a 0.1 uF cap across the bridge fixed 8 of 10 blocks. tried 2 different type caps (ceramic disc, polyester) thinking first damaged by heat.
measured ~0.7VAC across bridge of one detector falsely active, as low as ~0.012VAC across others not having any problems.
still unclear what signal (noise) is the cause of the problem on these larger blocks. must be higher in frequency than ~10kHz DCC for cap to supress.
we plan to look again at resistance across rails and wiring, as well as trying different detection circuits.
Probably keeps noise and spikes from false triggering with that capacitor.
we completed more of the detector wiring. all of the longer blocks were active w/o occupancy.
the circuit we're using does not have the 0.1uF cap across the output of the bridge that is shown in the NMRA circuit (see full featured)
i have my guess. wondering what other may think
it could be components just on that board. three circuits seem to have the same problem while 6 others on different boards do not. will know when other circuits are wired
Bad bridge rectifier, or conencted to the wrong side? Or maybe the 33 ohm resistor in the opto. Or just a failing opto, or out of spec and turning on the transistor with much less brightness. Or maybe it's within spec and just near one side instead of being more to the center.
i will check, but while capacitor and resistor size could possibly make the detector less sensitive, i don't see how their values can make a detector more sensitive.
the detector requires a voltage across the bridge and sufficient current to turn on the opto transistor repeatedly to keep the capacitor drained. what is the source if there's nothing across the rails?
Trying to figure out what would make it more sensitive. The goofy one - check the 10uF cap, make sure it's not damaged and/or leaking. And is the pullup the 120K shown on the schematic, and not a 12K, or 1.2M?
we found that using 2 spare detectors on a different board solved the immediate problem.
not sure what the issue is with that particular board
i have toroids. I could try putting one on the bus wire near the detector
How are they run relative to the others which work fine? Near any other wiring?
"Tried a different detection circuit known to work" - so you swapped the detector on this line with another one, with the same false detection?
Maybe it's being overly sensitive due to something with the bus/feeder wiring. You can reduce that a little with a .01uF cap across the diode bridge (between the DCC input for the detected rail and the track output for the detected rail). I've seen that in other schematics as an option to reduce noise sensitivity. You can go as high as .1uF if .01 doesn't work.
no
why just some blocks?
Key is the point where you said it falsely detects with the track feeders disconnected by touching one of the bus wires. You're getting either an inductive load (are the bus wires twisted?) or a capacitive load.
having a problem with detectors constantly active (indicating occupancy) when no train is in the block.
we're using the NMRA type of current detection circuit which is in series with one of the rails. A sufficient current creates a voltage (2 diode drops) across a bridge rectifier which is sufficent to drive a current thru an opto, that drains the charge on a capacitor. The 555 is used as a Schmitt trigger that is active when the capacitor voltage is < 1/3 Vcc and deactivates when the capacitor is allowed to recharge, > 2/3 Vcc, when the block is no longer occupied and no longer drawing current.
we're wiring up staging loops that will eventually be hidden, covered by a 2nd set of loops. the loops are divided into 2 sets, one w/ 2 tracks and the other w/ 3 tracks. each loop is intended to store 2 trains and the storage portion has 4 blocks, a long and a short block that can be switched off to automatically stop the train.
the problem blocks are the 2 blocks with 2 turnouts each (4,5 and 2,3) connecting the violet, orange and blue tracks.
has anyone had a similar problem?
any thoughts?