how to make a virtual serial port conection between proteus and serial port emulator
Discussion in "Project Doubts" started by dhanushka888 May 4, 2013.
Sat May 04 2013, 01:28 am
I tried to connect haserver proteus simulation with virtual serial port software.
but I couldn't do it.
that the telnet client is not responding to the proteus simulation hardware.
any suggestions??
but I couldn't do it.
that the telnet client is not responding to the proteus simulation hardware.
any suggestions??
Sat May 04 2013, 12:46 pm
You need to create a virtual com port pair on your PC where one side of pair goes to proteus COMPIM port and other goes to HAserver. then you will be able to simulate this project.
Some Virtual com port drivers are:
http://www.hhdsoftware.com/free-virtual-serial-ports
http://sourceforge.net/projects/com0com/
Some Virtual com port drivers are:
http://www.hhdsoftware.com/free-virtual-serial-ports
http://sourceforge.net/projects/com0com/
Sat May 04 2013, 04:44 pm
ajay sir,
I'm using below virtual serial port driver and made connection between com2 and com3. COM2 goes to the COMPIM .
COM3 goes to the haserver VB application. telnet client get nothing from server. you could see that COM2 sent 0 bytes. what could be the reason??
I'm using below virtual serial port driver and made connection between com2 and com3. COM2 goes to the COMPIM .
COM3 goes to the haserver VB application. telnet client get nothing from server. you could see that COM2 sent 0 bytes. what could be the reason??
[ Edited Sat May 04 2013, 04:47 pm ]
Sat May 04 2013, 07:05 pm
can you post COMPIM connections? make sure in COMPIM, TX goes to TX and RX goes to RX.
Mon May 06 2013, 03:09 pm
ok.. remove max232 from proteus and connect RXD of controller to RXD of COMPIM and Txd of controller to TXD of COMPIM directly. let me know what happens...
kibbutz4success like this.
Mon May 06 2013, 04:59 pm
when I press ENTER in telnet window, some symbols are appeared and error mark indicator of compim make some sign(red color)
Mon May 06 2013, 06:48 pm
I am assuming you connected rxd to rxd and txd to txd. Try this.. open second com pair in hyper terminal and see if you can interact with hardware or not.
Powered by e107 Forum System