-
-
-
-
@DrAzzy Well in the example i drew i didn't hook it up to the original power supply, but i included a image from the oscilloscope reading of the original power supply in my first post.
-
-
-
-
@DrAzzy Here is a quick and dirty painting
-
@DrAzzy Haha, thanks for the answer. I placed this project on the shelf over the summer, but you sparked my interest again. I will send a photo when i get the time.
-
-
Thanks, that's great ! What do you mean by defining it as a number ? the reason has to not match that specific number right.
Isn't that constant already defined ?
define BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION 0x13 /**< Remote User Terminated Connection. */
Do you mean that i should define it as 0x13 ? -
Hey i'm trying to to do different things depending on what reason the ble disconnect says. Hard to view this live and debug.
Got a MDBT42Q module hooked up the bangle. I wish to differentiate the gatt.device.disconnect() (user terminated disconnection) event and the event when range is reason to disconnect. Is this possible ? and what events might those be ? and how do i check them.
Currently i do this with no luck, it seems that the same event is fired for both types of disconnection.
NRF.on('disconnect', function (reason) { if (reason !== BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION) { standardBuzz(); } connected = false; });
Standard buzz never happends.
-
@jeffmer Ah.. Thank you !
-
Hey i'm writing an application for controlling a MDBT42q module but i'm having issues with the connect disconnect events.
I want to do a Bangle.buzz on connect/disconnect but they never fire.
This should fire once i disconnect but no luck.
NRF.on('disconnect', function() {Bangle.buzz()})How could i debug this further ?
-
I am trying to power a low voltage tungsten halogen bulb using an MDBT42Q and an IRF3708 mosfet
The lamp is a KANDOLite 6v 50w.Im trying to replicate the signal coming from another driver that successfully powers the lamp.
The images with all statistics included is the original working solution.
There is one image when the lamp is connected and one without the load.The image with fewer statistics is the signal from the drain pin in my solution.
Generating the pwm signal with MDBT42Q feeding it to the mosfet gate and powering the lamp with 6v. But no luck. Is it even possible to do this ?
-
Well thank you all for your comments, you all made me realize it was doable hehe..
Here you go
https://github.com/espruino/EspruinoDocs/pull/530Maybe i can improve some stuff, like could probaly make the user send in the i2c instance so it can be used with other devices on the same pins ?
-
Hey im trying to read the temperature and humidity from the AHT10 and im just stuck. I hook up the SCL an SDA with software ic2 and then i try to read on 0x38 and 0x39, 6 bytes.
The response is
[25,0,0,0,0,0]
And
[255,255,255,255,255,255]These vales doesn't change when i change the temperature. Whats the next thing i could try ?
-
-
-
I would love some code snippets ;)
They dont seem to provide the schematic directly but i bought this one
What i mean with the normal 3.3v pin is the pin that always just supplies 3.3v, i dont know how to target that pin through code. I will upload some videos of the application.
-
Thanks for your replies ! I did some investigation based on your answers and then it hit me.. I was driving the 3.3v side of the logic level shifter from Pin D25 with pinMode as 'input_pullup'.. bad idea. Moved it to normal 3.3 v pin. Now everything works smooth, first led works, dual strips.
Do you know why that was not working ? -
Hey so i got it to work thanks to the logic level shifter. But 2 other problem arose. I can't write to 2 different pins, which drives 2 different neopixel strips. Both are 9 leds long. Also cant seem to get the first LED lit up on either of the strips.
So once i write to 2 the API freezes and i need to reset the board before i can write to any again.
Im using pin D16 and D18
-
Well now i can verify that your fix works. Glad i could help and thanks !