Using the dgrp_gui, I see the Port (01) Status as “OPEN” and the Modem Status shows all the settings ‘on’ with the exception of RI.
Now if I open the tty (in a Linux console) using minicom,
the Status line says “Online”. The parameters on both ends of the connection, match (9600 8N2). But after that I get nothing (no prompt; I would expect to set a “login” prompt)
Yes, I have confirmed the cable and it does wiremap correctly according pinout shown. The correct end is plugged into the Cisco AUX port.
I did try dinc (installed as dinc.dgrp), but still don’t see any response/echo from the AUX port. Again, all the indicators on the dgrp_gui seem to show everything is fine. Is there any other easy way to test if the port is working?
One thing I’d recommend is connecting a terminal up to the Cisco port, and make sure you’re seeing what you’d expect to see. If not, you’d want to check the Cisco config.
Assuming you’ve tried that and see a Cisco login just fine on the terminal, you’d want to try doing a loopback test on the Digi port next. Plug a loopback connector in the port rather than the cable going to the Cisco, then once again open that port with dinc/minicom/cu/etc. Whatever you type should be echoed back to your screen.
One other thing to mention. When using rlogin and checking line settings on an Etherlite, be advised that physical port 1 on an Etherlite is actually “line 0” when using the line command via rlogin. It looks like you pasted results for physical port 2, since “line 1” is the command you used.
The Cisco AUX port works fine. I can access the router prompt via a terminal.
Next, I tried to do the loopback test using a hardwired rj45 plug using the pinout diagram of the Etherlite’s rs232 signals (found that a simple rollover of the wires did the trick, i.e 1-8,2-7,etc.), but that did NOT ‘echo’ as expected.
------ DINC — port=/dev/ttyEL07 ------
9600 BAUD 8 NONE 1 SWFC=ON HWFC=OFF
CAR=OFF DTR=ON RTS=ON CTS=ON DSR=ON
Type ~? for help.
hello
world
DINC closing…
[root@lineker rkb]#
However, looking the stats for the line, I see that
the Tx and Rx count has incremented and are equal (the before and after stats are shown) as expected.
If you saw the data on the screen (which is indicated by the output you posted), the loopback test was successful. If the data hadn’t been looped back you wouldn’t be seeing “helloworld”. Or do you mean you typed that in manually when you made the post?
Exactly. When connecting to the port with the loopback plug inserted you should see what you type. With it removed, you won’t see what you type in dinc.
This shows that the port is looping the data you type back through the port properly.
I guess I misunderstood the behaviour of dinc. I guess, as I type, the chars are sent (immediately) like h,e,l,l,o, etc. Is that correct? In a normal app the keyboard buffer is sent to the app in a line-by-line basis, i.e the chars typed in are stored and sent to the app when the is hit (so I expected to see hellohelloworldworld).
I will recheck that cable according to the specs you posted earlier. Thanks for your support with this.