Just wondering… 
Just wondering…
Single core CPU for one.
Its remote IO, not a controller for two.
The Node-RED dashboard not doing it for you? I have seem some amazing customer dashboards already…
The dashboard is usable but an incredible pain compared to Groov View. It would sure make building small stand-alone applications a lot quicker if the RIO had Groov View.
Potential can of worms here.
Node Red dashboard can be made to work but why give us that option of you have spent so many hours developing your own (Groov View)?
I feel Groov View would have made the RIO whole, from an Opto22 standpoint. I can understand from a sales point what your reasons are, the processor being a drawback is something that can be overcome.
A product like this has HUGE potential 
Thanks for the reply
Cheers
I for one am glad the RIO is low cost and light weight. It is nice to have a flexible IO device that can compete with much less expensive competitive devices. Node-Red already gives it an edge over those competitors. If people need PID controls and Groov View then they can easily add an Epic or AR-1.
For me, I want to keep the pricing on this as low as we can get it. We have needed this alternative for a long time.
Norm - FYI, RIO f/w V3+ now has PID loops (at no extra cost).
I came across this thread here and this info on the node-red repository:
NOTE: This project is based on Angular v1 - As that is now no longer maintained, this project should be considered to be on “life support”. Small patches will be applied on a best can do basis, but there will be no major feature upgrades, and underlying security breakage may occur.
In light of this info, what is the plan for replacing the dashboard?
Node-RED developers have said that a new UI is on their list, but there’s no firm date when that will happen, as far as I know.
They did compare a few UI packages on their blog, one of the alternatives to the standard dashboard might be what you’re looking for:
Those are interesting, but not currently compatible with RIO or EPIC.
2023-05-09T22:29:38.265Z Install : @flexdash/node-red-fd-corewidgets 0.4.64
2023-05-09T22:29:38.462Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict @flexdash/node-red-fd-corewidgets@0.4.64
2023-05-09T22:29:56.681Z [err] npm ERR! code ENOTSUP
2023-05-09T22:29:56.724Z [err] npm
2023-05-09T22:29:56.724Z [err] ERR! notsup Unsupported engine for @flexdash/node-red-flexdash@0.4.154: wanted: {"node":">=16.0.0"} (current: {"node":"12.22.1","npm":"6.14.12"})
2023-05-09T22:29:56.724Z [err] npm ERR!
2023-05-09T22:29:56.725Z [err] notsup Not compatible with your version of node/npm: @flexdash/node-red-flexdash@0.4.154
2023-05-09T22:29:56.725Z [err] npm ERR! notsup Not compatible with your version of node/npm: @flexdash/node-red-flexdash@0.4.154
2023-05-09T22:29:56.726Z [err] npm ERR! notsup
2023-05-09T22:29:56.726Z [err] Required: {"node":">=16.0.0"}
2023-05-09T22:29:56.726Z [err] npm
2023-05-09T22:29:56.726Z [err]
2023-05-09T22:29:56.726Z [err] ERR!
2023-05-09T22:29:56.727Z [err] notsup Actual: {"npm":"6.14.12","node":"12.22.1"}
2023-05-09T22:29:56.987Z [err]
2023-05-09T22:29:56.987Z [err] npm ERR! A complete log of this run can be found in:
2023-05-09T22:29:56.987Z [err] npm ERR! /home/dev/.npm/_logs/2023-05-09T22_29_56_732Z-debug.log
2023-05-09T22:29:56.995Z rc=1
Our devs are aware of this node version issue (there are a few other nodes that need the higher version) and are working on an update, we will have more to say about this soon.
Thanks for testing it on groov and letting us know how it went. (I plan to test out flexdash for a personal project in the next few weeks, it looks pretty interesting).