FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
02-21-2023 02:33 PM - edited 02-21-2023 02:35 PM
Hi,
I experience following strange situation.
I developed a node-red application that uses the DL subscriptions nodes and REST/API to monitor parameters of the servo drives. The source of the information for this flow is the DriveConnect App V1.18 which publishes data on DL. I monitor e.g. 7 drives and collect about 10 parameters from each with sampling based on seconds/minutes not ms.
I noticed such strange behavior with the ctrlX core (also on newest firmware V1.18.4).
Short version of the story:
7 The drive monitoring can be restarted.
8 I recreated same setup on other ctrlX unit and the situation is the same – led is yellow in the morning.
My suspicions:
I attach sample log to this post and below image as summary of log entries
3 I noticed, if you have debug nodes in node-red flow they also generate a lot of logs information to the central log mechanism of the ctrlX - in this case it can also influence on the ctrlX log or disk overflow.
4 The DriveConnect App is developed in a way that is automatically creating DL nodes under /devices/drives for drives discovered in the same network subnet as ctrlX unit - I would assume that DriveConnect App is using the UPnP mechanism for the discovery of the drives. Do you think that maybe here can be a source of huge number of messages from the UPnP protocol?
TLDR version:
3 I have no other choice like to unplug the device from the power and plug again.
4 Logs in the ctrlX are having a few hours of missing entries
And here comes another tricky part:
I recreated the same config on the other ctrlX unit I made exactly the same install of the environment and versions: ctrlX firmware, Node-red and drive connect.
And…. the second ctrlX unit behaves exactly the same. It is blinking yellow in the morning
I made another test and restarted both units same time before going home yesterday. And today in the morning they are blinking yellow again and are not reacting until I power them down and up.
I made also one interesting observation: I saved last heart beat of both units from last night. In the node-red there is a flow which collects actual CPU utilization and writes it to the database with actual timestamp. This is done every 5 seconds.
Please see the records form last night:
The units stopped the activity same time around 01:25 AM – difference is 5 seconds between them.
Some may say:
“Ok, there was some power failure in the building during the night (but it wasn’t cause I have a third unit which is working and also some other computers/servers which did not report power down last night ) and maybe the ctrlX units were not powered up properly or some peak power et.c” - but I cannot believe it. As this behavior happens every day to me I would assume this is something wrong with the particular setup or in ctrlX firmware itself ( I am running the newest).
I will try today:
Will keep you posted.
Regards,
Kookoolinoo
PS. In general it is fun 😊
Solved! Go to Solution.
04-14-2023 02:35 PM
Hi Kookoolinoo,
any news here?
Regards
06-22-2023 12:09 PM
Hi,
So with release 1.20 all problems were gone. Not experiencing this sistuatnion anymore.
🙂