It seems to me that I have had trouble with extra blank lines whenever I try to go from PST to a normal terminal emulator. I don't think its default settings match common practice. Maybe we can get Parallax to fix that.
Guys,
If I am missing the boat on this one let me know. I think that the best way to set up terminal function would be to code things to react as closely to say VT100 as possible. I know that nearly everything can be configured to be compatible with this or VT220. VT320 may be a reach. Or ansi or whatever, as long as it conforms to a known followed standard that is supported across all possible development systems as well as any systems that the end device may be deployed with as an endpoint.
If I am missing the boat on this one let me know. I think that the best way to set up terminal function would be to code things to react as closely to say VT100 as possible. I know that nearly everything can be configured to be compatible with this or VT220. VT320 may be a reach. Or ansi or whatever, as long as it conforms to a known followed standard that is supported across all possible development systems as well as any systems that the end device may be deployed with as an endpoint.
Frank
The terminal mode in the new propgcc release works the same on under Windows, Linux, and Mac and I believe it behaves the way traditional terminals did with respect to the CR and LF characters. It sends the Propeller a CR when the user presses the RETURN key and it requires a CR and LF at the end of each line of text received from the Propeller. The libraries have been adjusted to work in this mode although I think they may be able to support other modes as well.
Hi,
now all Terminal Programs work well.
I have ported my Radiometer Project ( posted in another Thread) to propgcc.
Therefore I written my own Terminal Server on PC side and it's work also well.
That's great news! Thank you for all the testing and for your bug reports -- they've been very helpful.
Eric
Well, I think I have found the reason that my c3 was not behaving correctly with fibo. I noticed that it appeared to be seeing the USB serial port, but was doing nothing. I toggled the DTR pin (a function of GTKterm), and fibo started outputing its values to the terminal program as expected. So I don't believe that the terminal problems I had originally ascribed to the loader / gcc were in fact a gcc problem, rather a serial and USB problem......
Well, I think I have found the reason that my c3 was not behaving correctly with fibo. I noticed that it appeared to be seeing the USB serial port, but was doing nothing. I toggled the DTR pin (a function of GTKterm), and fibo started outputing its values to the terminal program as expected. So I don't believe that the terminal problems I had originally ascribed to the loader / gcc were in fact a gcc problem, rather a serial and USB problem......
Hmmm, interesting. I'm glad you figured that out -- thanks for the update!
Comments
Guys,
If I am missing the boat on this one let me know. I think that the best way to set up terminal function would be to code things to react as closely to say VT100 as possible. I know that nearly everything can be configured to be compatible with this or VT220. VT320 may be a reach. Or ansi or whatever, as long as it conforms to a known followed standard that is supported across all possible development systems as well as any systems that the end device may be deployed with as an endpoint.
Frank
now all Terminal Programs work well.
I have ported my Radiometer Project ( posted in another Thread) to propgcc.
Therefore I written my own Terminal Server on PC side and it's work also well.
http://home.mnet-online.de/reimay/Projects/Radiometer/PC_Software/GUI/Clipboard01.jpg
Thanks again for the good job.
best regards
Reinhard
That's great news! Thank you for all the testing and for your bug reports -- they've been very helpful.
Eric
Well, I think I have found the reason that my c3 was not behaving correctly with fibo. I noticed that it appeared to be seeing the USB serial port, but was doing nothing. I toggled the DTR pin (a function of GTKterm), and fibo started outputing its values to the terminal program as expected. So I don't believe that the terminal problems I had originally ascribed to the loader / gcc were in fact a gcc problem, rather a serial and USB problem......
Frank
Hmmm, interesting. I'm glad you figured that out -- thanks for the update!
Eric