![]() ![]() We don't recommend setting the charge rate below 100mA or above 500mA but as long as its well documented why you chose it, its fine. On the Cellular Feathers, its reasonable to require 750mAh or higher, and have the charge rate be 500mA. We tend to require no smaller than a 250mAh battery for WiFi/Radio Feathers. The connector must be in the same location, 0.425" from the left edgeĪlso, you must have some charge indication LED, we strongly recommend sticking a yellow CHG LED below the microUSB connector. If you are making a mainboard Feather you must have onboard LiPoly charging (its a core expectation) and the LiPo connection must be a JST 2-PH that matches Adafruit batteries. It should be 3.0-3.7V or so, with variable current capability. This is the power that comes from the 'optional' LiPoly battery. Boards that have names with the Express suffix also support CircuitPython for fast and easy programming. The Feathers and Wings all have example code written in Arduino C/C++ so as your projects adapt, all your wings and code will come along with you. Maybe build a project with a Feather M0 Bluefruit, then realize you need more range so you switch to a Feather M0 LoRa. So, other than a few exceptions (mostly the GPS Featherwing), you can re-use, re-cycle, and upgrade your Feathers and Wings between projects and as need arises.įor example, start out with a Feather 32u4, then decide to upgrade to the Feather M0 or M4 for more Flash - the pin out is the same! Or, make an IoT project with the ESP8266 and then super-power it with an ESP32 just by swapping out the main Feather. You can (in theory) add as many Wings as you like to a single Feather main-board, as long as you don't run out of power, space or have pin collisions.īest of all, we've tested all of our Wings against all of our Feathers. Wings are like little "shields" or "HATs" for Feathers. WavePlayer.Once you've picked your main dish (the Feather mainboard) you can pick and choose from a wide wide variety of Wings. The package is also still available through bower, although this will be faded out eventually bower install waveplayer.jsĪfter that the package may be directly included using a tag: This package is available through npm: npm install -save waveplayer If the JSON contains an associative array, only the first entree will be used. It is enough to provide a single array of floating point values. There exist a number of tools for extracting waveform data in JSON format from an audio file wav2json or py-wav2json can be used for instance. An error will be thrown if this JSON file does not exist and no waveform data was passed in explicitly as a second argument to the load() function. When supplying a JSON file, it should have the same name as the corresponding audio file and should exist at the same location. In order to minimise waveform drawing times it is necessary to supply an URL to a JSON file or a data array / object representing the waveform of the audio file numerically. Waveplayer.js is tested to work on Chrome, Firefox and Opera (no support for Internet Explorer yet). License: MIT Browser Support & Other Requirements Inspired by wavesurfer.js and waveform.js, but different. An HTML5 based audio player with a waveform view.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |