ccurtis
Well-Known Member
Xiptron, the program does nothing else but run in a loop while waiting for a state transition on the DSR pin. It cannot ever get to the place where it asks for a new filename until a state transition occurs. It is intentionally stuck in that loop until a DSR occurs. Therefore, I can only conclude that Windows detects a state transition on DSR before you expect it to. Bear in mind that any state transition on DSR will trigger the timers to start, whether is be from low to high, or high to low. Is it possible that noise or some other unintentional state transition is occurring?
If my conclusion is correct then what is happening is that an unintentional DSR causes the timers to start. The timers expire and the program asks for a new filename. So, then the DTR output must also be taking place. Did you notice that DTR was also tripping whatever you are driving with it?
I can add a hotkey to start the timers by force, but if there is noise or some other unintentional transition of DRS, the issue will not be resolved by a hotkey.
If my conclusion is correct then what is happening is that an unintentional DSR causes the timers to start. The timers expire and the program asks for a new filename. So, then the DTR output must also be taking place. Did you notice that DTR was also tripping whatever you are driving with it?
I can add a hotkey to start the timers by force, but if there is noise or some other unintentional transition of DRS, the issue will not be resolved by a hotkey.
Last edited: