I have written several scripts using the set txpace in the start of the script. Most the time with Meridian 1 PBX’s it helps so you don’t push commands out faster then the PBX can receive it. This is what the command was intended for but here is what I have discovered after having a lot of trouble with my ProComm software.
When you use txpace it changes this variable forever in your Procomm software, for all connection types, for all terminal types until you change it back. It can be changed back by a script (txpace = 0) or you go to options>system options> system options > transmit pacing.
I had trouble with certain emulations and connections. I wondered why connections I made via telnet or other equipment on dial up did not act right. For instance I connected to some equipment that allowed you to navigate with the 4 arrow keys on your keyboard but all I got each time I used an arrow was an escape sequence. From trial and error I discovered it was a txpace issue. As soon as I set my TXPACE back to 0 these other emulation issues went away.
I thought it might be helpful to post this message for others who might be experiencing this problem could benefit from what I have learned. So often when a key sequence does not work its it is easy to assume it is a keyboard mapping issue or something else. If you use txpace at the start of a script it might be wyse to end the script with txpace = 0
When you use txpace it changes this variable forever in your Procomm software, for all connection types, for all terminal types until you change it back. It can be changed back by a script (txpace = 0) or you go to options>system options> system options > transmit pacing.
I had trouble with certain emulations and connections. I wondered why connections I made via telnet or other equipment on dial up did not act right. For instance I connected to some equipment that allowed you to navigate with the 4 arrow keys on your keyboard but all I got each time I used an arrow was an escape sequence. From trial and error I discovered it was a txpace issue. As soon as I set my TXPACE back to 0 these other emulation issues went away.
I thought it might be helpful to post this message for others who might be experiencing this problem could benefit from what I have learned. So often when a key sequence does not work its it is easy to assume it is a keyboard mapping issue or something else. If you use txpace at the start of a script it might be wyse to end the script with txpace = 0