Sign in to follow this  
Followers 0
kwhy

Comms Problem with syswin on laptop

11 posts in this topic

Hi all I'm trying to connect to an Omron plc CPM1A with a old toshiba laptop 4600 through its com1 ( Syswin 3.4 on Win98) and getting 'connect failed' Using the same set up on a newer XP desktop works fine Tested the com1 port on Laptop by connecting a serial modem to it, works fine Help Kwhy

Share this post


Link to post
Share on other sites
What are your comm's settings in Syswin...

Share this post


Link to post
Share on other sites
9600 , data bits =7 , Even and Stop = 2. Tried different baud rate and no luck. Same settings work on the other PC

Share this post


Link to post
Share on other sites
Does the PLC comm;s light even flash when you try and connect.... Typically it will flash around 3 times while it trys to communicate to the PLC... if it aint flashing then there would apprear to be a problem with the comm;s getting through... 1. Could be that an application has hold of the comm;s port 2. A programming cable problem 3. A broken cable 4. Problem with the CIF01 5. Problem with that PLC's comm's port.

Share this post


Link to post
Share on other sites
Yep, light flashes while its trying to connect. Like i said the same cable and plc works on a different pc . It has to be the laptop. But what !

Share this post


Link to post
Share on other sites
Ok, so you have proved the comm;s to the PLC... but it sounds like Syswin aint getting a response back. When you tested the modem where you getting your characters echo'd back ?

Share this post


Link to post
Share on other sites
Used a wire jumper to connect pin 2 to pin 3. And With hyperterminal any text type was echoed on the screen. Like you said it must be syswin not talking properly to com1

Share this post


Link to post
Share on other sites
If using a CIF01 RS232C adapter, is the mode switch setting on the CIF01 set to "host" ?

Share this post


Link to post
Share on other sites
Have you check if any resident programs are nabbing the port ?

Share this post


Link to post
Share on other sites
That is a good way to test com port. However, it may not be enough sometimes. Shorting 2 and 3 only tests Rx and Tx. If some other pins required for hardware handshake are burnt and you are trying to communicate by 'Hardware Handshake' , you may not be able to communicate. Try without an handshake

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0