Iot at Zroasting, remote monitoring is a solver problem or creating new problems? | Equipment Forum | Clorofile
Clorofile Equipment
Equipment
Forum Equipment

Iot at Zroasting, remote monitoring is a solver problem or creating new problems?

R
satu bulan yang lalu
has anyone implemented a Lot on the ZZCF002Znya setup? Not just local logging, but actually sending data to cloud real-time, can monitor from the location.

I'm exploring this so I can monitor the batch that runs from the office. simple exception: BT and ET sensors send to server, can alert if there are anomalies.

But I'm worried about latency. Time the data reached the dashboard cloud continues I had to feed back to the operator in the field, how many seconds delay? It could be critical at approaching first crack.
192 8 0
8 Replies
M
satu bulan yang lalu
the latency was a valid concern. I once tried a simple setup with an MQTT plus cloud broker. latency average 30,000-80m if connection is stable. It's okay to monitor, but make hard-time control like an adjustment gas is too slow.
E
satu bulan yang lalu
how much does a budget cost? just make a picture, because if it's worth buying a new machine it doesn't make sense.
D
satu bulan yang lalu
it depends on DIY or buy the solution. DIY with Raspberry Pi plus thermocouple sensors plus open source stack could be under 500,000. The allIt's huge.
U
satu bulan yang lalu
more important question: if there's an anomaly and you're away from the roastery, what are you gonna do? alert came in, you're a remote, operator in the field that has to be action. this remote monitoring end- to-end is only useful if there are trained onsite operators at all times.
D
satu bulan yang lalu
my most value slot setup is not for real-time control but for post-analysis. logging all parameters to cloud, could pull data anytime for a strange batch review, same correlate Zcupping result. That's the real value.
Y
satu bulan yang lalu
gw pernah coba pakai ESP32 DIY buat kirim data BT tiap 5 detik ke Firebase. jalan, tapi waktu koneksi internet putus sesaat tiba-tiba ada gap di log. kalau lagi approaching first crack dan ada gap data 30 detik itu lumayan bikin panik.
Z
satu bulan yang lalu
local logging backup is mandatory. don't count on cloud only. there's a gap in the log that makes post@-@ batch analysis inaccurate.
I
satu bulan yang lalu
at the rodeo where I work, a lot of them were used to communicate documentation more than anything. Every batch has an automatically-exported timestamp log. That's the most useful certification quality.

Write a Reply

Login first to reply.

© 2026 CLOROFILE, PT Clorofile Tangguh Perkasa. All rights reserved.

Report Thread

Sign in first if you want to report this thread to the moderator team.

Create New Post

Silakan login terlebih dahulu untuk membuat post.

Unsaved Writing

You have unsaved writing. Save it as a draft before closing?

Member Info

Loading member info...

Sign In to Clorofile Forum