{"searchBar":{"inputPlaceholder":"Busca por palabra clave o haz una pregunta","searchBtn":"Buscar","error":"Ingresa una palabra para buscar"}}
{}

Nuestras marcas

{"support":{"yesButton":"Sí","noButton":"No","feedback":{"title":"¿Qué podemos hacer para mejorar?"},"submitButton":"Enviar","successMessage":"Gracias por tus comentarios","title":"¿Te fue de ayuda?","feedbackPercentLabel":"de las personas encontraron esto útil","captcha":{"error":"Por favor, marca una casilla"}}}
Buscar Preguntas Frecuentes

Why Node-red embedded with Ecostruxure Augmented Operator Advisor stop few second after starting?

Symptom
After few second, you can see that Node-red stop working

How to diagnotic
When you start AOA, there is one MS-dos windows with a lot of information

In this exemple, you can see that the problem occur after flow starting and after more details about which flow create this error

How to solve the problem
This flow error avoid to start Node-red. 
So, we will see how to restart with the previous working flow

Go to …Schneider-electric \ Ecostruxure Augmented Operator Advisor \ Node-red \ node-red home

In this folder you can see the current flow and also the last backup
The propose is to reuse the backup (the last working flow) and delete or rename the current flow (the flow creating node-red crach)
  1. Change the name or remove the flow named flow_W7FRN05933L.json
  2. Change the name of the backup .flow_W7FRN05933L.json.backup to  flow_W7FRN05933L.json
  3. Restart node-red

¿No encuentras lo que estás buscando?

Comunícate con nuestro equipo de Atención al Cliente para recibir soporte técnico, asistencia para quejas y más.