Null structure pointer in feedback statement in timeline brings NX-3200 to its knees
I ended spending way too much time chasing this one around. I had a controller go bad. It started dropping offline constantly. When I replaced it, the code just crawled on the new controller. I swear it acted like the processor was running at just a couple ticks a second. Turned out not to be the hardware, I tried another one and got the same result; turned out not to be any of 3 different versions of firmware; turned out not to have anything to do with RMS version vs. firmware version. It turned out I have a feedback timeline referencing a "masterroom" variable which is null until the first time you've selected a specific room on the master panel. Fresh code upload to a new controller doesn't have that variable set, and the processor just chokes on it. It shows up in the logs as an error, but it's not clear from that just how much it drags the controller. In the end, I just iffed out those 5 feedback statements to not evaluate unless theres a value, and Shazaam! Code took off like a champ.