Yes, absolutely you can ditch the network protocol layers and send data 'directly'. But, you probably don't want to. What you do is use standard Ethernet Phy's, magnetics, and connectors.

But instead of using an Ethernet MAC (media access controller) you use an FPGA to send/receive data without the network overhead. This has been done for several 'not quite Ethernet compatible' interfaces like, and other industrial protocols. One thing that you can't ditch is the packet nature. You must still transmit data in packets of 64 to about 1500 bytes (some Phy's allow packets up to 8192 bytes). You can't transmit packets smaller than 64 bytes, or larger than 1500. And you must allow for the proper 'gap' between packets. But you have complete control over what is in the packets, and any header (if any).

Solarwinds Orion 10 3 Keygen Idm. Mobile Controlled LED Light Strip. Here at NetBurner, we love coming up with cool projects to show of some of the devices we've built, and there's not much out there that is cooler than LED light strips. In this video, we demonstrate just how easy it is to set up a platform independent, mobile ready control panel that allows. Sending Commands to a device via Serial Port. I hope anybody can help, I am involve in process where we're programming a unit CPU or Controller.

I am glossing over lots of details, however. It's actually not all that easy, and the requirements are different depending on which Ethernet standard you want to use (10/100/1000 mbps). In some cases there are signal encoding issues to deal with. I would advise that you not do this to Ethernet. It requires a large amount of skill to design the FPGA logic-- skill that most people do not have. And the benefits of doing this are minimal. It's much easier to simply use the standard Ethernet controllers and the associated protocol stacks than to dream up your own thing.

@supercat That's not entirely correct, at least not in this context. Shorter packets might be OK, but longer packets would not be (unless spec'd in the Phy datasheet). The Phy is doing something called 'Baseline Wander Correction'. Normally the Phy uses the inter-packet gap to recalibrate the baseline. If this is not done frequently enough, it goes out of whack and you get data errors.

Modern phys with better BWC allow for longer packet lengths (a.k.a. Jumbo Packets). Collision detection does play into it, but that's not the whole story. – user3624 Jan 5 '12 at 16:44.

You can indeed run RS232 over Cat5 ethernet cable. Routers and similar devices sometimes have serial 'console' ports with 8P8C modular sockets (RJ45 jacks).

However if you want to send serial data through an Ethernet NIC without actual Ethernet packets appearing on the wire, you are out of luck. On the other hand, many manufacturers sell serial-to-ethernet converters which can be used in pairs to transparently connect serial devices using Ethernet infrastructure. Search for 'Ethernet Serial' Sometimes these come with 'ComPort Redirector Software' that create a Virtual Com port on a computer. These probably work with most applications that expect a real serial port. They may not work if you are doing low-level bit twiddling. Based on your question I think I know what you want, but I want to clear some things up first. • Ethernet (or as the standard is called ) is on layer 2 () of the.

• The wire (the cat5/6 cable and connectors) are actually defined in Layer 1 (), You may have heard of the term before, that is defining the physical layer. • Ethernet does not have to run over 100BASE-T, and 100BASE-T does not need to carry Ethernet Now on to your question: that will carry serial over 100BASE-T but will not do any encapsulation. Download Saint Seiya Inferno more.

These devices will not work with your home network as your switch/hub/router is expecting IEEE 802.3 packets to be coming down the wire and not Serial packets. That will do serial over IP but it does not have to use 100BASE-T cable (or Ethernet). No, not with what is usually understood as the 'physical layer' of ethernet. This includes the cable, magnetics, and the PHY (stands for 'physical'). Even at the physical layer, you're not just sending arbitrary 0 and 1 levels to the other end. There are also multiple things called 'ethernet' that are different at the physical layer. There is the original, 10base-2, 10base-T, 100base-T, etc.

The older slower ones used manchester encoding if I remember right. At 100 Mbit/s things were changed to achieve the higher speed. Even if you restricted yourself to the old 10 Mbit/s manchester encoded versions the answer would still be no. Data is inherently sent in packets.

These have a preamble private to the phy layer which is used in part for collision detection (in some variants), clock synchronization, and start of packet identification. Then there is some out of packet signalling, like link pulses, which is handle in the physical layer. Since ethernet is transformer coupled, everything has to happen at some minimum frequency since the DC level is lost from one end to the other. This is one reason for manchester encoding.