Hello, I am currently trying to set up an Etherlite 80 with my Ubuntu computer. I have set the IP to 30.2.2.101, and my computer’s IP is 30.2.2.2. I installed the driver per the instructions here (http://www.digi.com/support/kbase/kbaseresultdetl.jsp?id=3052), and it produced no errors, from what I could tell. I ran the utility /usr/bin/dgrp/config/dgrp, which showed the Etherlite, and started the daemon using the menu.
I can successfully ping the unit, but when I attempt to rlogin to the unit, it hangs and never terminates or outputs anything.
Based on advice from the troubleshooting guide, I powered off the Etherlite and pinged that IP, and there was no response, indicating that it’s not a duplicate IP.
Also, based on advice from the “Etherlite Rlogin Guide,” I modified my /etc/hosts file with the entry “30.2.2.101 etherlite80.” This had no effect; I still could not connect with either “sudo rlogin 30.2.2.101” or “sudo etherlite80.”
A separate (or perhaps connected) issue:
I have my Etherlite80 set up to have 8 ports, with the prefix AS. I can see the ports /dev/ttyAS00 through /dev/ttyAS07, but when I attempt to connect to them with minicom, I get a “file not found” message. Is this simply a problem with minicom? Is there another simple way to test a serial connection?
There are a couple of rlogin versions floating around on Linux, try specifying the full path:
/usr/bin/rlogin (IP_of_Etherlite)
Not sure why minicom is not able to connect. Try using the dinc utility to connect to the port:
dinc 9600 /dev/ttyAS00
Also, make sure the EtherLite unit is running RealPort capable firmware. This can be checked with rlogin and the version number should start with a number 1.
Thanks for the response.
specifying /usr/bin/rlogin makes no difference.
As for dinc, I don’t really understand this utility, so here’s the output (i typed the characters printed out after the “Type ~? for help” line, then typed ~? again and it displayed the help information):
sudo dinc 9600 /dev/ttyAS00
------ DINC — port=/dev/ttyAS00 ------
9600 BAUD 8 NONE 1 SWFC=ON HWFC=OFF
CAR=OFF DTR=ON RTS=ON CTS=ON DSR=ON
Type ~? for help.
~?
?
~
?
~
DINC tilde cmds:
(±)Baud Csize Dtr Framing Hwfc Info breaK Modem Oflush Parity Rts Swfc eXit
DINC closing…
I’m not sure why rlogin is not working. Did you run it as root?
Anyway, the dinc results show you are successfully connecting to the port. However, whatever is attached to the port does not appear to be communicating. What is attached to the port? What cabling pin-outs are being used?
Running dpa.dgrp as root may show more details about the port signals/settings.
Also, check the baud rate, parity, flow control, stop bit settings on the attached device to confirm they match the Digi serial port.
I ran rlogin with “sudo,” which I believe is the same as running it as root. (As a side note, isn’t sudo the same as su, but for one command? If I type su, then enter the password that works for sudo, I get an Authentication failure. How is that?)
I have a unit hooked up to the port. This unit should output version and other information over the console port whenever it is rebooted, but minicom does not show it. By the way, minicom now runs properly (but still doesn’t show output)… I think that problem was a fluke.
I ran dga.dgrp, it shows the Etherlite as “Available.”
Looks like the parity should be none, flow control should be off, and stop bits are correctly 1. Didn’t see anything about Baud rate. How can I change the Digi serial port settings to match these?
Also, I should say that I’m using Ubuntu, which may have some issues with serial ports. I couldn’t get a USB-to-serial converter to work a few weeks ago, so just keep in mind that this may be an OS issue, though I have tried to fix it before.
Haha, is it safe to assume that this is the same person dealing with my support request? If so, we should limit this conversation to one area.
I’m not sure what you’re asking for when you ask for “cabling pinouts.” I told you which pins are being used; beyond that, I’ll need instructions if I’m to give you information about the pins.
I should say that I switched out my serial connector for another one that is known to work, and this did not fix my issue.
Quick update:
I have tried the following configurations, the results of which point to a problem in either the Etherlite or the computer or something about their interaction:
My computer, my Etherlite, my unit, my connector: doesn’t work.
My computer, my Etherlite, my unit, other connector: doesn’t work.
My computer, my Etherlite, other unit, other connector:
doesn’t work.
Other computer, other Etherlite, my unit, other connector: works.
Other computer, other Etherlite, other unit, other connector: works.
Note: for all of the above tests, the Ethernet cord used corresponds with the Etherlite used. Thus, if the other Etherlite was used, so was the other Ethernet cord. I am using a brand-new Ethernet cord, which I just tested by connecting it to my computer and the switch, and it worked.
I would like to use my computer with the other Etherlite, but it would seem that that can create more issues than it solves; setting up the interaction between the computer and the Etherlite takes a few steps, and it is likely an issue with that setup that is causing the problem.
Please tell me if you’d like me to take a particular action, and thanks again for your help.
I got it working! Thanks for your help!
rlogin still doesn’t work, but I can successfully see output from the unit. I just copied the minicom settings from the other computer onto this one; I thought that it was the same, but apparently that was for a different profile.
Thanks again, and sorry to take up your time with a problem the Etherlite wasn’t actually causing (though I still wonder about rlogin).