25 replies to this topic

[QRAsk]

I can write a program to generate a QR code from a program LabVIEW or not.

[Jordan Kuehn]

I think this is the closest thing I've seen. https://decibel.ni.c.../docs/DOC-14718

The author notes that the details required for implementation of QR code generation (and licensing I assume) are expensive.

[QRAsk]

Thank you.

[Phillip Brooks]

If you have an active internet connection, you can use this VI.

It uses Datasocket and the Google Chart API.

 Create QR Code.vi   14.46K   264 downloads
(LV 8.6)

[QRAsk]

Thank you.
I want to generate on offline.
What tools I have to use?

[Phillip Brooks]

Thank you.
I want to generate on offline.
What tools I have to use?

I don't know how you would do this offline. As I stated, you must have internet access because it uses the Google Charts API.

[QRAsk]

I don't know how you would do this offline. As I stated, you must have internet access because it uses the Google Charts API.

Thank you.

[Wouter]

There are several .dll availables for .NET. You can use them also in LabVIEW. http://www.google.nl...e generator dll. Further when you google on "ISO/IEC 18004:2006" you may or may not find a .PDF file containing the ISO/IEC specification of QR code, enabling you to fully implement QR code in LabVIEW. However note that the .PDF is actually not the latest edition "ISO/IEC 18004:2006" but the previous "ISO/IEC 18004:2000".

[Mr Mike]

I think this is the closest thing I've seen. https://decibel.ni.c.../docs/DOC-14718

The author notes that the details required for implementation of QR code generation (and licensing I assume) are expensive.

It's a combination of the price and time. I (the author) work on the LabVIEW Language team and developing libraries for users is not one of my job responsibilities. Most of the work on the bar codes is done during my free time or on our free form test days.

I recently added (but have not yet cleaned up / tested / published) support for PDF417, which may be an acceptable alternative to QR codes. I noticed recently that tcpdf supports QR codes and it's distributed under the LGPL. I may be able to port it, but it's not very well documented (and neither is the source of their QR code support. It seems like a very complex bar code from what I've seen, so I'm not optimistic about being able to implement it quickly. (I'd also need to double check with NI's legal department regarding porting from LGPL code)

[Mr Mike]

I've done most of the implementation for supporting QR codes, but I'm having a lot of trouble generating the error correction codes. There are four error correction levels (L, M, Q, and H). 100% of my tested QR codes have the correct error correction for Q and H. About 50% of M codes have the correct error correction codes, and none of the L codes have the correct error correction data. I can't figure out what's wrong with it. Does anyone have experience with generating QR codes?

I've looked at some other implementations (MIT license only -- I'd like to stay away from GPL code just in case), but their implementation is very confusing to me.

[QRAsk]

I'm studying. About the QR Code.

[Darin]

I've done most of the implementation for supporting QR codes, but I'm having a lot of trouble generating the error correction codes. There are four error correction levels (L, M, Q, and H). 100% of my tested QR codes have the correct error correction for Q and H. About 50% of M codes have the correct error correction codes, and none of the L codes have the correct error correction data. I can't figure out what's wrong with it. Does anyone have experience with generating QR codes?

[Mr Mike]

Yes, but did you make that with LabVIEW?

[ShaunR]

Yes, but did you make that with LabVIEW?

According to the text in the code....yes

[Darin]

Yes, but did you make that with LabVIEW?

Shaun is correct, 100% pure G. Not up to spec, no Kanji, no mixed mode messages, just a simple encoder I have used many times to label objects around the lab. Chokes in a few corner cases when I approach the data limit of a particular version, but all levels of EC work.

(I am not trying just to be a tease, but there is a bit of cleanup left to do since I kind of stopped once it was working. I can probably help with the problems in your code though).

Edited by Darin, 12 April 2012 - 07:55 PM.

[Phillip Brooks]

http://zxing.org/w/d...=6585&full=true

[Mr Mike]

According to the text in the code....yes

Shaun is correct, 100% pure G. Not up to spec, no Kanji, no mixed mode messages, just a simple encoder I have used many times to label objects around the lab. Chokes in a few corner cases when I approach the data limit of a particular version, but all levels of EC work.

(I am not trying just to be a tease, but there is a bit of cleanup left to do since I kind of stopped once it was working. I can probably help with the problems in your code though).

Haha, I just realized that. I read it so quickly before that I completely skipped the first half of the sentence! I'd use the oops smiley if I didn't think it was obnoxious

Darin, check your messages

[Wouter]

Shaun is correct, 100% pure G. Not up to spec, no Kanji, no mixed mode messages, just a simple encoder I have used many times to label objects around the lab. Chokes in a few corner cases when I approach the data limit of a particular version, but all levels of EC work.

(I am not trying just to be a tease, but there is a bit of cleanup left to do since I kind of stopped once it was working. I can probably help with the problems in your code though).

Would you maybe want to publish the code on a public source? GIT? Google code? And maybe even a better start question do you even want to share it? (oh and I don't really care if its messy )

Edited by Wouter, 16 April 2012 - 12:29 AM.

[Darin]

You asked for it. A little cleaning went a long way, just did not have a chance to document things very well (have to jog my memory for that). This was built with piecemeal documentation, mostly to the original iso-spec, and with a lot of reverse engineering. Seems to work as well as my iPhone reader, hard to tell which one is the problem in a few corner cases.

Not sure if I want to be on the hook for documentation/support if I posted to the CR, maybe a NI community page is in order, or Mr Mike will sort his out and add to the page. By all means let me know of any bugs, certainly a lot of version/EC combinations have not been tried.

Attached Files

•  QR Generator.llb   428.91K   176 downloads

[ShaunR]

Not sure if I want to be on the hook for documentation/support if I posted to the CR, maybe a NI community page is in order, or Mr Mike will sort his out and add to the page. By all means let me know of any bugs, certainly a lot of version/EC combinations have not been tried.

Forums are a much better format for in-progress development IMHO. You are also far more likely to get contributions to bring it to fruition. You can decide on a license that suits you and is much clearer to people than the NI site.

Additionally, once mature and if you decide to, it can go as part of the Lava tools network, a package under the jki thingy, or just remain in the CR with no major headaches. Documentation isn't that rigorous (readme and version history if I recall). Perhaps start it off in the uncertified.

Nice work.

Edited by ShaunR, 16 April 2012 - 03:07 AM.