Table of Contents
Advertisement
Using Duet Remote Debug
Making Incremental Code Changes and Starting
a New Debug Session
When finished with a debug session:
1. Click the Disconnect toolbar button
2. To clean up the Call Stack view, click the Remove toolbar button.
3. Complete any Java code changes found from debugging
4. Regenerate and Repack the project.
5. In NetLinx Studio 2, build (compile) and transfer the project files to the
target NetLinx Master.
Note: To restart the last debug session, press the 'Debug' icon, or change
settings first if needed (e.g.: Debug Port address).
Finishing a Duet Debug Session
When you have verified that the Module changes are complete, return the Master
to regular operating mode (non-debug mode) by highlighting the uppermost
stack-line (beg: Duet icon, "[Duet Remote Debug]"), then pressing the AMX
Boot icon to reset the AMX Master from debug controls. This function has the
equivalent effect as the NetLinx Studio's Tools > Reboot the Master
Controller... command.
Note: For more information, On-line help is available to learn more about
industry-standard debug controls available in Café Duet. Go to Help > Help
Contents and open the "Java Developers Guide" and refer to "Concepts" >
"Local debugging", "Remote debugging", "Breakpoints", etc...
Café Duet v1.8 - User's Guide
51
Hide quick links:
Advertisement
Table of Contents
