The General Idea

About Forums Forum Suggestions The General Idea

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #929


    This is a great concept and straightforward.  I am confused about one thing though. In the example the person must know the IP address of the computer running the server.  If that server is on a Wi-Fi network and has a shared “external” ip, how can the mobile user be directed to the right computer? Also, does the mobile/other user always have to be on the same network? How could somebody passing by a storefront get on the same wireless network in order to communicate with breakout?


    The instructions for using BreakoutJS with a mobile device are only for using it on a local wi-fi network. BreakoutJS was created initially for rapid prototyping.

    However you could get what you are trying to achieve to work by using a router that can do port forwarding (most if not all wi-fi routers will do this). You’d need a static IP for the router (or you may be able to use dynamic DNS). You’d configure the router to forward messages to and from the static IP address to the local IP address on the network.

    For people outside to connect you could print a QR code that links to the static IP address. The trick to manage then is how to handle multiple users simultaneously. Breakout Server has a mode (under the settings tab) to enable multiple connections. Check that box. This works well when multiple users are viewing data (reading sensors). It’s much trickier if you’re allowing them to control actuators (leds, motors, etc) since only one user should have control over a single actuator at a time. Such a level of control would require a custom server implementation to properly manage the connections per feature. I don’t have anything like that planned for the future. That’s when the boundary crosses from prototype to production.


    I’m looking for BreakoutJS support for the arduino Bosch BMP085 / BMP150/ BMP180 module which is a barometric pressure sensor. They all do the samething.


    I am not the moderator of this board but perhaps you might want to ask your question on a different thread. Your post is a little off topic.

    However, your post did take me back to @soundalogous’ answer, which is so clearly written and helpful that I should have thanked him at the time of writing. So, here is a delayed thanks.


    @Akaplan. I have looked into adding support for that pressure sensor in the past. It appeared that there was a non-standard delay needed between sending two of the I2C commands and it was not possible to implement given the generic nature of I2C support in Firmata. I have this sensor so I’ll look into it again sometime in the next 2 or 3 weeks (I’m extremely busy right now… just finished moving across the country and am starting a new job tomorrow).

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.