@JonnyMac said:
I've seen a few oddities with the Spin Tools internal terminal, too, so I tend to open and use PST. I tried your string in both. In my case all characters seem to print, but there is some extra cruft at the end of the string using the Spin Tools terminal.
I'm not sure, could be tx pin floating when the cogs are terminated ?
Seems that weird things happens if I don't call txflush at the end, or don't add an endless repeat to keep the main cog running (using your jm_fullduplexserial library).
@macca If you do any updates to the Spin Tools terminal would you consider adding the ability to turn off the flashing cursor?
The cursor is draw when the line input box is disabled, but yes I can add a setting.
Unfortunately PST doesn't have a cursor control code, ANSI/VT-100 have escapes to set the cursor blinking or hide and show.
@lab_ges said:
Hi @macca
I have been noticing for a while that certain ASCII characters seemed to be missing when using the SPIN Tools terminal, specifically most of the RIGHT brackets i.e. ") > }" as well as "\"
It may be something in my setup but the characters are there using spin Tools with PST, as shown on the screen prints, I have combined, below.
Had these rendering issues in the past and I have changed the terminal rendering code to prevent that, in version 0.47 if I remember correctly. Are you using the latest version ?
Opps sorry I meant to say this was on "Spin Tools IDE 0.49.1" which is still the latest version according to your site. It has never been a major problem but thought it was worth mentioning. I am also running on Windows 11 pro if that makes a difference?
This problem has been arround for several versions at least and I thought that one day it would go away when a new version was released, but it has hung on.
I find it interesting that @JonnyMac isn't seeing the same thing, though I do note he is missing the\symbol between the square brackets!
I never see those funny characters at the end or the blinking cursor that JonnyMac sees either, it is like he is seeing the CR LF characters at the end of the line (which can be a handy thing for debugging).
On on my Spin tool terminal there is actually a backtick type character (like these but not possible to show on the forum) showing instead of the backslash.
I generated the characters using this simple test code, though I think I actually missed out the space in the screen prints above.
repeat byte[x] from $20 to $7E 'Full visible ascii range starting at space!
waitms(50)
send(byte[x])
send(13)
send(10)
@lab_ges said:
Opps sorry I meant to say this was on "Spin Tools IDE 0.49.1" which is still the latest version according to your site. It has never been a major problem but thought it was worth mentioning. I am also running on Windows 11 pro if that makes a difference?
This problem has been arround for several versions at least and I thought that one day it would go away when a new version was released, but it has hung on.
I find it interesting that @JonnyMac isn't seeing the same thing, though I do note he is missing the\symbol between the square brackets!
I don't see problems here with Linux and Windows 11.
Are you using a different font than the default (that on Windows should be Consolas) ?
@Rayman said:
@macca Just tested the serial port issue on another computer and it acts the same way...
Have to close IDE if was in debug mode and serial cable unplugged and replugged.
That auto device discovery option is selected.
Ah... I found that on Windows the COM port number doesn't change... I need to adjust some parts of the discovery process.
I find it interesting that @JonnyMac isn't seeing the same thing, though I do note he is missing the\symbol between the square brackets!
My fault; I copied the wrong result string from your original post. I duplicated your repeat loop code and it seems to work. Unless there's a specific reason I don't understand, you don't need to cast x as a byte because term.tx() only sends the lower eight bits of what it gets.
I'm not sure, could be tx pin floating when the cogs are terminated ?
Seems that weird things happens if I don't call txflush at the end, or don't add an endless repeat to keep the main cog running (using your jm_fullduplexserial library).
That may have been the case because I'm not able to replicate that now. Sorry for the false alarm.
@macca said:
I don't see problems here with Linux and Windows 11.
Are you using a different font than the default (that on Windows should be Consolas) ?
Ok, you got me there, I remember playing around with the Parallax2 font at some stage and I must have left it in the options. I changed it back and it now works OK.
Sorry for the trouble I caused you!
@JonnyMac > Unless there's a specific reason I don't understand, you don't need to cast x as a byte because term.tx() only sends the lower eight bits of what it gets.
Thanks for the comment, always useful. In this case the program was just an exercise to get to the cause of the missing characters in the terminal, ultimately I will be creating ethernet packets and I just grabbed some code from my main program and edited it to use for the demo.
@macca I had to perform an update on one of my large projects last night. It was my first time really putting Spin Tools IDE through its paces. Wow, what a difference from Propeller Tool. Having the ability to jump straight to the PUB/PRI method or the OBJ file using the window on the right made a tremendous difference in the amount of time required to get things done. What used to be a bunch of searching and scrolling is now just a click away.
Comments
I'm not sure, could be tx pin floating when the cogs are terminated ?
Seems that weird things happens if I don't call txflush at the end, or don't add an endless repeat to keep the main cog running (using your jm_fullduplexserial library).
The cursor is draw when the line input box is disabled, but yes I can add a setting.
Unfortunately PST doesn't have a cursor control code, ANSI/VT-100 have escapes to set the cursor blinking or hide and show.
Opps sorry I meant to say this was on "Spin Tools IDE 0.49.1" which is still the latest version according to your site. It has never been a major problem but thought it was worth mentioning. I am also running on Windows 11 pro if that makes a difference?
This problem has been arround for several versions at least and I thought that one day it would go away when a new version was released, but it has hung on.
I find it interesting that @JonnyMac isn't seeing the same thing, though I do note he is missing the
\symbol between the square brackets!I never see those funny characters at the end or the blinking cursor that JonnyMac sees either, it is like he is seeing the CR LF characters at the end of the line (which can be a handy thing for debugging).
On on my Spin tool terminal there is actually a backtick type character
(like these but not possible to show on the forum) showing instead of the backslash.
I generated the characters using this simple test code, though I think I actually missed out the space in the screen prints above.
repeat byte[x] from $20 to $7E 'Full visible ascii range starting at space! waitms(50) send(byte[x]) send(13) send(10)I don't see problems here with Linux and Windows 11.
Are you using a different font than the default (that on Windows should be Consolas) ?
Ah... I found that on Windows the COM port number doesn't change... I need to adjust some parts of the discovery process.
My fault; I copied the wrong result string from your original post. I duplicated your repeat loop code and it seems to work. Unless there's a specific reason I don't understand, you don't need to cast x as a byte because term.tx() only sends the lower eight bits of what it gets.
That may have been the case because I'm not able to replicate that now. Sorry for the false alarm.
Ok, you got me there, I remember playing around with the Parallax2 font at some stage and I must have left it in the options. I changed it back and it now works OK.
Sorry for the trouble I caused you!
@JonnyMac > Unless there's a specific reason I don't understand, you don't need to cast x as a byte because term.tx() only sends the lower eight bits of what it gets.
Thanks for the comment, always useful. In this case the program was just an exercise to get to the cause of the missing characters in the terminal, ultimately I will be creating ethernet packets and I just grabbed some code from my main program and edited it to use for the demo.
@macca I had to perform an update on one of my large projects last night. It was my first time really putting Spin Tools IDE through its paces. Wow, what a difference from Propeller Tool. Having the ability to jump straight to the PUB/PRI method or the OBJ file using the window on the right made a tremendous difference in the amount of time required to get things done. What used to be a bunch of searching and scrolling is now just a click away.
Thank you so much for Spin Tools IDE!
I suggest to those that can, support Marco!
--Terry