Link to home
Start Free TrialLog in
Avatar of sinnedph
sinnedph

asked on

NIC Programming

I'm planning to make use of the NIC to control and read devices (such as Ph Device, Airconditioners, etc.) since there are 2 input and 2 output if you use ethernet. Any help regarding how to control NIC. I believe it would be possible for Parallel printer port and serial port but I don't know if it's possible for Network INterface Card. Any information is highly appreciated. Thanks!
ASKER CERTIFIED SOLUTION
Avatar of Jaime Olivares
Jaime Olivares
Flag of Peru image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
As a personal experience, I recommend you to use Ethernet ports instead of USB for many reasons:
- USB is harder to program than Ethernet, Ethernet is as easy as create a Socket object and use Send() function
- USB microcontrollers are harder to program than Ethernet
- USB is intended for near peripherals not for mid- and long-distances
- USB hardware is less fail tolerant, it is easier to build a ethernet cable than a USB cable
Avatar of fulscher
fulscher

Well, it certainly depends on the requirements.

The USB module I thought of contains insulated inputs and outputs, so it shouldn't be sensible at all to external influences - you can even connect certain devices directly to the inputs, as long as the voltage is below 24V. The outputs are protected by relays, so you again can connect low-voltage devices directly without additional electronics. I would imagine that programming them with the included software modules is just a matter of a function call (something like Port1 = FALSE). I'm not sure about this, though; check the docs.

For most other ports (Ethernet, parallel port, serial port, etc.) you'll need additional hardware for the insulation and protection of the main board - add this to the cost of the chip, and you'll end up at similar prices ($100+), without accounting for the time required to assemble the device.

But of course, for long distances, Ethernet is a good solution. You could also use RS485 (can be used over Ethernet cable, is much less sensitive to electronic noise, allows for distances of several 100 feet). Or you could use a TCP/IP-to-Serial converter with additional logic and hardware and transmit the signals over a WLAN. Or use two TCP/IP-over-Powerline adapters and again a TCP/IP-to-serial converter. There are probably many more options. It all depends on what you need and want to spend in terms of money and effort.

J