# How to visualize temperature map MLX90640

**URL:** <https://discourse.nodered.org/t/how-to-visualize-temperature-map-mlx90640/7856>\
**Category:** Dashboard\
**Created:** [12 February 2019 02:01 UTC](https://discourse.nodered.org/t/how-to-visualize-temperature-map-mlx90640/7856 "2019-02-12T02:01:05Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [28 February 2019 23:11 UTC](https://discourse.nodered.org/t/how-to-visualize-temperature-map-mlx90640/7856/12 "2019-02-28T23:11:56Z")

</div>

> [@Announce: node-red-contrib-ui-heatmap (beta release)](https://discourse.nodered.org/t/announce-node-red-contrib-ui-heatmap-beta-release/8125/21):
>
> my flow (using your heatmap) works, but I am not happy as on top of 1Hz update rate, there is about 5s lug most likely due to nodered reading output from command line. Without nodered the application produces output smoothly every 1s. Anyhow, I am looking for another way of reading data from MLX90640 to nodered to make it better (faster, more reliable, higher frame rate).

Hey @janek,  
I'm going to continue here, to keep the other discussion focussed on the UI-node.

Do I understand this correctly? Your ML9060 sensor is connected via I2C to the RPI pins of your Raspberry, and then you use a third-party application (which you trigger via the Exec-node) to read data from the RPI pins into your Node-RED flow.

I have no experience with the I2C yet, but have you already tried for example the node-red-contrib-i2c node. It might (??) be faster to read the I2C data directly from Node-RED? I'm pretty sure that other people on this forum might be able to help you with this ...

---

_[View the full topic](https://discourse.nodered.org/t/how-to-visualize-temperature-map-mlx90640/7856)._