jdlombardo
About
- Username
- jdlombardo
- Joined
- Visits
- 95
- Last Active
- Roles
- Member
Comments
-
metawear.InitializeAsync(); metawear.GetModule().EraseAll(); metawear.GetModule().ResetAfterGc(); metawear.GetModule().DisconnectAsync(); [ wait, scan, find it again... ] metawear.InitializeAsync(); metawear.ReadDeviceInformationAsync(); …
-
expected v actual: * expected: programs / macros erased, LED & neopixel turned off / deallocated. * actual: programs / macros erased, neopixel stays lit and is not controllable please note that i did not yet do exhaustive testing with …
-
tested. it does not do what we need.
-
as mentioned in my last, the macro side doesn't really address the full problem. regardless of that detail, we've gotten a little off track. we're trying to move from the iOS SDK to the C# SDK. one of the features we've been relying on for years …
-
that doesn't help with the second need to reset the neopixel. our goal is to reset the board fully to a known-good configuration as part of the connection sequence. this is a sort of sledgehammer approach but given various issues we've had in day…
-
for our application we do need to erase macros and do the setupEvents / runOnDeviceBoot piece. we also use that call for the secondary purpose of resetting the neopixel hardware. if there are reliable ways to do both of those via other means, that's…
-
sorry, i misremembered the precise name. there are two options in the (old?) iOS API app and SDK. 1) in app: "Soft Reset" / in iOS SDK code: "resetDevice" Perform a software reset of the device. 2) in app: "Reset To Factory Defau…
-
> do all LEDs in the strand end up having the same tone? not sure, i'm using a single-neopixel "strand". i can build an strand with multiple neopixels next week and see. > How repeatable is the result? (marginal timing should genera…
-
@Matt thanks for the info. odd indeed. FYI: in continued testing I'm seeing some more issues on the 0.6 boards w/1.3.7 - in "slow" mode, red / green / blue work properly but after turning any of the colors on, the "turn off" command…
-
@Matt interesting, thank you. fast mode works fine with 0.6 RG boards w/1.3.7 firmware. is only odd that the same neopixels need slow mode to work properly on 0.5 RG boards w/1.3.6 firmware ¯\_(ツ)_/¯ it's easy enough to put a switch in…
-
individual ones of these: https://www.adafruit.com/product/1558
-
addendum: this is on neopixels that should work with the "slow" setting. normally they do not work at all with the "fast" setting, so right now it is somewhat of an inversion of expected behavior.
-
thank you. this mostly works. if the "driver speed" is set to "Fast" it works fine. if the "driver speed" is set to "Slow" setting the colors works, but turning the neopixel to "Off" does not entirely work; it ends up with a dim glow from the L…
-
very good, thanks!
-
thank you very much! do you have an ETA? we have some customers waiting on these.
-
...everything works fine on an older RG board (hw 0.5 fw 1.3.6)
-
ahh, thanks!
-
...and it's fixed in 2.11.1 thanks!
-
one additional method would be a great help: SequenceLed ([item, item, item], repeat, pulse, sync, delay) the first argument is an array of flash or solid commands then a number of repeats and pulses, like the current flash pattern, …
-
adding four arguments to both the FlashLED and SetLED methods could be very helpful and flexible. —————— bool SyncPattern [ only relevant if LED is currently flashing, no effect if LED Is solid or dark ] false = execute new settings i…
-
in the short term: it would be wonderful to change the behavior so that setLEDColor sets the new values immediately, without the extra clearing step. even without the clearing step, there seems to be a lag between the event and the LED change. the…