View Single Post
  #3   Report Post  
Posted to rec.crafts.metalworking
David Billington[_2_] David Billington[_2_] is offline
external usenet poster
 
Posts: 311
Default communication problem

On 08/08/15 15:13, Bill wrote:
Not sure what you're trying to do, but for devices to talk to eachother
pins 2 & 3 need to "crossover" like this.

Device #1 Device #2
Connector #1 connector #2

pin #2 (transmit) ------------------------------- pin #3 (recieve)
pin #3 (recieve) -------------------------------- pin #2 (transmit)

Staight cables (what you have) are sometimes used in special cases -
like flashing EPROMs.

Not always the case, I spent 20 years in software and did RS232 stuff
many many times and it all depends on how the maker wired their kit and
whether they considered it DCE or DTE and what is at either end. RS232
comms probably causes more problems than anything I can think of. I've
needed straight through on some applications, null modem?, and crossed
on others, then of course if handshaking is added into the mix other
signals may need to be added or pulled to an appropriate state to
satisfy flow control.


On Fri, 07 Aug 2015 02:18:02 +0000, Dcap wrote:

windows XP
single serial port 9 pin
2nd gen controller
cable straight thru pin for pin
loopback checked cable all good
checked port at all speeds from 4800bits per all the way past 115200
set up on second pc laptop compaq 9pin

same issues
i have run thru the troub;eshoot docs completely.

one item
C:\program\deskCNC
i have no .ini file