Code Monkey home page Code Monkey logo

microflo-core's Introduction

MicroFlo: Live dataflow programming for microcontrollers

Build Status

Unlike most other dataflow runtimes for constrained devices, MicroFlo run standalone on the microcontroller, can be introspected and reconfigured at runtime, and has built-in support for automated testing.

One can program with MicroFlo either:

  • Visually, using Flowhub
  • Textually, using the declarative .fbp DSL or .json definition
  • Programatically, by embedding it and building a graph using the C++ API

MicroFlo is very portable, written in C++03 without exceptions and stdlib. It comes with support for multiple platforms,including Arduino and Embedded Linux. It has been used on many different devices, from Atmel AVR8 to ARM Cortex M0/M1/M3/M4 devices (LPC mbed, TI Tiva/Stellaris), ESP8266 and Raspberry PI.

MicroFlo is designed to integrate with other data-driven programming tools, including msgflo for easy building of distributed systems (IoT).

Using

For visual programming your Arduino, follow the microflo-example-arduino.

Support

Flowhub logo

MicroFlo is a part of Flowhub, a platform for building robust IoT systems and web services.
We offer an Integrated Development Environment and consulting services.

Status

Minimally useful.

  • Works fine for simple programs
  • Components exists for standard I/O on Arduino devices
  • Live programming supported for most changes
  • Basic support for automated testing

MicroFlo in the wild:

  • Jon's fridge thermostat has been running uninterrupted since September 2013.
  • The Ingress table at c-base station, Berlin uses MicroFlo to control the lights. One major upgrade/bugfix since March 2014.
  • The lights on the CNC-milled Christmas tree at Bitraf, Oslo ran for 4 weeks during Christmas 2013.

Contact

When you find issues: file bugs and/or submit pull requests!

Changelog

Past milestones

Extending

For porting MicroFlo to other microcontrollers, see how-microflo-works and target bringup.

License

MicroFlo is released under the MIT license.

Note that the platform MicroFlo runs on (like Arduino), and MicroFlo components may be under other licenses!

microflo-core's People

Contributors

bergie avatar greenkeeper[bot] avatar jonnor avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

Forkers

mfkiwl

microflo-core's Issues

An in-range update of grunt is breaking the build 🚨


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency grunt was updated from 1.0.4 to 1.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v1.1.0
  • Update to mkdirp ~1.0.3
  • Only support versions of Node >= 8
Commits

The new version differs by 8 commits.

  • d5cdac0 Merge pull request #1706 from gruntjs/tag-neew
  • 4674c59 v1.1.0
  • 6124409 Merge pull request #1705 from gruntjs/mkdirp-update
  • 0a66968 Fix up Buffer usage
  • 4bfa98e Support versions of node >= 8
  • f1898eb Update to mkdirp ~1.0.3
  • 75da17b HTTPS link to gruntjs.com (#1683)
  • 6795d31 Update js-yaml dependecy to ~3.13.1 (#1680)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of microflo is breaking the build 🚨

Version 0.3.44 of microflo just got published.

Branch Build failing 🚨
Dependency microflo
Current Version 0.3.43
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As microflo is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 38 commits .

  • b389f54 Bump
  • f431e89 Merge pull request #104 from microflo/live-programming
  • 1ab7e30 runtime: Fix exception when removing some IIPs
  • 8cf5319 runtime: Basic support for live programming, opt-in
  • c5bf42f runtime: Only reset microcontroller on start, not stop
  • fd2ab05 Merge pull request #103 from microflo/remove-node
  • d0bf719 commandformat: Update checked in file
  • 603139c commandstream: Support for removenode
  • d2bb1aa engine: Implement removing nodes
  • ee8c1d8 AVR/Tiva/ESP/Mbed: Also support delete(.., size_t)
  • ff7fd18 Merge pull request #102 from microflo/more-protocol
  • 0f78e27 commandstream: Skeleton implementation of connection removal
  • 44e45ba engine: Implement removing a connection
  • 5d9e242 commandstream: Support new NetworkStop message
  • c4e0b7e engine: Separate stop() from reset()

There are 38 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of coffee-script is breaking the build 🚨

Version 1.12.3 of coffee-script just got published.

Branch Build failing 🚨
Dependency coffee-script
Current Version 1.12.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As coffee-script is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 23 commits .

  • 635e207 Update release date for 1.12.3
  • e87d574 Merge pull request #4429 from GeoffreyBooth/1.12.3
  • b89dd04 Add other 1.12.3 updates to changelog
  • 8ce7c30 Update generated docs for 1.12.3
  • 45d0a7d Update browser compiler for 1.12.3
  • 7291277 Bump version
  • 6d27277 Update documentation for 1.12.3.
  • 3108244 Fix stack trace (#4428)
  • d0ed2de Merge pull request #4420 from GeoffreyBooth/backport-2-doc-changes
  • a61429c Updated output
  • fbdfa65 Apply SVG fill color through CSS
  • 02198eb Fix link to Try CoffeeScript
  • cd8be89 Trim the installation and usage sections; can backport to v1
  • b398c88 Fix releaseHeader for the initial release; should backport to v1
  • f4353fa Merge pull request #4417 from BrianRossmajer/patch-1

There are 23 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of microflo-emscripten is breaking the build 🚨

Version 0.3.42 of microflo-emscripten just got published.

Branch Build failing 🚨
Dependency microflo-emscripten
Current Version 0.3.41
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As microflo-emscripten is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 2 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.3.0 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/microflo/microflo-core/builds/225139806)

Release Notes coverave

Thanks to all our contributors, maintainers, sponsors, and users! ❤️

As highlights:

  • We've got coverage now!
  • Testing is looking less flaky \o/.
  • No more nitpicking about "mocha.js" build on PRs.

🎉 Enhancements

  • #2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
  • #2769: Support --inspect-brk on command-line (@igwejk)

🐛 Fixes

  • #2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)

🔍 Coverage

🔩 Other

Commits

The new version differs by 89 commits0.

  • fb1687e :ship: Release v3.3.0
  • 1943e02 Add Changelog for v3.3.0
  • 861e968 Refactor literal play-icon hex code to a var
  • 1d3c5bc Fix typo in karma.conf.js
  • 9bd9389 Fix spec paths in test HTML files
  • 0a93024 Adds tests for loading reporters w/ relative/absolute paths (#2773)
  • 73929ad Comment special treatment of '+' in URL query parsing
  • e2c9514 Merge pull request #2769 from igwejk/support_inspect_break_in_opts
  • 038c636 Support --inspect-brk on command-line
  • b4ebabd Merge pull request #2727 from lamby/reproducible-build
  • 882347b Please make the build reproducible.
  • a2fc76c Merge pull request #2703 from seppevs/cover_utils_some_fn_with_tests
  • ed61cd0 cover .some() function in utils.js with tests
  • f42cbf4 Merge pull request #2701 from craigtaub/landingSpec
  • 6065242 use stubbed symbol

There are 89 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of fbp-spec is breaking the build 🚨

Version 0.1.18 of fbp-spec just got published.

Branch Build failing 🚨
Dependency fbp-spec
Current Version 0.1.16
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As fbp-spec is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 9 commits .

  • 56a03a5 Bump
  • d16905e Travis: Update NPM deploy key
  • 3f7a616 Bump
  • fb8ba64 Merge pull request #86 from flowbased/fix-webpack
  • a211271 ui: Get React from NPM
  • 4216574 ui: Only include for browser build
  • 7295b67 browser: Let webpack/browserify avoid CoffeeScript
  • 0004c68 NPM: Make sure browser/ is included
  • 7f45523 browser: Use browserify instead of grunt-noflo-browser

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.