Jump to content

Gepponline

Members
  • Posts

    64
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Gepponline

  1. Hi,

     I'm trying to insert some NULL values in a datetime field.

    In the example, the DATA_INSERIMENTO field has a non empty value and it works correctly but DATA_INTERVENTO doesn't accept NULL.
    If I use an empty string instead of null, the VI run without any errors but it fill the database field with a 1900-01-01 and it's not what I want.


    nullstring1.png

     

    If I use the DB Tools NULL VI it gives me another type of error, maybe 'cause I'm connecting a variant to a cluster of string.
    If i use a Variant to Data VI for the NULL value it returns an empty string so not the result I need.

     

    nullstring2.png

    If use the string you see in the label at the bottom of my diagram in SQL Server manager, it works correctly.
    How can I obtain the same result with labview?

  2. Is there a way to display a DXF or a DWG file?
    Not an interactive control, I need to display them as they are Images.
    Is to avoid to export bitmap form dxf files only to show the user a reference layout...

    something like a preview...

     

    Is there a way to do it?

     

     

  3. Hi!

      i need to check an integer string, but if i use Scan from string with a %d as format string, and I have a string that contains 12A13 for example, it don't return me an error 'cause it recognize a 12 before A.

    SHould i use a different format string to consider the whole string?

  4. Hi!

       I need to authenticate users on my program relying on LDAP.

    At the moment i use a .NET contructor that work but it takes 30 seconds to authenticate the user.

    Is there any other way to do this?

    Activex? dll? 

    Thank you!

     

    Attached you can find the snippet of the way i do now.

     

    post-1899-0-42837400-1422614971_thumb.pn

  5. Hi!,

       I have a problem with a spreadsheet file.

    I need to import a tabulated file that contain some text fileds with a EOL inside.
    I've tried exporting that file in csv with a text delimiter such as " but the problem is how to import the file makin labview recognize the text field and so ignore the EOL in the text field.

    At the moment with normal spreadsheet VI's i get a new line when i have a text field with an EOL character.

    Is there any solution for my problem?

     

     

    EXAMPLE:

    88 250 P A2 1971 1-lug-1990 Tenax D 250 P DP "Testa con passaggio acqua
    Monta Verin D. 60 corsa lunga" 110 x 110 345 Tenax 1
     
    the above text return me two line 'cause "Testa con passaggio acqua EOL Monta Verin D. 60 corsa lunga" is a single text field and the EOL must be ignored.
     

    thank you!

     

    Geppo!

  6. Hi,

      I have a problem with my signal generation Vi.

    I use a Ni PCI-6221 board to generate arbitrary waveform.

     

    In my application i need to change waveform and frequency on the run and the next waveform MUST start after the last point of the first one.

    I attach an example of what i need to do. Don't care about the shape of the waveform bout only the frequency.

    As you can see in the exampel when i change waveform the new waveform immediately start truncating the waveform in execution.

    I need the new waveform to start at the end of the first one.

     

    NOTE: I MUST use continuee samples or regeneration 'cause i could not be fast enough to write continuously the waveform when i generate 100hz waveform or similar.

     

    could anyone help me?

     

     

    Prova2.zip

  7. Hi Jared, By Changing the Constant(0x07),. any Integer file can be accessed. But, before changing the constant, create that particular file in the PLC and configure it as integer. also configure the number of registers in that file as required. Accessing Bool File directly is a bit tough. Instaed of accessing a Bool File., You can keep some registers in the N7 and access it. In plc side, keep a logic to read from the integer file register and update the bool file. Use one of the these values for this field. Do not use any othervalues; doing so may result in unpredictable results.

    Hi!

    I'm communicating with a Micrologix 1400 PLC.

    I Can read the N7 integer value, but the plc software use even "B" and "I"files for boolean variables. I Can't modify the PLC software.

    Is there a way to read these files with your VI's?How?

  8. Hi!

    i'm going to develop an application to read a couple of analog input from an object that turn continuously.

    Needing a wireless communication, i decided to use Xbee modules.

    Now I have my modules but i don't know how to start communicating with them using labview.

    Any Idea about it? Is there any labview tool to communicate with xbee modules?

    Is bettere to use API mode or AT command mode?

    thank you so much.

  9. Anyone actually using this? (apart from me laugh.gif )

    I've another release almost ready so if you want any additional features / changes.... now is the time to mention it (no promises tongue.gif ).

    I'm not using it at the moment but i'm going to use it early to substitute the old SQlite wrapper i used in some applications

  10. Here it is!

    http://gepponline.altervista.org/_altervista_ht/SQLite.zip

    I'm not able to attach file here in the forum, maybe a Proxy problem of my net. If anybody can download it from the link and upload it in the forum it's better 'cause that is my old domain and it can give some problem for file sharing.

    I deleted recursion istances and all seems to work.

    i use it with Ubuntu and Labview dor linux 8.5.

    ...ma ciao!

    Geppo!

  11. IC.

    Well that explains the recursion issue you are seeing. Prior to LV9.0 recursion was only supported by opening a ref and using a call vi node. But its nice to know with a bit of hacking it can work on older LV versions......even Linux biggrin.gif. I presume (since you haven't mentioned any so far) that there are no issues in your windows LV 9?

    I confirm, no issues with LV9. And now that i have deleted recursive VI, no issues even with LV 8.5. Maybe i'll convert the recursive VIs as you said with call vi nodes to have all the tool working, but for the moment i only need to make some simple query and i don't need nothing more ;)

  12. I believe TARGET_BITNESS was first introduced in LV 8.6. Do you have any difficulties in LV 9?

    No I don't

    ...even if i cannot find any TARGET_BITNESS variable in the project...where is it placed?

    Oh, QUery3.vi, rename column and dlete column report the same recursion problem.

  13. I'm surprised by this. What said it? Those two function are actually a trick. They just use SQL to copy the data to another table, delete then recreate the original and copy all the data back. SQLite doesn't have delete or rename columns function, but it is needed. To get this error, one of the other VIs would have to include it. Do you have an example use that shows this error?

    I Didn't make an example i only created a new blank vi and place a Table.vi inside.

    Could it be a converting from LV9 to LV 8.5 problem? To make this i had to convert to 8.6 first and then with LV 8.6 to 8.5...maybe something get lost inthis step.

    OS and bitness are only available from within a Project. But Target Type is available all the time. Did you open them from within a project? Or just stand-alone VIs? Try adding them to a project.

    The problem is that linux, like windows, also has x32 and x64. We need the bitness to choose the appropriately compiled DLL.

    The choice of whether to use OS or Target Type was arbitrary. They both support the same things (more or less). I leaned towards OS because that is the one that NI use in their example.

    I created a New project but the OS variable was not "Unix" but "Linux" and the bitness variable did not exists.

    Now i'm trying reconverting Vis from LV9 to LV8.5 and using a project, i'll let you know if i find something new

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.