Paul Forgey
July 24th, 2003, 08:55 PM
Girder 3.2.9, Windows XP.
I've set up my Silitek according to another thread I've found in order for it to work at all: 1200 bause, bit number 8, dtr, 1 stop bit, fast silitek init, skip silitek init check, strip zeros from silitek string.
At first, things work OK. Then, after anywhere from 10 seconds to 30 minutes later, Girder quits responding to the Silitek. If I attempt to either disable the input or quit Girder while it is in this state, I get the message "cannot power down". Re-enabling the input later causes the error "com port busy". The only way to get back to normal is to quit and restart Girder.
Could stray or parital signals from the Silitek be causing a state in the plug-in where it doesn't have a proper timeout?
I've set up my Silitek according to another thread I've found in order for it to work at all: 1200 bause, bit number 8, dtr, 1 stop bit, fast silitek init, skip silitek init check, strip zeros from silitek string.
At first, things work OK. Then, after anywhere from 10 seconds to 30 minutes later, Girder quits responding to the Silitek. If I attempt to either disable the input or quit Girder while it is in this state, I get the message "cannot power down". Re-enabling the input later causes the error "com port busy". The only way to get back to normal is to quit and restart Girder.
Could stray or parital signals from the Silitek be causing a state in the plug-in where it doesn't have a proper timeout?