Merge pull request #38 from ryanvallieres/master

Debug Mode Hotfix

Author: jkreienh

.gitignore

@@ -0,0 +1 @@
+Built/

Source/Custom Device UDP-Custom-Device.xml

@@ -5,7 +5,7 @@
 		<eng>UDP Custom Device</eng>
 		<loc>UDP Custom Device</loc>
 	</AddMenu>
-	<Version>1.3.6</Version>
+	<Version>1.3.6a</Version>
 	<Type>Inline HW Interface</Type>
 	<MaxOccurrence>255</MaxOccurrence>
 	<MainPageGUID>1dbe19ca-57a1-40f3-b205-33efa5cbd18f</MainPageGUID>

Source/Engine/Debug Mode/Debug - Catch and Log.vi

@@ -22,7 +22,7 @@ Compile time: 0 minutes, 0 seconds
 
 
 
-Created c:\Data\GitHub\UDP Custom Device - Personal\Source\Help\UDP-Custom-Device.chm, 373,097 bytes
+Created c:\Data\GitHub\UDP Custom Device - Personal\Source\Help\UDP-Custom-Device.chm, 373,161 bytes
 
-Compression decreased file by 358,742 bytes.
+Compression decreased file by 358,949 bytes.
 

Source/Engine/Debug Mode/Debug - Initialize.vi

@@ -72,7 +72,7 @@ <h2>Configuration Summary</h2>
 				</tr>
 				<tr>
 					<td><STRONG>Debug Mode</STRONG></td>
-					<td>When active, logs verbose error messages to the Veristand console and default Veristand log file. Only errors are logged. Issues with opening duplex connections are current unhandled. Additionally, generates unique log files for the enabled packet. These log files can be found in the custom device directory on the target in the 'UDP_CD_Debug_Logs' directory. The custom device directory varies by target. These log files are unmanaged and should be manually cleaned-up or removed from the target upon completion of debug. Debug logs automatically begin overwriting old records after the file size has exceeded ~24MB. This caps the log file size around 24MB.<br><STRONG>NOTE:</STRONG> Debug mode sacrifices significant performance for thorough logging of errors. This includes receive packet timeouts and other potential error conditions.</td>
+					<td>When active, logs verbose error messages to the Veristand console and default Veristand log file. Only errors are logged. Issues with opening duplex connections are current unhandled. Additionally, generates unique log files for the enabled packet. These log files can be found in the custom device directory on the target in the 'UDP_CD_Debug_Logs' directory. The custom device directory varies by target.  The log file creation will be displayed at startup on the console. These log files are unmanaged and should be manually cleaned-up or removed from the target upon completion of debug. Debug logs automatically begin overwriting old records after the file size has exceeded ~24MB. This caps the log file size around 24MB.<br><STRONG>NOTE:</STRONG> Debug mode sacrifices significant performance for thorough logging of errors. This includes receive packet timeouts and other potential error conditions.</td>
 				</tr>
 				<tr>
 					<td><STRONG>New Data Options</STRONG></td>

Source/Help/Build CHM.log

@@ -88,7 +88,7 @@ <h2>Configuration Summary</h2>
 				</tr>
 				<tr>
 					<td><STRONG>Debug Mode</STRONG></td>
-					<td>When active, logs verbose error messages to the Veristand console and default Veristand log file. Only errors are logged. Issues with opening duplex connections are current unhandled. Additionally, generates unique log files for the enabled packet. These log files can be found in the custom device directory on the target in the 'UDP_CD_Debug_Logs' directory. The custom device directory varies by target. These log files are unmanaged and should be manually cleaned-up or removed from the target upon completion of debug. Debug logs automatically begin overwriting old records after the file size has exceeded ~24MB. This caps the log file size around 24MB.<br><STRONG>NOTE:</STRONG> Debug mode sacrifices significant performance for thorough logging of errors. This includes receive packet timeouts and other potential error conditions.</td>
+					<td>When active, logs verbose error messages to the Veristand console and default Veristand log file. Only errors are logged. Issues with opening duplex connections are current unhandled. Additionally, generates unique log files for the enabled packet. These log files can be found in the custom device directory on the target in the 'UDP_CD_Debug_Logs' directory. The custom device directory varies by target. The log file creation will be displayed at startup on the console. These log files are unmanaged and should be manually cleaned-up or removed from the target upon completion of debug. Debug logs automatically begin overwriting old records after the file size has exceeded ~24MB. This caps the log file size around 24MB.<br><STRONG>NOTE:</STRONG> Debug mode sacrifices significant performance for thorough logging of errors. This includes receive packet timeouts and other potential error conditions.</td>
 				</tr>
 				<tr>
 					<td><STRONG>Pointer Encoding</STRONG></td>

Source/Help/HTML Help Source/CD - Buffered Data Rx Packet.htm

@@ -70,7 +70,7 @@ <h2>Configuration Summary</h2>
 				</tr>
 				<tr>
 					<td><STRONG>Debug Mode</STRONG></td>
-					<td>When active, logs verbose error messages to the Veristand console and default Veristand log file. Only errors are logged. Issues with opening duplex connections are current unhandled. Additionally, generates unique log files for the enabled packet. These log files can be found in the custom device directory on the target in the 'UDP_CD_Debug_Logs' directory. The custom device directory varies by target. These log files are unmanaged and should be manually cleaned-up or removed from the target upon completion of debug. Debug logs automatically begin overwriting old records after the file size has exceeded ~24MB. This caps the log file size around 24MB.<br><STRONG>NOTE:</STRONG> Debug mode sacrifices significant performance for thorough logging of errors. This includes receive packet timeouts and other potential error conditions.</td>
+					<td>When active, logs verbose error messages to the Veristand console and default Veristand log file. Only errors are logged. Issues with opening duplex connections are current unhandled. Additionally, generates unique log files for the enabled packet. These log files can be found in the custom device directory on the target in the 'UDP_CD_Debug_Logs' directory. The custom device directory varies by target.  The log file creation will be displayed at startup on the console. These log files are unmanaged and should be manually cleaned-up or removed from the target upon completion of debug. Debug logs automatically begin overwriting old records after the file size has exceeded ~24MB. This caps the log file size around 24MB.<br><STRONG>NOTE:</STRONG> Debug mode sacrifices significant performance for thorough logging of errors. This includes receive packet timeouts and other potential error conditions.</td>
 				</tr>
 				<tr>
 					<td><STRONG>New Data Options</STRONG></td>

Source/Help/HTML Help Source/CD - Buffered Data Tx Packet.htm

@@ -78,7 +78,7 @@ <h2>Configuration Summary</h2>
 				</tr>
 				<tr>
 					<td><STRONG>Debug Mode</STRONG></td>
-					<td>When active, logs verbose error messages to the Veristand console and default Veristand log file. Only errors are logged. Issues with opening duplex connections are current unhandled. Additionally, generates unique log files for the enabled packet. These log files can be found in the custom device directory on the target in the 'UDP_CD_Debug_Logs' directory. The custom device directory varies by target. These log files are unmanaged and should be manually cleaned-up or removed from the target upon completion of debug. Debug logs automatically begin overwriting old records after the file size has exceeded ~24MB. This caps the log file size around 24MB.<br><STRONG>NOTE:</STRONG> Debug mode sacrifices significant performance for thorough logging of errors. This includes receive packet timeouts and other potential error conditions.</td>
+					<td>When active, logs verbose error messages to the Veristand console and default Veristand log file. Only errors are logged. Issues with opening duplex connections are current unhandled. Additionally, generates unique log files for the enabled packet. These log files can be found in the custom device directory on the target in the 'UDP_CD_Debug_Logs' directory. The custom device directory varies by target.  The log file creation will be displayed at startup on the console. These log files are unmanaged and should be manually cleaned-up or removed from the target upon completion of debug. Debug logs automatically begin overwriting old records after the file size has exceeded ~24MB. This caps the log file size around 24MB.<br><STRONG>NOTE:</STRONG> Debug mode sacrifices significant performance for thorough logging of errors. This includes receive packet timeouts and other potential error conditions.</td>
 				</tr>
 				<tr>
 					<td><STRONG>Transmit Options</STRONG></td>