Differences

This shows you the differences between two versions of the page.

--- public:vag [2019/07/19 10:31] – [Next Meeting] uppermill
+++ public:vag [2019/08/13 10:53] – uppermill
@@ Line 2: / Line 2: @@
 ^  Next Meeting  ^
-|**<color red>There are <COUNTDOWN:10:00 2019-08-13|the next Virtual Meeting (10:00 BST on 13-August-2019)></color>** |
+|**<color red>There are <COUNTDOWN:10:00 2019-08-27|the next Virtual Meeting (10:00 BST on 27-August-2019)></color>** |
 ===== MERG Virtual Area Group =====
@@ Line 47: / Line 47: @@
 ==== Next Meeting ====
-**<color red>There are <COUNTDOWN:10:00 2019-08-13|the next Virtual Meeting (10:00 BST on 13-August-2019)></color>**
+**<color red>There are <COUNTDOWN:10:00 2019-08-27|the next Virtual Meeting (10:00 BST on 27-August-2019)></color>**
 The proposed agenda is as  follows
-=== 9th July ===
+=== 27th August ===
 ^Item^Leader^Minutes^Notes^
 |  Future Topics|Discussion|  5  |Initial discussion while members join the call|
-|  Signalling Objects for CBUS|Dave Turner|  55  |The aims of this White Paper are as follows|
+|  Station Destination Boards|Discussion|  45  |An opportunity to discuss hardware and messaging systems|
-|:::|:::|:::|1 To make configuration and documentation of an interlocked system easier|
+|  Burning Topics|Discussion|  10  |Does anybody need some help?|
-|:::|:::|:::|2 To add the following higher level functionality to the existing CBUS messaging system|
-|:::|:::|:::| - System initialisation|
-|:::|:::|:::| - Interlocking of modelled signalling items|
-|:::|:::|:::| - Route reservation, locking and release|
-|:::|:::|:::| - Reporting  of operational errors|
 Once you have confirmed with the leader that you wish to participate, you will receive a reminder email on the day before the call and a second email 10 minutes before the call with a link to enable you to join the call.
@@ Line 76: / Line 71: @@
 I've scheduled some discussions over the holiday season so that we can deal more easily with fluctuation numbers of participants.
-=== 13th August ===
-^Item^Leader^Minutes^Notes^
-|  Future Topics|Discussion|  5  |Initial discussion while members join the call|
-|  DC Control|Discussion|  45  |An opportunity to discuss the forgotten world of DC control|
-|  Burning Topics|Discussion|  10  |Does anybody need some help?|
-=== 27th August ===
-^Item^Leader^Minutes^Notes^
-|  Future Topics|Discussion|  5  |Initial discussion while members join the call|
-|  Station Destination Boards|Discussion|  45  |An opportunity to discuss hardware and messaging systems|
-|  Burning Topics|Discussion|  10  |Does anybody need some help?|
 === 10th September ===
@@ Line 122: / Line 107: @@
 ==== Previous Meetings in 2019 ====
+=== 13th August ===
+^Item^Leader^Minutes^Notes^
+|  Future Topics|Discussion|  5  |Initial discussion while members join the call|
+|  DC Control|Discussion|  45  |An opportunity to discuss the forgotten world of DC control|
+|  Burning Topics|Discussion|  10  |Does anybody need some help?|
+=== 9th July ===
+^Item^Leader^Minutes^Notes^
+|  Future Topics|Discussion|  5  |Initial discussion while members join the call|
+|  Signalling Objects for CBUS|Dave Turner|  55  |The aims of this White Paper are as follows|
+|:::|:::|:::|1 To make configuration and documentation of an interlocked system easier|
+|:::|:::|:::|2 To add the following higher level functionality to the existing CBUS messaging system|
+|:::|:::|:::| - System initialisation|
+|:::|:::|:::| - Interlocking of modelled signalling items|
+|:::|:::|:::| - Route reservation, locking and release|
+|:::|:::|:::| - Reporting  of operational errors|
 === 25th June ===