# Node-red-mcu-plugin v1.0: Integrating Node-RED MCU Edition into the Node-RED editor
**URL:** https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693
**Category:** Share Your Projects
**Created:** [25 December 2022 19:56 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693 "2022-12-25T19:56:53Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@jmorris644](https://discourse.nodered.org/u/jmorris644)
#### Post date: [23 January 2023 22:15 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/21 "2023-01-23T22:15:29Z")
I have tried playing with this. I believe that I have everything installed correctly but when I try to do a build with the plugin I get a "make: \*\*\* Waiting for unfinished jobs...." on the console and nothing ever comes back.
---
### Author:  [@jmorris644](https://discourse.nodered.org/u/jmorris644)
#### Post date: [23 January 2023 22:18 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/22 "2023-01-23T22:18:03Z")
Oops, I am also getting some errors
````auto
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:58:25: error: unknown type name 'mcpwm_unit_t'
static bool pw_callback(mcpwm_unit_t mcpwm, mcpwm_capture_channel_id_t cap_sig, const cap_event_data_t *edata, void *arg);
^ ~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:58:45: error: unknown type name 'mcpwm_capture_channel_id_t'
static bool pw_callback(mcpwm_unit_t mcpwm, mcpwm_capture_channel_id_t cap_sig, const cap_event_data_t *edata, void *arg);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:58:87: error: unknown type name 'cap_event_data_t'
static bool pw_callback(mcpwm_unit_t mcpwm, mcpwm_capture_channel_id_t cap_sig, const cap_event_data_t *edata, void *arg);
^ ~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:62:50: error: unknown type name 'mcpwm_unit_t'
static uint8_t mcpwmFromChannel(uint8_t channel, mcpwm_unit_t *unit, mcpwm_io_signals_t *signal, mcpwm_capture_signal_t *select);
^ ~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:62:70: error: unknown type name 'mcpwm_io_signals_t'
static uint8_t mcpwmFromChannel(uint8_t channel, mcpwm_unit_t *unit, mcpwm_io_signals_t *signal, mcpwm_capture_signal_t *select);
^ ~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:62:98: error: unknown type name 'mcpwm_capture_signal_t'
static uint8_t mcpwmFromChannel(uint8_t channel, mcpwm_unit_t *unit, mcpwm_io_signals_t *signal, mcpwm_capture_signal_t *select);
^ ~~~~~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c: In function 'xs_pulsewidth_constructor':
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:83:5: error: unknown type name 'mcpwm_unit_t'
mcpwm_unit_t unit;
^ ~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:84:5: error: unknown type name 'mcpwm_io_signals_t'
mcpwm_io_signals_t signal;
^ ~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:85:5: error: unknown type name 'mcpwm_capture_signal_t'
mcpwm_capture_signal_t select;
^ ~~~~~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:154:5: error: unknown type name 'mcpwm_capture_config_t'
mcpwm_capture_config_t conf = {
^ ~~~~~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:155:9: error: field name not in record or union initializer
.cap_edge = MCPWM_BOTH_EDGE,
^
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:155:9: note: (near initialization for 'conf')
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:155:21: error: 'MCPWM_BOTH_EDGE' undeclared (first use in this function)
.cap_edge = MCPWM_BOTH_EDGE,
^ ~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:155:21: note: each undeclared identifier is reported only once for each function it appears in
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:156:9: error: field name not in record or union initializer
.cap_prescale = 1,
^
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:156:9: note: (near initialization for 'conf')
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:156:25: warning: excess elements in scalar initializer
.cap_prescale = 1,
^
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:156:25: note: (near initialization for 'conf')
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:157:9: error: field name not in record or union initializer
.capture_cb = pw_callback,
^
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:157:9: note: (near initialization for 'conf')
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:157:23: error: 'pw_callback' undeclared (first use in this function); did you mean 'xsCallback'?
.capture_cb = pw_callback,
^ ~~~~~~~~~~
xsCallback
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:157:23: warning: excess elements in scalar initializer
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:157:23: note: (near initialization for 'conf')
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:158:9: error: field name not in record or union initializer
.user_data = pw
^
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:158:9: note: (near initialization for 'conf')
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:158:22: warning: excess elements in scalar initializer
.user_data = pw
^~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:158:22: note: (near initialization for 'conf')
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:162:13: error: request for member 'cap_edge' in something not a structure or union
conf.cap_edge = MCPWM_NEG_EDGE;
^
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:162:25: error: 'MCPWM_NEG_EDGE' undeclared (first use in this function)
conf.cap_edge = MCPWM_NEG_EDGE;
^ ~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:165:13: error: request for member 'cap_edge' in something not a structure or union
conf.cap_edge = MCPWM_POS_EDGE;
^
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:165:25: error: 'MCPWM_POS_EDGE' undeclared (first use in this function)
conf.cap_edge = MCPWM_POS_EDGE;
^ ~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c: In function 'xs_pulsewidth_destructor':
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:176:5: error: unknown type name 'mcpwm_unit_t'
mcpwm_unit_t unit;
^ ~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:177:5: error: unknown type name 'mcpwm_io_signals_t'
mcpwm_io_signals_t signal;
^ ~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:178:5: error: unknown type name 'mcpwm_capture_signal_t'
mcpwm_capture_signal_t select;
^ ~~~~~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c: At top level:
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:230:25: error: unknown type name 'mcpwm_unit_t'
static bool pw_callback(mcpwm_unit_t mcpwm, mcpwm_capture_channel_id_t cap_sig, const cap_event_data_t *edata, void *arg)
^ ~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:230:45: error: unknown type name 'mcpwm_capture_channel_id_t'
static bool pw_callback(mcpwm_unit_t mcpwm, mcpwm_capture_channel_id_t cap_sig, const cap_event_data_t *edata, void *arg)
^ ~~~~~~~~~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:230:87: error: unknown type name 'cap_event_data_t'
static bool pw_callback(mcpwm_unit_t mcpwm, mcpwm_capture_channel_id_t cap_sig, const cap_event_data_t *edata, void *arg)
^ ~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:293:50: error: unknown type name 'mcpwm_unit_t'
static uint8_t mcpwmFromChannel(uint8_t channel, mcpwm_unit_t *unit, mcpwm_io_signals_t *signal, mcpwm_capture_signal_t *select)
^ ~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:293:70: error: unknown type name 'mcpwm_io_signals_t'
static uint8_t mcpwmFromChannel(uint8_t channel, mcpwm_unit_t *unit, mcpwm_io_signals_t *signal, mcpwm_capture_signal_t *select)
^ ~~~~~~~~~~~~~~~~~
/home/joe/Projects/moddable/modules/io/pulsewidth/esp32/_pulsewidth.c:293:98: error: unknown type name 'mcpwm_capture_signal_t'
static uint8_t mcpwmFromChannel(uint8_t channel, mcpwm_unit_t *unit, mcpwm_io_signals_t *signal, mcpwm_capture_signal_t *select)
^ ~~~~~~~~~~~~~~~~~~~~~
make: *** [/home/joe/Projects/moddable/build/tmp/esp32/saola_wroom/debug/mz5ve8vnodc/makefile:1999: /home/joe/Projects/moddable/build/tmp/esp32/saola_wroom/debug/mz5ve8vnodc/_pulsewidth.c.o] Error 1
make: *** Waiting for unfinished jobs....```
````
---
### Author:  [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [23 January 2023 22:43 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/23 "2023-01-23T22:43:28Z")
Hi @jmorris644 !
Could you share the flow you're trying to build?
I can offer to check what's happening there...
---
### Author:  [@jmorris644](https://discourse.nodered.org/u/jmorris644)
#### Post date: [24 January 2023 13:53 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/24 "2023-01-24T13:53:09Z")
Just testing with an inject and debug node. Nothing else.
---
### Author:  [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [24 January 2023 19:05 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/25 "2023-01-24T19:05:58Z")
Thank you for the report.
I can confirm that the build fails on both `saola` devices.
As it looks like this is not related to Node-RED (but rather a topic of the core SDK), I've created an [issue](https://github.com/Moddable-OpenSource/moddable/issues/1012) @ the Moddable repository.
---
### Author:  [@jmorris644](https://discourse.nodered.org/u/jmorris644)
#### Post date: [24 January 2023 19:45 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/26 "2023-01-24T19:45:51Z")
Thanks! I will try another device and report back.
---
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [30 January 2023 22:03 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/27 "2023-01-30T22:03:06Z")
Hi @ralphwetzel,
Would like to start again with this, since Peter and Andy have been so kind to support the wt32-eth01 board on my request. Started from scratch again, and everything installed well (I think/hope) except your plugin:
```auto
pi@raspberrypi:~/.node-red $ npm install @ralphwetzel/node-red-mcu-plugin
npm ERR! Cannot set properties of null (setting 'peer')
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2023-01-30T22_17_13_696Z-debug-0.log
```
It happens both via command line or via the Node-RED palette menu.
Thanks!!
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [30 January 2023 22:18 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/28 "2023-01-30T22:18:12Z")
> [@BartButenaers](#):
>
> node-red-mcu
Is it this one?
> **[@ralphwetzel/node-red-mcu-plugin](https://flows.nodered.org/node/@ralphwetzel/node-red-mcu-plugin)**
>
> Plugin to integrate Node-RED MCU Edition into the Node-RED Editor
---
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [30 January 2023 22:19 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/29 "2023-01-30T22:19:06Z")
Hi Julian,
Sorry just updated my question. Had posted the wrong command. Sorry for the confusion.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [30 January 2023 22:20 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/30 "2023-01-30T22:20:44Z")
> [@BartButenaers](#):
>
> Sorry for the confusion.
Too quick for my own good 😁
Just back in from taking my son out for a 21st birthday Thai meal so you caught me just right - or just wrong as the case may be!
---
### Author:  [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [31 January 2023 06:26 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/31 "2023-01-31T06:26:32Z")
> [@BartButenaers](#):
>
> `npm ERR! Cannot set properties of null (setting 'peer')`
Hi @BartButenaers!
Sorry; can't reproduce this on my systems.
Could you send me the log please (PM or post it here) so I can check what causing this?
---
### Author:  [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [31 January 2023 18:28 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/32 "2023-01-31T18:28:01Z")
> [@BartButenaers](#):
>
> to support the wt32-eth01 board on my request
Hi @BartButenaers !
To get the support for your `esp32/wt32_eth01` board, you currently need to install the latest `1.1.2-post` version of the plugin, directly from GitHub:
`npm install https://github.com/ralphwetzel/node-red-mcu-plugin`
I don't know if this makes any difference though concerning the error you hit...
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [31 January 2023 20:41 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/33 "2023-01-31T20:41:27Z")
> [@ralphwetzel](#):
>
> npm install [GitHub - ralphwetzel/node-red-mcu-plugin: Plugin to support the Node-RED implementation for microcontrollers](https://github.com/ralphwetzel/node-red-mcu-plugin)
`npm install ralphwetzel/node-red-mcu-plugin` should be enough to install from GitHub's `main` branch.
---
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [31 January 2023 20:56 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/34 "2023-01-31T20:56:58Z")
Hmm, none of those commands work for me. They all give the same error, whether I download it from Github or from Npm.
I assume it is not related to Raph's package, but to my npm version. Read about other users having the same issue (for other package). Some of them posted it was resolved by upgrading from 8.15.0 to 8.16.0. Tried that but it didn't help...
> [@ralphwetzel](#):
>
> To get the support for your `esp32/wt32_eth01` board, you currently need to install the latest `1.1.2-post` version of the plugin, directly from GitHub:
Thanks for the tip!!
---
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [3 February 2023 23:17 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/35 "2023-02-03T23:17:47Z")
@ralphwetzel,
Now that your sidebar is installed, I would like to program my wt32-eth01 device.
After I have plugged the it into my Raspberry (via a CH340 TTL-USB converter) I can see this:
But that value isn't accepted by your sidebar:
Do you have any tips where I can get the correct value for that input field?
---
### Author:  [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [4 February 2023 06:05 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/36 "2023-02-04T06:05:05Z")
> [@BartButenaers](#):
>
> But that value isn't accepted by your sidebar:
It is - well, at least it should! When you build the project, the plugin takes whatever you typed in and forwards this as port info...
The red frame is just meant to be a visual indication, that it cannot find the port given. To see the ports the plugin is aware of, place your cursor into this field and press the down arrow key.
This data yet is filtered; it might be that its filter needs to be corrected...
---
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [4 February 2023 07:01 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/37 "2023-02-04T07:01:45Z")
Ah yes, now I see:
When I select that it is selected:
Hopefully some time during the weekend to continue with this.
Thanks!!!
---
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [4 February 2023 07:26 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/38 "2023-02-04T07:26:52Z")
> [@ralphwetzel](#):
>
> If you're curious to test it, just plug in the MCU Santa brought you (or the other one, that is laying around next to you) & create the flow that most (if not all) of you are familiar with:
> 
> Despite it looks quite nullish, you'll easily experience a lot of the functionality mentioned above in action!
Not sure if I understood this correctly. Suppose you want to run some kind of simple test flow, just to see whether the whole setup is correctly installed. Can I use your two-node flow somehow for that?
---
### Author:  [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [4 February 2023 09:38 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/39 "2023-02-04T09:38:07Z")
Yes. Just inject a timestamp (best repetetively) & let the debug node do it's thing...
---
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [4 February 2023 16:55 UTC](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693/40 "2023-02-04T16:55:41Z")
@ralphwetzel,
Had 10 minutes time in between...
Time enough for a few remarks:
1. When I start my flow editor, the MCU sidebar is empty in the beginning (when the MCU sidebar is my default sidebar at startup):
2. When a start a build for my wt32-eth01 device, I get the error _ **"$IDF\_PATH is not defined"** _
3. Another question about the simple Inject-Debug flow. Could you explain a bit more detailed how this works? Does the Inject node (which is triggered periodically) run on the mcu? If so, then the button of the Inject node won't be triggering messages I assume or does it somehow?
So in fact I don't really understand how an injected message arrives on the mcu, or how the mcu can show messages in the debug bar via the debug node 🤯
[Previous page](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693.md?page=1)
[Next page](https://discourse.nodered.org/t/node-red-mcu-plugin-v1-0-integrating-node-red-mcu-edition-into-the-node-red-editor/72693.md?page=3)