ARDUINO MEGA Functions Debug - Revision history

Bfeher at 20:48, 11 May 2012

2012-05-11T20:48:12Z

2012-05-11T20:34:44Z

2012-05-11T20:34:21Z

2012-05-11T20:33:49Z

2012-05-11T20:32:32Z

2012-05-11T20:31:59Z

2012-05-11T20:31:31Z

2012-05-10T19:52:48Z

2012-05-10T19:51:11Z

getAvailSpaceInDebugStream

2012-05-10T01:03:00Z

version

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:2560 (MEGA) Debug}}
+{{DISPLAYTITLE:2560 (MEGA) Debug Functions}}
 <yambe:breadcrumb self="2560 (MEGA) Debug">ARDUINO_MEGA_Functions_and_Variables|Functions and Variables</yambe:breadcrumb>
 <br />

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:2560 Debug}}
+{{DISPLAYTITLE:2560 (MEGA) Debug}}
-<yambe:breadcrumb self="Debug">ARDUINO_MEGA_Functions_and_Variables|Functions and Variables</yambe:breadcrumb>
+<yambe:breadcrumb self="2560 (MEGA) Debug">ARDUINO_MEGA_Functions_and_Variables|Functions and Variables</yambe:breadcrumb>
 <br />

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:Debug}}
+{{DISPLAYTITLE:2560 Debug}}
 <yambe:breadcrumb self="Debug">ARDUINO_MEGA_Functions_and_Variables|Functions and Variables</yambe:breadcrumb>
 <br />

@@ Line 2: / Line 2: @@
 <yambe:breadcrumb self="Debug">ARDUINO_MEGA_Functions_and_Variables|Functions and Variables</yambe:breadcrumb>
 <br />
 The debugger in ROBOTC allows you to see all of your sensor, motor and variables while running your program. ROBOTC also has a debug terminal called the "Debug Stream" that you can use to output a terminal-like stream of information to have an additional way to monitor your program.

@@ Line 1: / Line 1: @@
-{{DISPLAYTITLE:"debug"}}
+{{DISPLAYTITLE:Debug}}
 <yambe:breadcrumb self="Debug">ARDUINO_MEGA_Functions_and_Variables|Functions and Variables</yambe:breadcrumb>
 <br />

← Older revision		Revision as of 20:31, 11 May 2012
Line 1:		Line 1:
		+	{{DISPLAYTITLE:"debug"}}
	<yambe:breadcrumb self="Debug">ARDUINO_MEGA_Functions_and_Variables\|Functions and Variables</yambe:breadcrumb>		<yambe:breadcrumb self="Debug">ARDUINO_MEGA_Functions_and_Variables\|Functions and Variables</yambe:breadcrumb>
	<br />		<br />

@@ Line 102: / Line 102: @@
 <br />
-== bFloatConversionErrors==
+== bFloatConversionErrors ==
 {| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
 |-
@@ Line 108: / Line 108: @@
 |-
 | style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_bool|bool]]) When true, this variable will generate an exception if an out of range error occurs when converting a "float" value to an integer. ROBOTC will convert out of range exceptions into the largest possible integer number.
+|-
 |}
 <br />

@@ Line 80: / Line 80: @@
 {| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
 |-
-| class="variableType"| <span class="bigKeywordBI">intrinsic short </span><span class="bigKeywordB">getAvailSpaceInDebugStream()</span>
+| class="variableType"| <span class="bigKeywordBI">intrinsic short </span><span class="bigKeywordB">getAvailSpaceInDebugStream</span><span class="codePunc">()</span>
 |-
 | style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_short|short]])  Variable will return the current amount of space available in the debug stream. For the Arduino platform, the maximum size of the debug stream is 300 bytes.

@@ Line 102: / Line 102: @@
 <br />
-== version ==
+== bFloatConversionErrors==
 {| style="color:black;" width="100%" cellpadding="5%" cellspacing="0" border="0"
 |-
-| class="variableType"| <span class="bigKeywordBI">const word </span><span class="bigKeywordB">version</span>
+| class="variableType"| <span class="bigKeywordBI">intrinsic bool </span><span class="bigKeywordB">bFloatConversionErrors</span>
-|-
-| style="font-family:Verdana, Geneva, sans-serif; color:black; background-color:#FFFFFF; text-align:left; font-size:100%;"|([[Data_Types#dataType_word|word]])  Contains the firmware version number.
 |-
+|
 |}
 <br />