How do I file Bug Report? Labview FPGA

[noli]

I'm not sure if this is a software bug or what, but I'm trying to run the Analog Input example project for Labview FPGA , in "Find Examples >> Hardware Input and Output >> R Series >> Basic IO >> Analog Input - R Series".

The thing is, it works.. mostly..  I manage to send in a sine wave, and see it.  However, every now and then, when I set teh Waveform Graph X-axis to autoscale, and change the Update Mode, every time I put it into mode Scope Chart, it freezes my computer, and I have to physically power off my computer and power it back up (which i'm not happy about).  I'm using the default settings for the example, my card is in RSE mode, input signal at 25 Hz, 4V p-p

I doubt anyone can guess why this is happening, but is there any way to file a bug report?

Thanks,

Hardware:  Quad-core Xeon 2.33 Ghz, 8 GB RAM, PXI-7583R FPGA, PXI-1036 Chassis

Software:  Labview 8.6.1, LAbview FPGA 8.6., Vista 64-bit

[CoastalMaineBird]

http://sine.ni.com/apps/utf8/niae_asc.main

Click on the E-MAIL NI option, and fill out the choices.

On the next page describe your situation.

Someone will be back with you within 24 hours. 

[wolson]

I am writing a passwording schema for my laboratory and i need to compare strings for equality. The equal block is suppose to do this and return a boolean. However, when I give it identical strings from two different sources, it returns "False".

I then checked the canned example provided, "Equal - Various Uses.vi", and got exactly the same problem for strings.

I am using a Dell Precision T5400 64 bit computer with Windows XP x64 operating system.

My Labview version 8.6.1 is part of the Professional Development Suite.

Thank you,

Walt

Message Edited by wolson on 07-22-2009 12:02 PM

[Ben]

Is use that functinality regularly and noted no issues. make SURE your strings are the same (look for trailing spaces "o" vs "0" and the case). If you still have troulbe post an example for us to help you further.

Ben

[CoastalMaineBird]

1... Adding an unrelated question to a 3-month old post is not the best way to get your questions answered.

Start your own thread next time.

2... The example works fine for me.  The EQUALS function works just fine for strings.  Be aware of some things, though:

• Case matters.  If you want to ignore case, then uppercase both strings (or lowercase them) before comparing. 
• Length matters "X" is not the same as "X ". "123" is not the same as "1234".

[wolson]

So far the relies have not been helpful: I have done all those several times. Here is a link to some screen shots that demostrates what appears to be a bug:

http://www.eng.utoledo.edu/~wolson/string%20not%20equal.doc

Thank you,

Walt

[CoastalMaineBird]

That's not a screen shot, that's a WORD doc. I can't see it.

Can you post a real picture ?  (PNG, BMP, JPG)? 

[Ben]

Probe #28 in your first image appears to be coming from a concatenate string where you are appending CR, which is non-visable. Does the other wire's data end in a CR?

Ben

[wolson]

Ben,

I did that to checked to make sure that was not the problem! The other string does have a carriage return in the file from which is taken from. Originally, I did not have the CR in the string. I have been playing with this for a day and half trying to deterime why it is not functional. Now I am writing code to bypass this problem by requiring numeric passwords which does seem to be functional.

But thank you for taking the time to reply.

Walt

[Ben]

For troubleshooting purposes only create an indicator for both wires feeding the "equal". right-click both indicators and set the them for slash-code display. I still suspect there is a non-printable character in that string that is causing the "F".

Ben