Route Table - Revision history

Steve Cable: /* Route */

2019-01-10T20:50:45Z

‎Route

2019-01-10T20:25:20Z

2019-01-10T20:23:43Z

2019-01-10T20:23:12Z

‎Introduction

2019-01-10T20:22:20Z

2019-01-10T20:21:40Z

‎Var

2019-01-10T20:20:22Z

‎Input

2019-01-10T20:20:09Z

‎Input

2019-01-10T20:19:52Z

2019-01-10T20:17:48Z

@@ Line 72: / Line 72: @@
 The fifth element (0 or 1) specifies if the data is to be sent in a packed data format or using a NADS specific data protocol (which has not been fully implemented). ''In general use terms, this should be set to "1".''
 Next is a list of devices. The devices are specified as above and will appear in the order as they are specified. An “i” serves as the delineation between <html><span style="font-weight:bold; color:#436882;">outputs</span></html> and <html><span style="font-weight:bold; color:#84619e;">inputs</span></html>. (No "i" character is necessary if there are no inputs required.)
-−
-For the above example the address 192.168.100.3 would be sent a UDP datagram on port 4001 with three 32 bit integers at the rate of 60 Hz. Additionally, the miniSim would also listen locally on port 4000 for a UDP datagram consisting of three 32 bit integers.
 When multiple devices are selected and packed is also specified no padding will appear between variables in the data load.
+For the above example the address 192.168.100.3 would be sent a UDP datagram on port 4001 with three 32 bit integers at the rate of 60 Hz. Additionally, the miniSim would also listen locally on port 4000 for a UDP datagram consisting of three 32 bit integers.
 ==Code Examples==
 Coming soon

@@ Line 1: / Line 1: @@
 ==Introduction==
-The Route Table for the NADS miniSim provides the functionality for forwarding cell data over UDP “datagrams” to a specified location. The datagrams are sent at 60 Hz. The route table is specified by the '''routeTable.txt''' file. This file must exist in the “''miniSim_install_directory''\bin.x64” directory; if the file does not exist the miniSim will operate normally, although no data will be forwarded or recorded.
+The Route Table for the NADS miniSim provides the functionality for forwarding cell data over UDP “datagrams” to a specified location. The datagrams are sent at 60 Hz. The route table configuration is specified by the '''routeTable.txt''' file. This file must exist in the “''miniSim_install_directory''\bin.x64” directory; if the file does not exist the miniSim will operate normally, although no data will be forwarded or recorded.
 ==Structure==

@@ Line 1: / Line 1: @@
 ==Introduction==
-The Route Table for the NADS miniSim provides the functionality for forwarding cell data over UDP “datagrams” to a specified location. The datagrams are sent at 60 Hz. The route table is specified by the routeTable.txt file. This file must exist in the “''miniSim_install_directory''\bin.x64” directory; if the file does not exist the miniSim will operate normally, although no data will be forwarded or recorded.
+The Route Table for the NADS miniSim provides the functionality for forwarding cell data over UDP “datagrams” to a specified location. The datagrams are sent at 60 Hz. The route table is specified by the '''routeTable.txt''' file. This file must exist in the “''miniSim_install_directory''\bin.x64” directory; if the file does not exist the miniSim will operate normally, although no data will be forwarded or recorded.
 ==Structure==

@@ Line 1: / Line 1: @@
 ==Introduction==
-The Route Table for the NADS miniSim provides the functionality for forwarding cell data over UDP “datagrams” to a specified location. The datagrams are sent at 60 Hz. The route table is specified by the routetable.txt file. This file must exist in the “''miniSim_install_directory''\bin.x64” directory; if the file does not exist the miniSim will operate normally, although no data will be forwarded or recorded.
+The Route Table for the NADS miniSim provides the functionality for forwarding cell data over UDP “datagrams” to a specified location. The datagrams are sent at 60 Hz. The route table is specified by the routeTable.txt file. This file must exist in the “''miniSim_install_directory''\bin.x64” directory; if the file does not exist the miniSim will operate normally, although no data will be forwarded or recorded.
 ==Structure==

@@ Line 34: / Line 34: @@
 “FrameNum” is a special variable that does not have to be listed in the cec file, it will provide the current frame number. This is the same frame number that will appear in the daq file.
 ===Device===
@@ Line 60: / Line 61: @@
 The input section is for specifying cells the route table is to write to. The cells are written to just as data sent to the miniSim. The first element is the ID, this will be used by the route section. The var, element specifies the varaible name, this cell must exist in the cell table. The offset is in bytes as specifies offset into the cell the data is written. The size specifies how much data in written. If we wanted to write to a cell that was a single integer we would use 0 and 4 for the offset and size.
 ===Route===

@@ Line 31: / Line 31: @@
 'c': 8 bit character
-The last element on the line is the size, this is the number of elements in the cell, in the above example SCC_Audio_Trigger is a single integer.
+The last element on the line is the size, this is the number of elements in the cell, in the above example AUX_CACC_Engage is a single integer.
 “FrameNum” is a special variable that does not have to be listed in the cec file, it will provide the current frame number. This is the same frame number that will appear in the daq file.
 ===Device===

@@ Line 57: / Line 57: @@
 ===Input===
 <blockquote>
-<id> <var name> <offset> <size>
+<id> <varname> <offset> <size>
 </blockquote>