> I can understand the DTR reset situation when running RS232. I don't
know
> how USB can control the DTR??
The FTDI chip is emulating an RS232 connection, including in hardware.
The ARMmite connects to RXD, TXD, but also DTR --> Reset, and RTS -->
boot into ISP.
The reset line on the ARMmite runs out from under the FTDI chip and
turns 90 between the U and 2 of U2. So a fine dremel could cut that.
Once done to reprogram, you will be running like a wireless ARMmite
(you'll have to push the reset button on the board).
Getting data into a file
-
YahooArchive
- Posts: 1462
- Joined: Fri Oct 19, 2012 5:11 am
Re: Getting data into a file
OK, Bruce, thanks for the info. If I cut the DTR trace will the BASIC
program automatically run on power up and I can plug in the USB anytime to
download my data?? I only need to press the reset button when I want to
upload a new program, correct??
Pete
program automatically run on power up and I can plug in the USB anytime to
download my data?? I only need to press the reset button when I want to
upload a new program, correct??
Pete
-
YahooArchive
- Posts: 1462
- Joined: Fri Oct 19, 2012 5:11 am
Re: Getting data into a file
Hi,
I'm a newbie to Armite so pardon me if this has already been asked but I've
searched for it and can't find any mention.
I'd like to be able to log/capture the screen output to a file so I can capture
lots of information. I've only been doing screen copy and paste into a file but
I've kept my PRINT statements to a minimum to reduce any chance of overflow and
I've not seen any yet. But now I'm planning on adding much more output and I'm
afraid I may lose stuff. How do I log/capture the screen output to a file?
Also, it would help if there were a way to print at specific location on the
screen, that way I could show temporary status of the running program and keep
overwriting that part of the screen while continuing to log info into the rest
of the screen. I've tried using backspace, carriage return, and line feed
characters in the PRINT statement along with the CHR function but these
characters are ignored. Is there another way?
TIA
I'm a newbie to Armite so pardon me if this has already been asked but I've
searched for it and can't find any mention.
I'd like to be able to log/capture the screen output to a file so I can capture
lots of information. I've only been doing screen copy and paste into a file but
I've kept my PRINT statements to a minimum to reduce any chance of overflow and
I've not seen any yet. But now I'm planning on adding much more output and I'm
afraid I may lose stuff. How do I log/capture the screen output to a file?
Also, it would help if there were a way to print at specific location on the
screen, that way I could show temporary status of the running program and keep
overwriting that part of the screen while continuing to log info into the rest
of the screen. I've tried using backspace, carriage return, and line feed
characters in the PRINT statement along with the CHR function but these
characters are ignored. Is there another way?
TIA
-
YahooArchive
- Posts: 1462
- Joined: Fri Oct 19, 2012 5:11 am
Re: Getting data into a file
> I'd like to be able to log/capture the screen output to a file so I can
capture lots of information. I've only been doing screen copy and paste into a
file but I've kept my PRINT statements to a minimum to reduce any chance of
overflow and I've not seen any yet. But now I'm planning on adding much more
output and I'm afraid I may lose stuff. How do I log/capture the screen output
to a file?
The BASICtools are written in Tcl, and the text buffer is pretty big. I've sent
lots of stuff (many megabytes) to it and haven't seen it overflow, though there
is probably some limit.
It will allow you set the cursor at the top of the page, then use the scroll bar
to go to the bottom of the buffer, hold the shift key and select the whole text
when you set the cursor at the end. Yes, it would be good to have the ctl-A
Windows select all work, so that will go on the wish list. I could also add a
Save Output to File in the File menu (actually you could add that), as
BASICtools launches TclTerm.tcl when it starts and that contains all the serial
interface and the GUI.
>
> Also, it would help if there were a way to print at specific location on the
screen, that way I could show temporary status of the running program and keep
overwriting that part of the screen while continuing to log info into the rest
of the screen. I've tried using backspace, carriage return, and line feed
characters in the PRINT statement along with the CHR function but these
characters are ignored. Is there another way?
This may be a "religious" issue, but I don't think the right way would be to
invent yet another escape sequence and embed it in TclTerm. The better way is
to use TclTerm as a starting point and add your own interface, TclTk is an
extremely powerful GUI that is also cross platform, yes a bit of a learning
curve, but the Tk portion which does most of the GUI is also used by Python and
Perl. If we had to do it over again we might use Python, but Tcl is where we
are now. The ScopeDemo is an example of what can be done in Tcl, far more than
just moving a text cursor to a line. We could add something to
BASICtools/TclTerm that would look for a user add on tcl source file and include
it at startup.
capture lots of information. I've only been doing screen copy and paste into a
file but I've kept my PRINT statements to a minimum to reduce any chance of
overflow and I've not seen any yet. But now I'm planning on adding much more
output and I'm afraid I may lose stuff. How do I log/capture the screen output
to a file?
The BASICtools are written in Tcl, and the text buffer is pretty big. I've sent
lots of stuff (many megabytes) to it and haven't seen it overflow, though there
is probably some limit.
It will allow you set the cursor at the top of the page, then use the scroll bar
to go to the bottom of the buffer, hold the shift key and select the whole text
when you set the cursor at the end. Yes, it would be good to have the ctl-A
Windows select all work, so that will go on the wish list. I could also add a
Save Output to File in the File menu (actually you could add that), as
BASICtools launches TclTerm.tcl when it starts and that contains all the serial
interface and the GUI.
>
> Also, it would help if there were a way to print at specific location on the
screen, that way I could show temporary status of the running program and keep
overwriting that part of the screen while continuing to log info into the rest
of the screen. I've tried using backspace, carriage return, and line feed
characters in the PRINT statement along with the CHR function but these
characters are ignored. Is there another way?
This may be a "religious" issue, but I don't think the right way would be to
invent yet another escape sequence and embed it in TclTerm. The better way is
to use TclTerm as a starting point and add your own interface, TclTk is an
extremely powerful GUI that is also cross platform, yes a bit of a learning
curve, but the Tk portion which does most of the GUI is also used by Python and
Perl. If we had to do it over again we might use Python, but Tcl is where we
are now. The ScopeDemo is an example of what can be done in Tcl, far more than
just moving a text cursor to a line. We could add something to
BASICtools/TclTerm that would look for a user add on tcl source file and include
it at startup.