Components

cancel
Showing results for 
Search instead for 
Did you mean: 

Syslog Component

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.

authored by
Christian L, CLA
Systems Engineering Manager - Automotive and Transportation
NI - Austin, TX


  
0 Kudos
Message 11 of 26
(9,000 Views)

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:

syslog_Hostname.png

0 Kudos
Message 12 of 26
(8,765 Views)

Leif,

 

Thank you for the error report. Attached is an updated VIP, which should be posted to the LV Tools Network VIPM repository in a few days.

 

 

authored by
Christian L, CLA
Systems Engineering Manager - Automotive and Transportation
NI - Austin, TX


  
Message 13 of 26
(8,753 Views)

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:

syslog_caching_Hostname.png

It would be nice if you could release a new version with this improvement.

Kind regards

LeifS

 

 

Message 14 of 26
(7,084 Views)

Thank you LeifS,

 

I have added your suggestion and built a new package. This will be added to the LabVIEW Tools Network repository soon.

 

 

authored by
Christian L, CLA
Systems Engineering Manager - Automotive and Transportation
NI - Austin, TX


  
0 Kudos
Message 15 of 26
(7,057 Views)

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

0 Kudos
Message 16 of 26
(6,730 Views)

I added the ability to specify the Client Port on the Init VI and rebuilt the package. (attached)

 

It has been added to the VIPM repository. 

 

 

authored by
Christian L, CLA
Systems Engineering Manager - Automotive and Transportation
NI - Austin, TX


  
Message 17 of 26
(6,722 Views)

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.

SyslogInit_ClientPort.png

Best regards

Leif S

0 Kudos
Message 18 of 26
(6,530 Views)

Thank you for the suggestion. I've attached the updated VIP.

 

 

 

 

authored by
Christian L, CLA
Systems Engineering Manager - Automotive and Transportation
NI - Austin, TX


  
Message 19 of 26
(6,523 Views)

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.

0 Kudos
Message 20 of 26
(5,300 Views)