FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
08-04-2024 06:41 PM
I'm working with a "Virtual Control", I'm waiting for the object B0.R911410037 COREX-C-X3-11 (I think it will arrive in 3-4 weeks).
On "Virtual Control" I installed the node 'ui_table' on node-red using the "palette" I didn't receive any errors or warnings.
I manage the node in the develop environment and the compilation is OK. When I view the dashboard the table doesn't appear.
The json source is ok because this table is working on node-red installed on windows and also on debian.
I turned off and restarted the "Virtual Control"... even if it shouldn't be necessary.
Maybe when I have the physical object I will have other feedback, for now I just can't get directing.
I recently tried the ctlrX product and maybe my approach is wrong... maybe it's an architecture thing. I'm in try catch mode 😐 because I don't know where to look for a possible log... where is setting.js...
and other...to say if I wanted to ask "npm -v && node -v" from which shell I must use..
so when I install node-red on a computer for me it's different...
....that's why I think... maybe my approach is wrong.
.......so the questions
-About the node 'ui_etable' doesn't work any tip ?
- How can a user like me orient himself on ctrlX-NodeRed product?
thanks for support
gigiA
Solved! Go to Solution.
08-06-2024 10:52 AM
Hi @gigiA
I just installed the ui_table palette in the NodeRed App in my ctrlX CORE virtual. I imported the sample "Richer table" which comes with the palette. It works fine for me and I can see the table in the dasboard. Did you maybe miss to click on inject after deploying?
The NodeRed Json Files you can find in the ActiveConfiguration on your ctrlX CORE (virtual). To access this file-location click on the folder symbol in the header of the web-ui of your ctrlX CORE:
To see log messages of the Node-RED App go tho Diagnostic->Logbook and enable the "Developer View". Then you switch to "System and trace" and filter for the Source unit: "snap.ctrlx-node-red.node-red.service".
Best regards,
Nick
08-06-2024 01:52 PM
Thanks so much. solution Ok!
for ui_table the my fisrt error was on manager property of columns..... I must review my code.
for debug very fine, Now I can read what I write inside a function with console.log(msg.payload)
.....🤗obviously once the delivery is finished it is better to remove these logs as well as the debug ones 😊
..thank you again. regards gigiA
08-06-2024 03:20 PM
@gigiA ,
As an additional tip, you can log to the Node-RED debug pane using node.warn("MESSAGE") in your function nodes.