Jump to content

i2dx

Members
  • Posts

    683
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by i2dx

  1. In my opinion 8.0.0 is not useable, due to the bugs -- the 8.0.1 patch is absolutely necessary.

    LV 8.0.0 is a good example for "hey, it compiles, let's start immediately shipping it" ;-)

    maybe the management / sales department should think about, that you can't put unlimited pressure on the programmers to accelerate the development. If you make a big change (like in LV 7.1 --> 8.0) you need time.

    (I am sorry, that's allways me, to bring the bad news ...)

    nevertheless, there are still bugs in LV 8.0.1, I found my first one today. It is one of these lousy, hard to reproduce ones (in the PDA Module), I will tell more, if I have a Demo ...

    I can understand, NI does not want to release a full installer on their FTP-Server. This will cause 4 or 5 times more traffic. But they could e.g. bring out full Release for BitTorrent?

    Do you get an Update-CD if you are in the SSP?

  2. theoretically this should be possible, but it will be lots of work, to realize this.

    with the "BlockDiagram" Property-node, you get a array of references to "all Objects", which you can use to build a list of all objects on the BD. then you have to check the connections of the objects among each other and find out which connections exist.

    Finding subVIs is easy: there is a "subVIs" Property.

  3. i have only LV 7.1 and LV 8.0 installed, so i can't beat you :-(

    but i have a nice background picture :-)

    post-885-1141504550.jpg?width=400

    For those with an historical interest: LabVIEW v2.2 on a Mac Classic.

    Still gets used.

    WHOW ... i never saw this in real life

    ok. i've heard about that ;-)

  4. Yes I believe this is for representation.

    As a side note, the enum ctl has to be idle (not running and not in the call chain) for the string property to work.

    PJM

    that' correct. i think 8 is for U8, please try it out.

    and Ben, the fame does not belong to me! i just remembered, that i asked this question in Q4/2005, too, here in the forum. it was answered by one of the "big old ones" in this forum. unfortunately I could not find the old thread any more and could not remember the name of my saviour, so I posted this example ...

  5. the PDA crashes, if you send a flattened cluster. it does not crash, if you send e.g. a flattened double ...

    the demo is about one mb, because it contains the compiled PDA-exe ...

    sending a flattened cluster with LV 7.1 works fine ...

    i don't know what happens with Win2003, because i have only a WinCE PDA and a Windows Mobile 5 PDA ...

    the attatchment contains the VIs and the Project file ...

    the "BAD CHAR" VIs reveal, that the PDA does NOT crash because of a "special" char ...

    Download File:post-885-1141323891.zip

  6. Moreover, does hardware triggering require specific I/O cards such as PCI-6534?

    hmm ... how to say this?

    if you want to programm a hardware trigger, you have to use a card, which supports hardware trigger. Most of the NI-DAQ-Cards support at least a rising edge start trigger, but only a few support e.g. a "reference trigger"

    therefore, yes, you have to use a specific card, but as mentioned above most of the NI-DAQ-Cards are those "specific" cards

  7. Hi folks,

    there is a big bug in the LV 8 PDA Module TCP/IP VIs:

    all seems to work fine, if you only send e.g. a double value or an integer, like in the PDA Demo. BUT, if you try to send e.g. a flattened cluster with TCP/IP to the PDA your PDA will throw an exception (WinCE) or "hang" (WindowsMobile 5). Only the PDA-Module is affected, the Windows "module" is working fine ...

    The bug has been sent to NI and is confirmed. (CAR is created ...).

    If you are interested in the "Bug-demo", please send me an email or PM, the file is about one MB

    sad but true

    <crylikeababy>

    cb

  8. i close the database everytime .how can i free the memory?

    another condition :the used memory change little when operateing ActiveX(Access) operate database .why?

    i have to admit, i am not a user of LabSQL, but as far as i know, it uses ADO / ActiveX. Somewhere in the palettes there has to be a function which does the following:

    post-885-1141241722.png?width=400

    the 2D Array of Variant is sored somewhere in the memory of your computer. LabVIEW gets the pointer to this region. If you send a select query without closing that pointer (=freeing the memory) the pointer holds an address of a new memory segment and the old segment is "lost", but the memory is still marked as "used" and is unavailiabe for other applications. with every new sql query, that does not free the memory after taking the data into your programm, the ammount of used memory is increasing

    maybe someone with deeper knowledge of LabSQL can help you out, finding the appropriate VI?

  9. hmm, i dont understand much about your problem, but I did some picture manipulation a while back, and maybe I have a hint.

    if you load a jpeg you can connect the "unflatten pixmap.vi" which has a 2D U32 Array output. This output is quasi a "bitmap" with the color values (RGB [24bit] mapped to an U32 integer). the uppler left pixel of your image is in the array on position 0,0, the lower right pixel is the lower right element of the 2D array.

    If you want to embed a watermark - as much as I understand - you have to slightly modify the colors in the selected area. you can choose the area in the picture by selecting the corresponding elements of the array.

    I have no idea how the algorithm for the color manipulation works. If you have one, I would be glad, if you can tell me a little bit more, I am still searching.

    After manipulation the colors you simply use the "flatten pixmal.vi" to write it back into the jpg-format ...

    best regards,

    CB

  10. [...] Perhaps there's a way to turn its echo off? :unsure:

    yea, just take a big hammer and bash it on the device, i am sure this will turn the echo off immediatey ;-)

    sorry, could not resist ;-)

    and just to talk something seriuos:

    i agree, it's very likely that the echo comes from the device. i have done a lot of coding for RS232 devices and i never stumbled uppon a "echo-function" in labview ...

  11. my guess is:

    if you start your VIs in the development environment, the SCC VIs use the LabVIEW SCC settings. If you start it as an exe, there is an instance of the LabVIEW Runtime engine started in the background, which has its own memory, thread, working directory, etc ...

    a workaround could be: calling the SCC-VIs dynamically and do NOT include them into the exe, but provide the path to to the LabVIEW directory ...

    I am not very experienced with SCC, so this "guess" could be complete crap, but I think, it's worth trying ...

  12. maybe you want to take a look at the "IBBLogger" which is free and availiabe for download on my homepage.

    It's only in german right now, but it would be no problem to translate it.

    Features:

    - log up to 8 channels @ 1Hz directly into an access database

    - it is working at 1kHz per Channel internaly, and averages the samples

    - graphical display

    - digital trigger

    - save your "measurement" configuration

    - export the logged data to a *.CSV-File

    it's working with "allmost any" NI DAQmx-Hardware, so all you need is at least a NI-USB-6008

    i am planing to bring out a new release in Q2/Q3 this year, where you can set the sample rate between 10 Hz and 1 Sample per Minute, set thresholds with digital output /stop measurement ...

    there exist lots of sensors, from cheap to expensive, for temperature, humidity and preassure. if they provide a 0-10V output it should be working fine with my datalogger ...

    best regards,

    CB

  13. Attached a quick example using "Scan From String" in the String Function Palette:

    Download File:post-3266-1140131641.vi

    Joe (orko)

    sometimes you get just crap over RS232, so i would put a case structure around the knob, connect the scan from string error out to the case selector and make it the no error case.

    If you dont connect the error out at scan from string nodes, you will get these nasty error-popoups, if the scan fails, which you maybe don't want to see, because it's "normal" that sometimes the scan from string fails ...

×
×
  • Create New...

Important Information

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