From: <jac...@us...> - 2013-03-22 19:28:11
|
Revision: 3054 http://openlcb.svn.sourceforge.net/openlcb/?rev=3054&view=rev Author: jacobsen Date: 2013-03-22 19:28:02 +0000 (Fri, 22 Mar 2013) Log Message: ----------- Gather info on time protocol all in once place, the new WN Modified Paths: -------------- trunk/documents/index.html trunk/specs/index.html Added Paths: ----------- trunk/specs/drafts/GenTimeProtocolWN.odt trunk/specs/drafts/GenTimeProtocolWN.pdf Removed Paths: ------------- trunk/documents/notes/FastClock.html trunk/specs/drafts/GenTimeProtocolS.odt trunk/specs/drafts/GenTimeProtocolTN.odt Modified: trunk/documents/index.html =================================================================== --- trunk/documents/index.html 2013-03-22 19:27:16 UTC (rev 3053) +++ trunk/documents/index.html 2013-03-22 19:28:02 UTC (rev 3054) @@ -110,8 +110,6 @@ <LI><P STYLE="margin-bottom: 0cm">Early proposal for a general-purpose <A HREF="ReservationProtocol.html">Reservation Protocol</A>.</P> - <LI><P STYLE="margin-bottom: 0cm">Note on possible - <A HREF="notes/FastClock.html">Fast Clock</A> support.</P> </UL> <LI><P><SPAN STYLE="font-weight: normal">NMRA 2010 Convention <A HREF="NMRA2010demo/index.html">Demo Notes and Diagrams</A></SPAN></P> Deleted: trunk/documents/notes/FastClock.html =================================================================== --- trunk/documents/notes/FastClock.html 2013-03-22 19:27:16 UTC (rev 3053) +++ trunk/documents/notes/FastClock.html 2013-03-22 19:28:02 UTC (rev 3054) @@ -1,93 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> -<HTML> -<HEAD> - <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8"> - <TITLE>OpenLCB Note: Display Protocol</TITLE> - <META NAME="GENERATOR" CONTENT="OpenOffice.org 3.4.1 (Unix)"> - <STYLE TYPE="text/css"> - <!-- - H2.cjk { font-family: "SimSun" } - H2.ctl { font-family: "Lucida Sans" } - H3.cjk { font-family: "SimSun" } - H3.ctl { font-family: "Lucida Sans" } - --> - </STYLE> -</HEAD> -<BODY LANG="en-US" DIR="LTR"> -<H1>OpenLCB Note: Fast Clocks</H1> -<P>OpenLCB can carry traditional layout fast-clock information in -Events, allowing both display (for people) and Consumers to react -(for automated controls).</P> -<H2 CLASS="western">Environment of Proposal</H2> -<H3 CLASS="western">Requirements</H3> -<P>Must be able to carry the fast time to second resolution. -</P> -<H3 CLASS="western">Preferences</H3> -<P>Should still work if an implementation needs to send only minute -resolution, e.g. to reduce traffic.</P> -<H3 CLASS="western">Design Points</H3> -<P>Time is sent as “time within today” so that consumers can be -taught to react to time-of-day. Date is handled separately.</P> -<H2 CLASS="western">Proposed Protocol</H2> -<H3 CLASS="western">Time Event ID format</H3> -<P>A FastClock Time-event is sent every second as [fast_clock_prefix -hh mm ss], with the hours/minutes/seconds encoded in bytes</P> -<H3 CLASS="western">Control Event ID format</H3> -<P>A FC SetRate-event is sent every (10?) seconds as -[fast_clock_prefix FC|r rr]</P> -<P>A FC SetTime-event is [fast_clock_prefix hh+60 mm]</P> -<P>(The coding for these needs to be explained in more detail)</P> -<P>If a FC Time-event is received, it is ignored. -</P> -<P>If a FC SetTime event is received, the FC time is set to it. -</P> -<P>If a FC SetRate-event is received, the rate is set to the rate -embedded in the event. -</P> -<P>Rate is fixed point rrrrrrrrrr.rr, 0.00, 0.25, 0.50, ..., 999.75</P> -<H3 CLASS="western">Use of Blue/Gold to configure</H3> -<P STYLE="margin-bottom: 0cm">The User Interface (UI) uses the Blue / -Gold buttons:</P> -<UL> - <LI><P>A (Blue/Gold)+ sequence Sets or Nominates the Time, Rate or - Alarms to learn a Teach-event. - </P> - <LI><P>Gold(Blue/Gold)+ sequence sends a Teach-event which includes - the event associated with the current-Time, the Rate-, or any of the - Alarms. - </P> -</UL> -<H2 CLASS="western">Examples</H2> -<P><BR><BR> -</P> -<H2 CLASS="western">Remaining Points</H2> -<P>Does the prefix need to have space in it (a byte?) to identify one -of N clocks?</P> -<P>Alarms? Should we define a separate set of events that are “this -time is special”? Any event ID could be produced by any node, upon -receipt of the particular time event, and don't have to be part of -this protocol. Is something specific for alarms useful, or just -redundancy?</P> -<P>The Arduino clockDisplay example says it contains:</P> -<UL> - <LI><P>Eight alarms, each can send a FC Alarm-event at its - associated FC Time.</P> -</UL> -<UL> - <LI><P>If a FC Alarm-event is received, the clock is set to the time - associated with that Alarm.</P> -</UL> -<P><BR><BR> -</P> -<P>The use of the same event to <U>broadcast</U> the rate and to <U>set</U> -the rate really needs to be revisited. Is that consistent with event -semantics? Or should a “rate set event” do the set and cause the -clock source to emit a “current rate” event?</P> -<HR> -<P>Site hosted by <FONT COLOR="#000080"> -<A HREF="http://sourceforge.net/projects/openlcb"><FONT COLOR="#000080"><IMG SRC="http://sflogo.sourceforge.net/sflogo.php?group_id=286373&type=13" NAME="graphics1" ALIGN=ABSMIDDLE WIDTH=120 HEIGHT=30 BORDER=2></FONT></A></FONT> -</P> -<P>This is SVN $Revision$ -</P> -</BODY> -</HTML> \ No newline at end of file Deleted: trunk/specs/drafts/GenTimeProtocolS.odt =================================================================== (Binary files differ) Deleted: trunk/specs/drafts/GenTimeProtocolTN.odt =================================================================== (Binary files differ) Copied: trunk/specs/drafts/GenTimeProtocolWN.odt (from rev 3051, trunk/specs/drafts/TemplateWN.odt) =================================================================== (Binary files differ) Added: trunk/specs/drafts/GenTimeProtocolWN.pdf =================================================================== (Binary files differ) Property changes on: trunk/specs/drafts/GenTimeProtocolWN.pdf ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Modified: trunk/specs/index.html =================================================================== --- trunk/specs/index.html 2013-03-22 19:27:16 UTC (rev 3053) +++ trunk/specs/index.html 2013-03-22 19:28:02 UTC (rev 3054) @@ -86,18 +86,12 @@ </TR> <TR VALIGN=TOP> <TD COLSPAN=3 WIDTH=60%> - <P>Train Control Protocol [<A HREF="../documents/notes/TrainControlProtocol.html">dev - note</A>]</P> - <P>Display Protocol [<A HREF="../documents/notes/DisplayProtocol.html">dev - note</A>]</P> - <P>Remote Button Protocol [prelim TN (<A HREF="drafts/GenButtonTN.pdf">.pdf</A>)(<A HREF="drafts/GenButtonTN.odt">.odt</A>)] - </P> - <P>Ident Method [<A HREF="../documents/notes/IdentMethod.html">dev - note</A>]</P> - <P>Event Teaching/Learning Protocol [<A HREF="../documents/TeachLearnConfigProtocol.html">dev - note 1</A>] [<A HREF="../documents/examples/BlueGoldConfig.html">dev - note 2</A>] [<A HREF="../documents/examples/EventConfigurationProtocol.html">dev - note 3</A>]</P> + <P>Time Broadcast Protocol [Working Note (<A HREF="drafts/GenTimeProtocolWN.pdf">.pdf</A>)(<A HREF="drafts/GenTimeProtocolWN.odt">.odt</A>)]</P> + <P>Train Control Protocol [<A HREF="../documents/notes/TrainControlProtocol.html">dev note</A>]</P> + <P>Display Protocol [<A HREF="../documents/notes/DisplayProtocol.html">dev note</A>]</P> + <P>Remote Button Protocol [prelim TN (<A HREF="drafts/GenButtonTN.pdf">.pdf</A>)(<A HREF="drafts/GenButtonTN.odt">.odt</A>)]</P> + <P>Ident Method [<A HREF="../documents/notes/IdentMethod.html">dev note</A>]</P> + <P>Event Teaching/Learning Protocol [<A HREF="../documents/TeachLearnConfigProtocol.html">dev note 1</A>] [<A HREF="../documents/examples/BlueGoldConfig.html">dev note 2</A>] [<A HREF="../documents/examples/EventConfigurationProtocol.html">dev note 3</A>]</P> <HR> <P>Abbreviated Configuration Description Information [prelim Std (<A HREF="drafts/GenAcdiS.pdf">.pdf</A>)(<A HREF="drafts/GenAcdiS.odt">.odt</A>)] This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |