开云体育

Does anyone know of a way to stop sending the debugger information to
the console?
I am trying to debug some simple user command stuff and I just cant
type that fast.

ChipG

I don't think there's a way to do that. If you're using Print()
statements from SIMPL+, they'll always show on the console. If you're
actually seeing trace information, try closing SIMPL Debugger.
Sometimes that bleeds into the console.

Otherwise, use a terminal emulator with line editing so you can enter
your command without worrying about output scrolling by. MUD clients
are good at this... try SimpleMU for instance, tell it to connect to
your processor's IP at port 23.

Jeremy

--
Jeremy Weatherford

If you are using toolbox, you can open up a secondary console (you
have to choose that as your connection type). Viewport, just open it
up and connect - it automatically uses a new socket (toolbox tries to
do everything on one, and splits it off as virtual consoles - however,
you get the side consequence that all the simple debugger data spills
out on you!) Or open up a console to port 23. By the act of it being
a "differnt" console, you won't get the Simple debugger data.

(if you're on a processor w/just RS-232, then you're sunk.)


--- In Crestron@..., "Jeremy Weatherford" <xidus.net@...>
wrote:

I don't think there's a way to do that. If you're using Print()
statements from SIMPL+, they'll always show on the console. If you're
actually seeing trace information, try closing SIMPL Debugger.
Sometimes that bleeds into the console.

Otherwise, use a terminal emulator with line editing so you can enter
your command without worrying about output scrolling by. MUD clients
are good at this... try SimpleMU for instance, tell it to connect to
your processor's IP at port 23.

Jeremy

On Jan 11, 2008 3:44 PM, lunarteq <lunartech@...> wrote:

Does anyone know of a way to stop sending the debugger information to
the console?
I am trying to debug some simple user command stuff and I just cant
type that fast.

ChipG

Check out the Files area for useful modules, documents, and drivers.

A contact list of Crestron dealers and programmers can be found in

the Database area.

Yahoo! Groups Links

--
Jeremy Weatherford

Once again, fooguy brings the foo to its knees. Thanks
Geez... its RIGHT There and all this time I never even bothered to see
what it does.

ChipG

--- In Crestron@..., "fooguy89" <fooguy89@...> wrote:

If you are using toolbox, you can open up a secondary console (you
have to choose that as your connection type). Viewport, just open it
up and connect - it automatically uses a new socket (toolbox tries to
do everything on one, and splits it off as virtual consoles - however,
you get the side consequence that all the simple debugger data spills
out on you!) Or open up a console to port 23. By the act of it being
a "differnt" console, you won't get the Simple debugger data.

(if you're on a processor w/just RS-232, then you're sunk.)


--- In Crestron@..., "Jeremy Weatherford" <xidus.net@>
wrote:

I don't think there's a way to do that. If you're using Print()
statements from SIMPL+, they'll always show on the console. If you're
actually seeing trace information, try closing SIMPL Debugger.
Sometimes that bleeds into the console.

Otherwise, use a terminal emulator with line editing so you can enter
your command without worrying about output scrolling by. MUD clients
are good at this... try SimpleMU for instance, tell it to connect to
your processor's IP at port 23.

Jeremy

On Jan 11, 2008 3:44 PM, lunarteq <lunartech@> wrote:

Does anyone know of a way to stop sending the debugger

information to

the console?
I am trying to debug some simple user command stuff and I just cant
type that fast.

ChipG

Check out the Files area for useful modules, documents, and drivers.

A contact list of Crestron dealers and programmers can be found in

the Database area.

Yahoo! Groups Links

--
Jeremy Weatherford

I know this is an old thread. I found it when googling for the same issue.

YES, you can issue a console command to stop the debugger data stream

DBGSIGNAL RESET ALL