My intent here was to be able to send requests to a set of requester chests supplied stations with a list of items needed for construction, resupply, and maybe personal long distance logistics. Although I found I can’t really arbitrarily send a train to a station via circuit signal without having all receiver stations except one be disabled.
I have that blueprint book but, never actually looked at the core module. If I woulda been able to reverse engineer what the heck is going on there it mighta saved me some headache. Hindsight is a bear
The easy solution to clock sync was to only have one clock. There's some funkiness required to TX a signal during the TX's clock cycle due to combinator timing but, I used that to my advantage on the RX side as it now only requires a single frame delay combinator to keep the signal alive 100% of the time.
Woo! Same! I'm working on a bit packing solution ATM. Should be more UPS friendly and more resource friendly :D
I think I was leaning into the clock method as it doesn't have an upper/lower limit to circuit values or number of distinct circuits. Actually as I'm typing this I realized concurrent signals would have to share a 32 bit address space greatly limiting the min/max values. Two channels already limits me to 2^16-1 assuming I want a signed value.
kk