Recent Posts

Pages: 1 ... 6 7 [8] 9 10

Support / Re: RDP probe unlinked/offline

« Last post by KasperV79 on June 13, 2019, 05:07:47 AM »

Thanks for quick answer:

heres copy of log:

I added the RDPevent meta type as tes to see if that did the trick. but it didnt do any different.

WiFiconnected with IP Address: 192.168.1.253 Mask: 255.255.255.0
Transmitting SYN datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":0,"RPPayload":[{"RPEventType":1}]}
Transmitting SYN datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":1,"RPPayload":[{"RPEventType":1}]}
Transmitting SYN datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":2,"RPPayload":[{"RPEventType":1}]}
Transmitting SYN datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":3,"RPPayload":[{"RPEventType":1}]}
Transmitting SYN datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":4,"RPPayload":[{"RPEventType":1}]}
Transmitting SYN datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":5,"RPPayload":[{"RPEventType":1}]}
Received packet of size 103 from IP Address: 192.168.1.247 Port: 5050: {"RPEpoch":1560402127.518846,"RPVersion":"RDP_1.0","RPPayload":[{"RPEventType":2}],"RPSerial":"Probe1"}
Packet was an ACK packet from server.
Beginning temperature transmission.
Transmitting Temps datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":6,"RPPayload":[{"RPEventType":3,"RPChannel":1,"RPValue":99.90,"RPMetaType":3001}]}
Transmitting Temps datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":7,"RPPayload":[{"RPEventType":3,"RPChannel":1,"RPValue":99.90,"RPMetaType":3001}]}
Transmitting Temps datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":8,"RPPayload":[{"RPEventType":3,"RPChannel":1,"RPValue":99.90,"RPMetaType":3001}]}
Transmitting Temps datagram to IP: 192.168.1.247, Port: 5050, JSON: {"RPVersion":"RDP_1.0","RPSerial":"Probe1","RPEpoch":9,"RPPayload":[{"RPEventType":3,"RPChannel":1,"RPValue":99.90,"RPMetaType":3001}]}

Support / RDP DIY

« Last post by alja on June 13, 2019, 02:33:12 AM »

Hello Danny, I'm up for building my kit and ready to buy the parts but found this https://www.adafruit.com/product/2471 and wonder if I could use it instead of the Feather HUZZAH w/ ESP8266. Also Just to make sure... is there any other part I would need? I have the max 31855 and the thermo couple K.

Thanks for the help.

Support / Re: RDP probe unlinked/offline

« Last post by Danny Hall on June 12, 2019, 11:54:57 PM »

Hi Kasper

So, you've got it to the point where you send a SYN request, and Roastmaster replies back with an ACK, correct?

If so, then it's probably a simple formatting issue.

Can you reply back with a sample of the JSON that you create as text for a temp reading? I'll see if I can spot the problem.

Danny

Support / RDP probe unlinked/offline

« Last post by KasperV79 on June 12, 2019, 09:49:21 PM »

Hi guys. I’m new to Roastmaster so hope you can help me.

I just made a esp6288 module with thermcoupler. Modified the example code a bit to suit my setup.

When starting up the esp search forc Ack from the app and the Ack is received when the app is opened, hereafter the rdp starts to send temp data, event type 3.

But nothing is no data to see on app prope. And the prope has status “unlinked” I checked the serial “name” and everything seems correct.

Are there been any updates to the RDP protocol or can it be due to running on IOS 12?
Br
Kasper

Support / Re: ThermaQ WiFi Compatible?

« Last post by DonK on June 07, 2019, 02:33:29 AM »

Great! Thank you

Support / Re: ThermaQ WiFi Compatible?

« Last post by Danny Hall on June 06, 2019, 11:13:01 PM »

Just the ThermaQ Blue, at the moment.

Quality wise, they should be exactly the same. Roastmaster will show you all the temperatures concurrently (based on the defined curves in a roast), so the extra screen real estate of the WiFi model doesn't yield any real benefit in practice. But that model does add complexity by necessitating a wireless network. The ThermaQ Blue model, of course, is a direct Bluetooth connection - it's easier and doesn't involve any other electronics, so I haven't given much thought to adding support for the WiFi model.

Support / ThermaQ WiFi Compatible?

« Last post by DonK on June 06, 2019, 02:33:30 PM »

Is Roastmaster compatible with ThermaQ WiFi or only ThermaQ Blue?

Is one better than the other?

Support / Re: Govee Bluetooth Thermometer

« Last post by Danny Hall on March 11, 2019, 02:12:28 PM »

Hi DonK

Sorry - no. The only supports hardware is listed here... https://rainfroginc.com/documentation-library/data-logging

The ThermaQ Blue is a great choice for K type thermocouples. It's easy to use and built like a tank.

Support / Govee Bluetooth Thermometer

« Last post by DonK on March 11, 2019, 02:31:57 AM »

I purchased a Govee Bluetooth thermometer. Is this compatible with the Roastmaster App?

Support / Re: Setting up Roastmaster app on Ipad

« Last post by Danny Hall on February 21, 2019, 03:12:13 PM »

"Trouble setting up" as in the ThermaQ probes won't link?

If so, Bluetooth LE peripherals will only accept incoming connections from one “central” device at a time. How the device defines a “connection” is up to the hardware/software of that device, i.e. how long before that connection times out. So, if you downloaded the ThermaQ app (even on another device or platform), and then tried to connect with Roastmaster, the ThermaQ app is probably holding onto the Bluetooth connection, even if the app is in the background.

Try terminating the ThermaQ app wherever it is in use - Android or iOS. Also, verify you've chosen a port in Roastamster's Probe Details screen.

Let me know how it goes.

Pages: 1 ... 6 7 [8] 9 10