configureGyroControlRegister1as an example here to simplify the space that we have to consider down to one register. But I would not recommend doing this in a real driver implementation. In both the Moddable SDK and our work at TC53, we combine all of the configuration options into one generic
configure(options)function that takes a single, potentially large options object and performs all of the configuration for the sensor.
configurefunction" implementation is in our LIS3DH driver that exposes its configuration options without regard to where on the device they actually live. More recent work that I've done for TC53 (driver implementations that are not yet in our public tree, because things are still moving around a bit there) take that a lot further by really exposing every option of the sensor.
outputDataRateproperty described above, it doesn't just mean 0x0 to 0x7. It means something like this:
outputDataRateproperty of the options object to take the values
952instead of the values
Alright, I'm going to call it a day here. Thank you for chatting, Donovan, and thank you to all the lurkers for stopping by to see what we're up to!
Our next office hour will be in a week or so. But please leave any questions, comments, or puzzles here in the meantime: a member of the Moddable team will get back to you in short order, even when we're not holding office hours. Cheers!
Hi, I recently bought a moddable two and three, and I have some issues with the wifi on Three, is this a good forum? Basically I can't connect nor scan,
examples/network/wifi/wifiscan just yields "Scan start" on the Three while it works fine on Two.
I'm running mcconfig as
mcconfig -d -m -p esp/moddable_three and
mcconfig -d -m -p esp32/moddable_two respectively.