01-22-2019, 09:56 AM
Hi
I have been using the WiModem232 with OLED to access the UK'sTELSTAR videotext system and it works very well. However, one thing that would help enormously when setting up a call to a system such as this, is to interpret the character 0x5F as a CR when in command mode.
Videotext systems do not use <CR> as a line terminator but use 0x5F (#) instead. This means that it is often not possible to establish a call using something like ATDS=2<CR> when using a viewdata terminal. This means that a call has to be established using a traditional terminal before connecting/reloading the viewdata terminal. Interpreting a 0x5F as a <CR> when in command mode would solve this.
If you wanted to go a stage further, what about an AT setting that configures the modem to auto-connect to the first stored number when first turned on.
Just a suggestion for your consideration. Great work on the device.
Details of TELSTAR are at https://glasstty.com/wiki/index.php/The_...tex_System
I have been using the WiModem232 with OLED to access the UK'sTELSTAR videotext system and it works very well. However, one thing that would help enormously when setting up a call to a system such as this, is to interpret the character 0x5F as a CR when in command mode.
Videotext systems do not use <CR> as a line terminator but use 0x5F (#) instead. This means that it is often not possible to establish a call using something like ATDS=2<CR> when using a viewdata terminal. This means that a call has to be established using a traditional terminal before connecting/reloading the viewdata terminal. Interpreting a 0x5F as a <CR> when in command mode would solve this.
If you wanted to go a stage further, what about an AT setting that configures the modem to auto-connect to the first stored number when first turned on.
Just a suggestion for your consideration. Great work on the device.
Details of TELSTAR are at https://glasstty.com/wiki/index.php/The_...tex_System