The FrogPad
 
A forum to get help or talk about Roastmaster…or anything else coffee.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rswift

Pages: [1]
1
Wish List / Re: Data Logging from DIY kit
« on: August 31, 2016, 05:25:39 PM »
Just wanted to say thank to Danny for his work in the background moving my request forward... I never expected such interest, very excited to see things move to a version that my custom hardware can transmit temperature readings to :)

Cheers - Robert...

2
Wish List / Re: Data Logging from DIY kit
« on: July 17, 2016, 08:54:29 AM »
Hi Danny,

This sounds great, thanks for the update. I am using iPad (I do have an iPhone too, but don't use Roastmaster on it) so looking forward to being able to float some datagrams around and see the results appear :)

Cheers - Robert...

3
Wish List / Re: Data Logging from DIY kit
« on: July 12, 2016, 05:43:42 PM »
I posted some ideas about the JSON structure here: https://github.com/rswift/wifi-temperature-broadcast/wiki/JSON-Payload-Format

Hope it is useful :)

Robert.

4
Wish List / Re: Data Logging from DIY kit
« on: June 28, 2016, 06:13:27 PM »
Excellent stuff, and Dublin isn't a bad place for drinks other than coffee :)

I'll keep my eyes out for progress :)

Cheers - Robert...

5
Wish List / Re: Data Logging from DIY kit
« on: June 26, 2016, 08:32:57 AM »
I've been thinking more about how to link up DIY kit via the Data Logger feature. The broadcast app I've written uses JSON, but equally could have used XML. I think a text based format makes sense over binary, there isn't much data so little/no need to compress the data itself.

The format I've used is:

{
  "celsius":" 123.45,
  "fahrenheit": 254.21,
  "probeName": "Gené Cafe Bean Mass"
}

and I have an optional "debugData" (broadcast rate, some internal data etc.) if debugging is enabled within the broadcasting app:
{
  "celsius":" 234.56,
  "fahrenheit": 454.21,
  "probeName": "Gené Cafe Bean Mass",
  "debugData": {
    "key": "value", ...
  }
}

So, I'm thinking that within the probe setup, a "DIY" probe could be added, a push/pull data collection (in my current code it'd be a push from the probe, but I've already started to think about a pull whereby the probe broadcasts details of itself including properties such as "serverPort" so a client can then make a basic HTTP GET request to pull the data on demand).

I can see from the data logger feature you have the concept of ports, so mapping the DIY probe could be via a given UDP broadcast port number, or preferably a unique identifier such as the probe name (two reasons, firstly I may have multiple probes from one ESP8266 broadcast unit, and secondly there will probably only be a few probes at most, and logical naming makes a great deal of sense).

Then all it'd need would be a simple mapping of metrics that Roastmaster needs to fields in the text based payload, so "celsius" to a °C curve for example.

BTW: I've splashed out the £10.99 to buy the data logging feature to see what it provides, even though it is useless to me at the moment, so I do hope all this comes to fruition :)

Logically this could be taken a step further too, things like fan speed, voltage, even ambient temperature could be logged.

It'd make sense to structure the payload to permit multiple probes, so maybe more like:

{
  "readings": [
    {
      "probeName": "Gené Cafe Bean Mass",
      "reading": 234.56,
      "scale": "C"
    },
    {
      "probeName": "Gené Cafe Air Inlet",
      "reading": 234.56,
      "scale": "C"
    }
  ],

  "systemInformation": {
    "someKey": "someValue",
    "aDifferentKey": someNumericValue
  },

  "debugData": {
    "debugKey": "debugValue", ...
  }
}

Cheers - Robert...

6
Wish List / Re: Data Logging from DIY kit
« on: June 20, 2016, 07:39:50 PM »
Hello Danny,

Sincere apologies for the tardy reply, I've been doing some tinkering but not had as much time as I wanted over the last few weeks.

I would be more than happy to beta test anything. I've put my Adafruit code up on Github (https://github.com/rswift/wifi-temperature-broadcast/blob/master/WiFiTemperatureBroadcast.ino) and I've prepared a basic iOS app to listen for the broadcast messages (https://github.com/rswift/iOS-WiFi-Temperature-Receiver).

I strongly suspect the payload is lacking in content and possibly finesse too?

It'd be interesting to know what Roasthacker thinks about integration with a native iPad app, I am sure it'd be an interesting avenue to explore! http://roasthacker.com/?page_id=65 is the latest, I'm going to post a link to this forum post up there.

Thanks again - Robert...

7
Wish List / Re: Data Logging from DIY kit
« on: April 29, 2016, 03:09:19 PM »
I should have added, there is always Bonjour/Zeroconf too - basically any means of the app running on iOS to find the host server. The API would then be implemented there, so Roastmaster would HTTP GET the value and expect a response in an appropriate format.

Just a thought.

Robert.

8
Wish List / Data Logging from DIY kit
« on: April 29, 2016, 02:49:43 PM »
Hello,

The app is great, I'm using a Gene Café CBR-101. I recently stumbled upon a web site called Roast Hacker, there are a couple of great articles about adding a thermocouple directly to the rotating drum: http://roasthacker.com/?p=529

I've built the probe and am hacking the software a little. I don't have the Data Logging feature of Roastmaster, I did wonder if I could mimic the Phidgets setup, but that's not looking easy...

So I'm wondering, is there an option for Roastmaster to have a Data Logging feature whereby either, you publish a specific API to poke temperature readings into (sensor placement [bean mass, ambient, whatever], temperature value etc.) and a means of discovering that service on a local WiFi network, or, a simple multicast message to a given (configurable) port could be implemented to enable anyone to code up any device to broadcast a trivial UDP packet to the local network, to be swept up by Roastmaster?

It'd break the dependence on a very specific set of devices, those of us who want to tinker with the growing number of things from people like Adafruit (the kit roast hacker uses) could easily integrate. Roastmaster would still make money from the Data Logger feature, a handful of config properties could make it very easy to customise and like I say, it breaks your dependence on a very specific hardware components :)

Thanks in advance - Robert...

Pages: [1]