# NVL from CODESYS to Node-Red delay **URL:** \ **Category:** Node-RED\ **Created:** [April 1, 2026, 2:54pm UTC](https://www.wago.community/t/nvl-from-codesys-to-node-red-delay/2657 "2026-04-01T14:54:50Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![WagoDamRud](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagodamrud/32/258_2.png) [@WagoDamRud](https://www.wago.community/u/WagoDamRud)\ **Post date:** [April 3, 2026, 7:23am UTC](https://www.wago.community/t/nvl-from-codesys-to-node-red-delay/2657/2 "2026-04-03T07:23:09Z")
PFC200 and CC100 both have 1 processor, so tasks like runtime (high priority) or nodered (low priority) have to be call one by one. If you set runtime tasks with high priority and also low timing the system scheduler will prioritize runtime, so nodered can be even choked. **What can you do?** Use `htop` command with console: Download PuTTY ( [Download PuTTY - a free SSH and telnet client for Windows](https://putty.org/)) it is a SSH client, so we can connect do PLC console via SSH How to change `htop` configuration to see task names: > [@PFC200 - Putty command TOP always to 100%](https://www.wago.community/t/pfc200-putty-command-top-always-to-100/1865/2): > > I would recommand to use htop instead of top. Then in the settings (F2), in Display options check Tree View and Show custom thread Names. It will display processes and sub processes accordingly, and you can even see the Task name within your CODESYS program. and check if _Load average_ is near 1-2, if not, change codesys tasks time or change 751-9412 CC100 (2 threaded processor) or PFC300 (2 threads) ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/f/fdae6146c3eaf3f30d51c200eeebfe1cbbf5de60.png) Task priority advice: ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/7/772e3d81711b9228c05ab8d78ef09c1bbef29cf8.png) --- _[View the full topic](https://www.wago.community/t/nvl-from-codesys-to-node-red-delay/2657)._