base64 encoding

[sokol]

Hi everybody!

I wonder if anybody have done anything to automate receiving e-mail with base64 encoded attachments?

Sending and receiving e-mail is quite straight forward but I am stumbling over base64 encoding/decoding.

Any suggestions or examples would really help.

Thanks a lot.

[unclebump]

Maybe you could use this program with system exec.

http://www.fourmilab.ch/webtools/base64/

[unclebump]

Try this thread.

http://forums.ni.com/ni/board/message?board.id=170&message.id=135986&requireLogin=False

[sokol]

Right on the money!

Both links are extremely useful - highly recommended!

OpenG.org is also an interesting motion http://openg.org/index.php.

I think they've got a new member...

Thanks a lot!

[2014spring]

I'm looking for a vi that does base64 encoding and decoding. I read all the related threads in the forum and it seems that all the links mentioned are not working any more. Does anyone still have the vi?

Thank you very much!

[DavidBoyd]

Look in vi.lib\httpClient.  There are a pair of VIs already written for you, they're members of the HTTP client library.

Dave

[2014spring]

Hi Dave,

Thank you so much for pointing me to the right direction! I found the VIs in the library but when I try to open the block diagram, it pops up an Authentication window saying: "LabVIEWHTTPClient.lvlib:Base64Encode.vi is password-protected. Enter the password to acces the block diagram". I have no idea about which password it's asking for. Do you?

Thanks very much!

[Sam_Sharp]

It is a National Instruments VI so they have protected the VI from being opened as it is their intellectual property.

Why do you need to open the VI? Why can't you just use it as it is?

[DavidBoyd]

As Sam_Sharp says, it's part of the NI standard library of VIs, and in this case, they've chosen to lock the block diagram.  Not all NI-developed VIs in vi.lib are locked; in fact, most are not.

If you just need VIs to reliably encode/decode base64 for your RedRat XML file parsing/building, you've got what you need.  On the other hand, if you wanted to LEARN how a developer might code these algorithms in LabVIEW, you're out of luck here.

The general explanation for why NI chooses to lock a BD on a particular VI fall along one or more of the following:

1) uses an undocumented/potentially unsafe internal LabVIEW feature which must not be exposed;

2) has dependencies on other third-party interfaces which aren't licensed for other use;

3) is subject to change in the future which might break user code if the internal bits were directly accessed;

4) really, really ugly implementation no one should ever use as a reference design (OK, I made that one up)

Good luck with your remote control project.  I was reading up on the RedRat (from your other post, which is where I saw the base64 stuff in their XML), looks like a fun tool to write some LabVIEW around.

Dave

[2014spring]

Thank you Sam_Sharp for looking at my question and replying it! I guess you are right, I can just use it. 🙂 Many thanks!