Think of it this way -- a serial cable is like a composite television cable. You plug it in and it shows up on the TV, more or less. There's not a whole lot of fiddling.
A network cable is more like an antenna cable. If you plug it in and see nothing, maybe you're on the wrong channel, band, protocol.... It can carry lots of different things at the same time, you have to select what you want.
This is why you can't just 'cat /dev/ethernetdevice' and see the raw data from your data logger. You need to know what IP address and protocol you want to get data from, and have to have your computer configured correctly to read it.
Is there a way it's supposed to be used? Absolutely but we don't know what it is yet since all the information we need to know is missing. You've refused to answer all our questions.
You've been asked repeatedly for information about the device you're trying to log from. What is it? What model is it? Chances are the device will not log information until you make a TCP connection to it. It might use telnet or it might use http or it might use something else. The information may be in its manual.
When you tried to make a network, presumably to talk to this device on, we asked you repeatedly what information you had for the various things on your network. Several working, cooperating pieces all correctly configured are are required for a working network; knowing
one computer's settings is less than half the story.
Moderator's Comments:
|
|
We cannot help you if you don't start answering questions. We are not being mean. These questions are essential.
|
|