Proper technique needed to nest a setWatch() within a separate setWatch()

Quick update as I realize it is late by you, . . . with more testing to do,

'This is more to humour Robin'

Okay humored! (sic US sp)

L2 spi.setup({mosi:D14,sck:D15});

Took a bit to get up and running, determined PulseView software requires MISO to be included also, for the protocol decoder to work.

With using just the code from #15

First thing I noticed is the active state on the pins is not the same. Clock phase. As pinMode() isn't used, I'm guessing looking at default and setup will uncover that.

Added a setInterval() on send side MDBT42Q so I didn't have to keep pulsing that side, and kept the bus quiet for at least a full second.

Without the CS detect, the WiFi slave side does decode as in #15

MDBT sends out 8usec clock ~100KHz


I don't see any major differences, except for the CS state inclusion.

Speculation here: Sanity Check

Commented out strings, outside of functions are not included in the upload? (yes?)

Inside the CS setWatch() during development, I placed console.log() statements to see what was going on. Had a hunch that the update to the WebIDE console window was getting bogged down, as it took a while to Ctrl+C out. I commented out ~three debug statements, and the console updated fine.

HUNCH: Even though the console now appeared to be updating without noticeable delay, that in reality, the commented out lines were causing a delay in the setWatch() read perhaps?

Off for coding CS inclusion and more testing . . . .