-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DCCPacketScheduler::opsVerifyCV() #17
Comments
That's a great idea. However, verifying ops mode writes—if I recall correctly—requires RailCom hardware, for which I don't have a design or prototype to test this kind of thing. I'm not at all opposed to your proposal, as I want to start exploring RailCom, but I'm curious if you have a proposal for an easy to build hardware accessory to support ops verifies? |
I must admit that I'm only becoming familiar with the DCC protocol now for my CalcDCC project; my previous experience has all been with DC control. I do have EE experience, though, so I'll explore what this would require and get back to you. |
If you haven't, you should have a look here: http://www.nmra.org/sites/default/files/s-9.3.2_2012_12_10.pdf |
Looks reasonable enough. I suspect their circuit is unnecessarily complex for a first iteration, since it precisely detects decoder responses only within the spec. An alternative, much simpler design looks worth a try to me: http://usuaris.tinet.cat/fmco/dccgen_en.html#ack . If I can find an optoisolator lying around my parts box, I'll give it a try. |
Nice find! I look forward to hearing your results! Don't forget you'll need a RailCom-capable detector (most TCS decoders have it as an un-advertised feature) |
I'm sure it's something you've considered, but support for a DCCPacketScheduler::opsVerifyCV() method to match DCCPacketScheduler::opsProgramCV() would be great. Let me know if I can help. TIA!
The text was updated successfully, but these errors were encountered: