 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Serial comms @ 9600, 7E1...
| Author | Message | ||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9593 |
Hi folks. 
I have an old system that talks to a WYSE-100 terminal, but the settings for correct operation are 9600 baud, 7E1. This is different from the default of 8N1, although, it may not be by much. Is there any way I can use the ASCII terminal with this configuration? ...as far as I know, the ASCII terminal is 8N1 and that is all it can ever be, unless I am missing something... Smoke makes things work. When the smoke gets out, it stops! |
||||
BobD Guru  Joined: 07/12/2011 Location: AustraliaPosts: 935 |
From the manual [quote] Set-Up Menu The terminal can be configured with a number of options on the SetUp menu. This menu is invoked by using SHIFT- F12 on the keyboard and the menu will be displayed on the video display. Note that this means that you cannot set any options over the USB interface, you must connect a keyboard and monitor. In the Set-Up menu you can select the number of lines to display in VGA mode (24 or 36), the type of composite output (PAL or NTSC) and the type of keyboard connected (French, German, US, etc). For the serial interface you can select the number of bits, parity and the number of stop bits.[/quote] |
||||
MicroBlocks Guru Joined: 12/05/2012 Location: ThailandPosts: 2209 |
The WYSE should be able to be setup for 8N1 use. I only found a WYSE-60 manual here Maybe it gets you started. Microblocks. Build with logic. |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9593 |
@ BobD - Hell's bells - how did I miss that? Will take a closer look at that menu now - had forgotten about the VT-100's menu.... 
@ TZA - The problem is not the Wyse-100, the problem is that the system that sends the serial to the Wyse-100 outputs it's data as 7E1, NOT 8N1, so using 8N1 results in garbled comms. 
EDIT: Thanks, BobD - talk about a blonde moment.... Fancy forgetting the fecking setup menu. I will try this out tomorrow on site. The old Wyse-100 is suffering from very severe phospher burn-in, making it very hard to read with the ghostly image of the main menu on every screen!  Smoke makes things work. When the smoke gets out, it stops! |
||||
Bryan1 Guru Joined: 22/02/2006 Location: AustraliaPosts: 1454 |
Are you that isn't the magic smoke saying let me out  |
||||
| WhiteWizzard Guru Joined: 05/04/2013 Location: United KingdomPosts: 2933 |
@Grogster Bryan raises an excellent point . . . . |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9593 |
Could be, if you mean the magic smoke in my brain.....  Smoke makes things work. When the smoke gets out, it stops! |
||||
| robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2437 |
7E1 versus 8N1 hmmm, you could use a micromite to translate between the two - am i right in saying that the only difference is in what the topmost bit is set to? out of curiosity - what is the wyse terminal attached to? an important/valuable bit of kit? 7E1 can be translated to 8N1 by just ANDing each byte with 127 before passing it along to the 'new terminal': Cr=(Cr AND 127)
going the other way is a little bit more tricky, as you need to calculate the parity of the bottom 7 bits and adjust the 8th accordingly: P=0
IF (Ct AND 1) <> 0 THEN P=P+1 IF (Ct AND 2) <> 0 THEN P=P+1 IF (Ct AND 4) <> 0 THEN P=P+1 IF (Ct AND 8) <> 0 THEN P=P+1 IF (Ct AND 16) <> 0 THEN P=P+1 IF (Ct AND 32) <> 0 THEN P=P+1 IF (Ct AND 64) <> 0 THEN P=P+1 IF (P AND 1) <> 0 THEN Ct=(Ct OR 128) cheers, rob :-) |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9593 |
It talks to an ancient old nursecall system from the 1980's. Visiplex brand, if that means anything. Software version is 1.00D, yet it has never ever been updated firmware wise as long as I have been taking care of it, and despite it's very early 1.00 revision number, it gives no trouble running 24/7/365. It's the CRT Wyse-100's that suffer the most. 
This system is actively being phased out, but they need to keep it running as long as possible while the replacement system is rolled out over a few years. They still have spares for it including a whole spare base unit, so there is no harm in continuing to use it, with the possible exception of a few burnt-in terminal screens!
EDIT: This old system, I thought, would be a PERFECT chance for me to use an ASCII Terminal(Geoff's VT-100 circuit) paired with a small LCD screen to prevent burn-in. The ASCII Terminal, provided it can talk to the system, will be a green-screen. The existing Wyse-100's are orange. According to research, LCD's can also suffer from a kind of memory-effect similar to that of phosphor burn-in on CRT's if you leave a static image on them for a long time, but I understand it takes a lot longer to happen. I have a VGA screen on an old security system that has been running for 3 years now 24/7 and there is no evidence of any memory-effect on that LCD - and it was a cheapie screen too. Smoke makes things work. When the smoke gets out, it stops! |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
