08-22-2013 09:48 AM
Clendon,
You are absolutely correct. It looks like the error case structure was added in a recent version of the component in an effort of adding error handling to all VIs. I will remove it and repost the VI package.
04-23-2014 03:44 PM
Hi,
I think I've found a bug in the SubVI "syslog_Hostname.vi"
The boolean constant value makes the VI to return the first byte of the IP address instead of the hostname.
Change the value to FALSE as below instead gives the hostname in return:
04-25-2014 02:44 PM
05-15-2016 12:43 PM
Hi again,
We have noticed that the send function (Syslog Device Send.vi) executes quite slow in some environments. After some performance analyzing we found that the blame goes to syslog_Hostname.vi , which executes the StringToIP and IPToString for each time a Syslog message is sent.
This is easily fixed by caching the hostname in the VI like this:
It would be nice if you could release a new version with this improvement.
Kind regards
LeifS
05-18-2016 10:56 AM
08-25-2016 04:44 AM
Hi,
I also have run into this issue with the local IP port conflict, and although I certainly can fix it myself, I'd prefer NI to fix it and distribute a new version of the package.
Can you please do that?
Best regards
Leif Suonvieri
Midroc Automation, Sweden
08-25-2016 02:17 PM - edited 08-25-2016 02:33 PM
09-20-2016 06:51 AM
Hi Christian,
Your latest fix was good, but only works if I have the Collector running on the same computer.
Could you please change so that I can select ClientPort agains a remote Syslog server?
Below I'm proposing a solution for this.
Best regards
Leif S
09-20-2016 10:14 AM
03-13-2018 09:27 AM
Hi Christian,
RFC 3164 specifies that the total length of the syslog message including PRI and HEADER must not exceed 1024 bytes, but I can't see any such limit imposed in the component (so arbitrarily long content strings will be sent without truncation).
Should the message 'syslog_Device Function Engine.vi' truncate the message length to 1024 bytes?
Richard.