Canadianweasel
IS-IT--Management
I'll set the scenerio for you here...
I have some software which, among other things, is used to control gate access. What will happen is that a membership card holder will scan their card, and if it is valid, send a signal (a string of characters) to the com port where a small piece of hardware will close the circuit to open a access gate.
The hardware I have gets its power from the com port itself. When it receives a string of characters, it will close the circuit and open the gate.
If tested using something such as Hyperterminal or an echo command from a DOS prompt, the box recieves the signals and closes the circuit. Fair enough, that works perfectly well.
The software that is to be actually used doesn't do this, when it opens the com port it does so without supplying power to the port itself, thereby making the hardware fail to do its thing. If I attach a modem with its own power supply, I notice the the software will send characters to the modem, so I know the software is actually outputting to this com port.
So, herein lies the question. I need to either A> physically supply power to that com port (which I don't have the capability to accomplish), or B> set the software up so that it sends its characters to a com port, and based on that a written VB program will see these characters, open and output to another com port while supplying the power. (A regular com port open)
I attempted to open the com port before the software takes over, but it sees that as an open com port. I echo to the com port, that opens it fine, close the dos window it remains open. Start the program, it closes the com port on me.
I truly hope that explanation makes sense. Basically taking the output of one com port (without conflicting with the software that has it open) and redirecting it to another com port on the same machine.
Thanks.
I have some software which, among other things, is used to control gate access. What will happen is that a membership card holder will scan their card, and if it is valid, send a signal (a string of characters) to the com port where a small piece of hardware will close the circuit to open a access gate.
The hardware I have gets its power from the com port itself. When it receives a string of characters, it will close the circuit and open the gate.
If tested using something such as Hyperterminal or an echo command from a DOS prompt, the box recieves the signals and closes the circuit. Fair enough, that works perfectly well.
The software that is to be actually used doesn't do this, when it opens the com port it does so without supplying power to the port itself, thereby making the hardware fail to do its thing. If I attach a modem with its own power supply, I notice the the software will send characters to the modem, so I know the software is actually outputting to this com port.
So, herein lies the question. I need to either A> physically supply power to that com port (which I don't have the capability to accomplish), or B> set the software up so that it sends its characters to a com port, and based on that a written VB program will see these characters, open and output to another com port while supplying the power. (A regular com port open)
I attempted to open the com port before the software takes over, but it sees that as an open com port. I echo to the com port, that opens it fine, close the dos window it remains open. Start the program, it closes the com port on me.
I truly hope that explanation makes sense. Basically taking the output of one com port (without conflicting with the software that has it open) and redirecting it to another com port on the same machine.
Thanks.