larryllix Posted December 22, 2018 Posted December 22, 2018 This is an awesome. NodeLink reported a duplicate variable name on my ISY system! AFAICT this name has been duplicated for about a year or more. I don't know what trouble this may have caused me, my NodeLink, or other areas, but I would be sure it wold cause some grief down the road, if not already. Luckily it was an unused variable "int_102" so I may have been lucky. It would seem if io_guy implemented this feature, it was to eliminate some possible NodeLink snag. @io_guyWell done! Thanks for your hard work and smarts here!
gviliunas Posted December 24, 2018 Posted December 24, 2018 I also have had the experience of NodeLink identifying my ISY programming issues. In my case, I began entering an ISY program Conditions but never entered any Then/Else Actions. Later, I looked at the Nodelink log and noticed that NodeLink reported an ISY error when loading programs. With this hint, it was easy to find the problem. I would like to echo Larryllix sentiment: @io_guyWell done! Thanks for your hard work and smarts here!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.