Xiptron, I think you might like the program that dmitry_n found and posted a link to.

It's Windows based and it looks like it does everything you want, with all the bells and whistles.

Let me know. Otherwise, I will continue with the update for you, no problem.

 

Hi cc. I'll check it out but I'd prefer us to carry on with this particular project. With your final "polishing" it'll be pretty much perfect. Hope that's ok with you.

 

Can you give me the link - I can't find his post.

 

Sure. Here ...

 

LOL - I had to laugh a bit - I know the X-Note Stopwatch program quite well. In fact it was ME who suggested that they add the serial control you see in V1.40!!! I've had a look at v1.5 but it doesn't work in the fashion I require. I'd still prefer we finish ours for now.

 

Xiptron, attached is the update addressing everything I could address. One has 5 timers. The other has 8 timers. I gave up on starting an external executable. I can do it, but the external executable has to finish and exit before returning control back to the timer program. The path in titlebar is operating system dependent. The background is gray, not white. I have to go to another screen mode to get a white background and I don't want to go there.

Best wishes.

Attached Files

MULTI6E.zip (50.9 KB, 2 views)

 

Hi CC. Great job and thanks. The 5 and 8 option is good. The file entry method is better now as once loaded the program is ready to be started. All the other bits and pieces are fine and I'm very happy ... except for one thing (don't kill me!!!!) - it turns out that the green font is very hard to see compared to the white settings above. I h-a-t-e to ask .. but can you make the timer text the same as timer settings? i.e white on black. DOS properties doesn't change the timing color. I also think Lucida Consol 12 pt font looks cleaner - can you make that the default? Those are my last requests, I promise lol!!!!
--------------------------
About the executable. I have since discovered that my application can be started with any single key as long as I assign one. Would it be possible for your program to access Windows and KEYBOARD and effectly press the assigned key and then return to dos and start countdown. This could be a very short event, not long enough to seriously delay timing start? What do you think?

 

but can you make the timer text the same as timer settings? i.e white on black. DOS properties doesn't change the timing color. I also think Lucida Consol 12 pt font looks cleaner - can you make that the default?

Xiptron, okay, the white on black versions are attached. About the font, you change that in XP by right-clicking on the title bar of the window, then click Properties, then click Font to change the font and font size for the application.
--------------------------
Would it be possible for your program to access Windows and KEYBOARD and effectly press the assigned key and then return to dos and start countdown. This could be a very short event, not long enough to seriously delay timing start? What do you think?

I don't see a simply way to do that. I think I will have to leave it as it is.

Attached Files

MULTIF.zip (50.9 KB, 2 views)

 

That's great CC. Program looks good now and all working fine. Don't worry about the external start problem, I solved it by assigning "1" as a hot key and wired across the key's contacts inside the keyboard! This then goes off to a remote relay closure. Desparate measures but it works fine, the program and timers now start together.

Thanks for your expert help and know that we finally "got there!" lol. Keep in touch.

 

Hi Curtis, a small problem has surfaced: after the program has been set ready to start but left waiting overnight for DSR (10-12hours later), it has reverted to asking for a new filename. Is this a function of Windows not detecting serial port activity (timeout)? Twice now it has failed to start because of this mysterious change of state. Also, is it posssible to start the program with a hotkey as well as shorting dsr to rts? A hotkey would enable me to start the program via remote desktop. G

 

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.

 

I have had it on test again overnite and so far no change of state. I can only assume it was a false trigger for some reason. No worries, I realise it can't do it by itself.

The hotkey would be great, as that will allow me to start the timers remotely if I have to. What key will you assign?

 

Is there any particular key you would like? Any alphanumeric key is easiest for me.

As far as false triggering goes, an open DSR pin is just begging for noise to trigger it. The open input sits somewhere between high and low states, and usually considers it a true low (mark, -12v). I can set some other output pin low. Then tie a 10K resistor between it and the DSR pin. This will hold the DSR pin low, for sure, until you connect it directly to the RTS pin, which is set to high.

 

The '1' key will be ok. Ok, I'm using pin 7 (RTS) so you could take DTR to neg (pin 4).

 

Come to think of it, DTR starts out neg. Yeah, just keep a 10K resistor always connected between DSR and DTR, and use RST to bring DSR high to start the timers. When the DTR pin goes high at the expiration of a timer, it won't matter because the timers have started already anyway.

You might want to check that out a few times before going with it. I think I set DTR low again then clear the transition that is stored before polling DSR again on the next go-around.

I put the "1" key mod in tomorrow.