Theoretical train design

Discussion

With all these train layout designs and ideas (Omnistop and the such). Has anyone attempted to build a train system based off of Ethernet? I mean the over head at each stop might be over the top to make it super viable. But 802.3 is a solid protocol that works with 2 data wires. Logical circuits have 2 wires... and in theory the space for wayyyyyyy more spacial streams.

Just thought I would get that idea out there and get an idea of the feels from the community.

Posted Oct 15, 2019, 10:57 PM UTC

37
BlandblBurn All Blueprints•

How exactly do you mean to implement 802.3 in terms of factorio? Perhaps it's because it's morning but I can't seem to get my heard around it.

Nothing complicated but personally I use the ip addressing system to simply name my train stops.

Eg.

Iron.1.4.0

Uranium.2.1.0

Iron.1.4.1

Iron.1.4.2

The first "byte" is resource type, second num of locomotives, and third num of non locomotives wagons. The fourth type is for type of station i.e. 0 for unloading and 1 for loading. >1 additionally for different designs and trains that may be incompatible with the first two or if I simply want to create a type c subnet for splitting my trains. This system easily allows identifying and assigning different train designs to my train network.

2
Carhugar1OP•

I mean you implement the MAC protocol over 1 of the lines. So you use a broadcast signal to request a train containing iron then someone sends a acknowledge stating they are sending the train. Since everything on the logic network line is instant you can see if there are collisions and such at the mac layer, thus you should be able to run a simple csma/cd implementation.

1
BlandblBurn All Blueprints•

Hmm I don't think you have to worry about collisions and I think you can do this over one data wire since it's full duplex. You could send different requests with the different ores and acks with different colored signals or the letters. I think csma would reduce throughout especially with megabases with multiple stations constantly needing to send requests. Or maybe I'm failing to just imagine a way to handle multiple requests with csma

1
Carhugar1OP•

Right but if 2 requests got sent out at the same time they would overlap on the wire and potentially mess up the underlying requests thus I figured collisions would occur.

1
Nezerin:train:•

Isn't something like this what Intangir and Haphollas are sort of trying to do?

They're using vanilla circuits to create train networks that allow for dispatching only the number of trains that you need to retrieve the proper amount of resource. They also allow for multiple patches of the same ore to be utilized at the same time.

Is that what you were getting at or where you wanting to do something more?

0
nemotux:circuitblue:•

What Intangir and Haphollas did was design protocols for communicating specific bits of information across the network - "need more iron ore", or "iron ore ready for pickup". These are implemented directly w/ the capabilities of the circuit network.

What OP is suggesting is to build a generic communication protocol on top of the circuit network (specifically 802.3) that would then allow arbitrary packet-based communication at a higher level. To send a signal of "need more iron ore", you would not be sending out the iron ore w/ value 1 signal directly on the circuit network. Rather you would be encoding that information in a binary packet of data.

1
Nezerin:train:•

Okay, that makes more sense. Thanks!

1