Rube Goldberg Code

[altenbach]

Ways to cast a two byte string to a number.

(the original seen here)

[wiebe@CARYA]

Careful!

The Unflatten From String solution is only the same if there are two (or more) characters in the string!

[altenbach]

---

wiebe@CARYA wrote:

Careful!

Yes, but here he is reading exactly 2 bytes from the network, so the size is guaranteed. 😄

[altenbach]

Converting three bytes into a floating point value (seen here).

I have the nagging feeling that we don't need anything green and much less orange.

[altenbach]

To a text programmer, this formula node probably looks very reasonable. I have the gut feeling that there are simpler alternatives. 😄 (seen here)

[altenbach]

Sometimes the Rube Goldberg is not in the code, but in the external wiring. (seen here)

Question: "Please share ... connection diagram of how everything is wired up"

Answer:  The encoder is connected to Counter 0 while the servo connections are made to the Counter 1. The Encoder has 5 cables and they go into pins 96 (+5V), 86 (DGND), 81 (channel A), 85 (channel B) and 83 (Z index). Servo has 3 cables and they go into pins 96 (+5V), 94 (DGND) and 91 (signal).

I already see the sparks fly!

[AeroSoul]

Jesus christ, that cable is completely shredded. How it didn't blow up yet is a real mystery.

[wiebe@CARYA]

Lots of lessons to be learned here (please pitch in 😋).

Some highlights (RB, Bugs, and other madness):

[altenbach]

Can you explain the up to three values for each time point? Are they related?

[wiebe@CARYA]

---

@altenbach wrote:

Can you explain the up to three values for each time point? Are they related?

---

I think there's time, and then 1, 2 or 3 (maybe more?) values. The graphs shows the 1, 2 or 3 values as a function of time. So I think those values are positions, and s(he)'s trying to correlate the positions to 1, 2 or 3 objects that move over time, in one dimension.  

But that is my interpretation.

I do see a strong coherence between bad solutions and bad explanations of the problem. 🙄