User`s guide

Getting Star ted with RTDX™
Your processor may already be stopped at this point. In a script, you might
put the function in an
if-statement as we have d one h ere . Consider this
test to be a safety check. No harm comes to the processor if it is already
stopped when you tell it to stop. When you direct a stopped processor to
halt, the function returns immediately.
2 You have stopped the processor. Now disable the RTDX channels you
opened to communicate with the processor.
cc.rtdx.disable('all');
If necessary, using disable with channel name and processor identifier
input arguments lets you disable only the channel you choose. When you
have more than one board or processor, you may find disabling selected
channels meets your needs.
When you finish your RTDX communications session, disable RTDX to
ensure that Embedded IDE Link CC releases your open channels before
you close them.
cc.rtdx.disable;
3 Use one or all of the fo llow ing function syntaxes to clo se your open
channels. Either close selected channels by using the channel name in the
function, or use the
all option to close all open channels.
•
cc.rtdx.close('ichan') to close your input channel in this tutorial.
•
cc.rtdx.close('ochan') to close your output channel in the tutorial.
•
cc.rtdx.close('all') to close all of your open RTDX channels,
regardless of whether they are part of this tutorial.
Consider using the
all option with the close function w h en you finish
your RTDX work. Closing channels reduces unforeseen pro blems caused
by channel objects that exist but do not get clos ed correctly when you end
your session.
4 When you created your RTDX object (cc = ticcs('boardnum',1)atthe
beginning of this tutorial, the
ticcs function opened CCS IDE and set the
visibility to 0. To avoid problems that occur when you close the interface to
RTDX with CCS visibility set to 0, make CCS IDE visible on your desktop.
2-41