Jump to content

jgcode

LabVIEW Tools Network
  • Posts

    2,397
  • Joined

  • Last visited

  • Days Won

    66

Posts posted by jgcode

  1. Nope, and nope. In general I don't think you need to recompile prior to a build as I would assume the build process includes a recompile. I could be wrong though... it's just what I've always assumed.

    Well thats what I thought/assumed too but I just had the time of my life finding this out!

    T? But I was using Scan Engine (SE) on LabVIEW Real Time (RT) and until I compiled the Variable nodes returned either an error or the wrong value, source ran fine tho!

    Don't know if its an issue with SE/RT, or if I should be forcing a recompile before each build. But it raised alot of questions

    I ran into this a ton back at TI wrt wanting to not have the system need to compile anything at load time....that's just sloppy.

    But then I had to balance against checking in a file a ridiculous number of times for re-compile.

    In the end I just gave into having a ton of useless check in's

    Yes, I wanted to know if I could avoid this.

    I think this is something worth someone @ NI addressing our stance on (which I really don't know but figure it'll be "just check in a bunch"

    I'll try to pass this onto some other folk, but no guarantees.

    Keep bitching about it though and maybe some proposed solutions

    Cheers, much appreciated :cool:

  2. What really annoys me is when LV grabs onto files which were opened by completely separate applications. Examples I remember are MP3 or AVI files which I opened with Media Player Classic (by double clicking them in an Explorer window) and then for some reason LV opened one or more handles to them, thus preventing their deletion (I saw it's LV by using a third party program and by the fact that I can delete them immediately after I close LV).

    Glad someone else has seen this, I thought I was going insane when this was happening! :wacko:

  3. I ran into a nasty issue where a build for Real_Time was returning incorrect data!

    The solution was to recompile the top level VI and save all callers (have to save as its RT).

    The problem arose as most VIs were read-only as they were in SCM.

    What is the standard protocol for this from SCC point-of-view?

    Should I check out the VIs, compile/build/archive-build, then check them back in and tag them as "recompiled" or similar?

    Or should I check out the VIs, compile/build/archive-build, then get last revision to overwrite the new local copies?

    What do you guys do?

    Cheers

    JG

  4. Between this error (1502) and error 6 (file I/O=Path too long), building an executable is getting really difficult.

    This really need to get fixed.

    I have complained before about Error 6 but am still of the opinion that it is better than having files outside of the build.

    I would be nice if NI could do the build in a temp directory (as close to the root as possible) to avoid this, then copy it back to the dist location - all transparently (I currently have to use a script to do this manually).

    I have also had the annoying problem of Vague Errors in builds.

    The fastest way I have found to identify the issue is to

    • Build after integration - so I can keep track of what the problem may be down to
    • Disabling/removing modules of code and rebuilding until it works - when it works, the last thing I removed may be the culprit and I can build a test VI to confirm.

    Does anyone has any other/better ways?

    In the past, for me, these issues have been caused by e.g.

    • Dot Net calls, the client PC did not have the framework installed, but all I got was a Vague Error
    • Dirty class (once), I have no idea why but it would work in source but not in the build, I had to delete it and start again

    The first one can be avoided by prechecking registry etc... but a descriptive message would be appreciated

    I do not know why LabVIEW cannot return better diagnostic information when this happens?

  5. Is it specific to items in classes or is it any time you're building LLBs, regardless of content?

    For me, its to do with classes because:

    • I build classes into LLBs for distribution of reusable code
    • But I use VIPM for almost all other LLB distributions

    So I can't say exclusively classes, but my use cases predominately includes them.

    I started noticing it happening with controls, in particular DVRs, which is what I played around with a lot since LabVIEW 2009 came out. But I have seen controls and VIs (as per my example) excluded too.

  6. Has anyone else had the problem of?:

    When building an llb (from a class in this case), (random) build items move outside of the llb even though their destination should be inherited from the caller.

    In the video here: http://www.screencast.com/t/NmQ1MWVm, you will see I have to manually set the destination for these "sub-items" to fix the problem.

    I get this problem quite a bit.

    This is annoying and error prone.

    Cheers

    JG

  7. I'm unclear on this. Are you saying that IE8 solves all the problems you listed here?

    If you are unable to see the 32bit and 64bit files to download, please try reloading your browser window. I find that this usually corrects the issue.

    Sorry, to clarify:

    IE8 works, Google Chrome doesn't (and still doesn't)

    I was wondering if Google Chrome is not supported for NI FTP?

    Or is it just me?

    Anyways, I have my software, that's all that matter :)

  8. Hi fellow LabVIEW developers and Users,

    Last week MoviMED (www.movimed.com) launched the AF-1501 analog frame-grabber for NI CompactRIO and NI Single-Board RIO.

    This is the first vision-enabled C-series module for RIO and opens a new dimension of possibilities in the Programmable Automation Controller (PAC) world. It allows the RIO platform to capture images from Analog Video (AV) sources, including the most common standards (NTSC/PAL/SECAM).

    You can now acquire images from CCTV cameras, thermal cameras or low-cost spy cameras and process them with NI Vision RT in the CompactRIO/Single-Board RIO platform. Therefore the embedded real-time platform is now able to react (gather or store data, set signals, actuate on motors, etc) based on the acquired images.

    For those of you interested in the module check the description, data sheet and documentation at http://www.movimed.com/AF1501-framegrabber.htm .

    You can now buy it from http://www.movimed-store.com/ !!!

    This module sounds cool

    I have been checking it out as NI just announced Machine Vision on CompactRIO.

    The article mentions your module as well as support for IP cameras on cRIO

    We've used the CVS before for the sole reason of VGA output support.

    If the cRIO had this feature we could just use it instead.

  9. As promised, we have begun posting the beta software. If you've waited for this prior to applying for the beta, now is your time.

    Hi Robert

    The only (windows) software I can download is the Platform DVD2. Platform DVD1 gives an error and 32bit and 64bit are empty?

    Is there any reason for this? - I will try again later tho.

    Cheers

    JG

    <edit>

    Seems my Google Chrome can't see the downloads?

    IE8 is working tho so I am happy

    Cheers

    </edit>

  10. hi all,

    I want to access database on one PC(let’s consider A ) from remote PC (let’s consider B ) in LabView. I am using Mysql 5.1 with ODBC 5.1.

    On B mysql 5.1 is configured as server while on A it is configured as development machine.

    On both A and B, we have checked with command prompt. With command prompt it is working fine but when I tried to make UDL file (to access database in lab view) it is showing error as connection Failed.

    And also please let us know setting about how to configure mysql as a server for particular database in “MySQLInstanceConfig.exe””

    And similarly for client to access server database.

    And guide also for software selection that we are using i.e. Mysql server 5.1 and connector/ODBC

    Please send me correct procedure to make server client connection.

    pravin

    Hi Pravin

    Attached is a protocols (how-to) document I wrote for my library on the subject, hope it helps.

    LabVIEW - Connect to mySQL.pdf

  11. However the main reason I posted the alternative solution was that the OP may not have been aware it could be done without all the string conversions. Unless required for something specific his procedure required lots of extra work to accomplish a very simple task.

    Yes, yours was a much better solution - mine officially sucks :)

    I didn't even think down that path - just followed the steps!!

  12. I understood what he was saying, but before reading his post I hadn't realized it was possible. I had just assumed that poly VIs had to have different inputs. It never occurred to me that it wasn't a requirement.

    I love to create APIs like this.

    And used to do it alot when I used MFVI/Action Engines for encapsulation.

    Now I would rather use LVOOP so I don't do as much.

    Anyways I wanted to add:-

    Don't forget that ":" in your Menu Name lets you create submenus which is really handy for creating a menu hierarchy for the developer to navigate.

    post-10325-126162067712_thumb.png

  13. no joy with uninstalling.

    Hi Neil

    In order to refresh everything:

    1. Uninstall the package using VIPM.
    2. The package backs up the original hooks to the <vi.lib>\addons\_JGCODE Toolkits\lvoop custom user scripting folder under the NewAccessors Original sub-folder. Delete the above lvoop custom user scripting folder (if it exists).
    3. Copy the attached files to their respective locations in <LabVIEW>\resource\Framework\Providers\LVClassLibrary\NewAccessors . These are the original (empty) hooks that come with LabVIEW (ensure they are not read only).
    4. Everything should now be back to default.
    5. Ensuring you have the latest package
    6. Install the package using VIPM.
    7. Test an example class.

    Please let me know how you go.

    Cheers

    -JG

    NewAccessors Original.zip

    [LabVIEW 2009]

  14. Here is what I am trying to do - posted on the Dark Side...

    Hi Norm

    All I am trying to do is create a shortcut for Size To Text property for a Free Label.

    Just the same as when are typing into a String Constant and you can press Shift + Enter and it sets Size to Text = FALSE and jumps to a new line without adding a line feed constant (<LF>)

    I thought Quick Drop (QD) would not disturb the flow of typing as currently I have to start and stop to do it.

    Workflow:-

    Typing text in Free Label reach certain width you do not want to exceed

    Hit QD shortcut

    Free Label text jumps to new line without adding a <LF>

    Focus is returned to the new line

    Continue typing etc..

    Hope that makes sense.

    Don't know if it's possible??

×
×
  • Create New...

Important Information

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