Sypris Teslameter Driver_too early to convert to 8.5 labview version

I am new to labview (8.5) programme and trying to use it to run my setup. I connected the Gaussmeter/Teslameter (FW Bell Sypris 6010) to the computer using serial port and RS-232 cable and used the driver (from the company) for this type of devices in order to allow labview to communicate with this device but there is always an error when I try to access the device through labview. This error says:
"VI version is too early to convert the current LabView version"
I would really appreciate any help in getting this solved.
Many thanks
Hadiq
Islam means peace
Solved!
Go to Solution.
Attachments:
FWB6010.zip ‏412 KB

Thanks for your suggestion. I did it and hope to get it sorted.
Many thanks,
hadiq
Islam means peace

Similar Messages

  • TestStand Deployment Issue - VI too early to convert

    I have a test system which has LabVIEW 8.0 and TestStand 3.5 running VIs and sequences developed on this system. I am trying to replace this with a deployment system and not having much success. I admit I'm pretty green with LV8 and TS3.5, but reasonably computer savvy.
    I purchased the same DAQ boards used in the existing system and installed them in a new PC. The PCs are different types, the existing system is a HP Pavilion and the deployment system is a Dell. I didn't think hat would have much effect.
    I created a deployment install image on the development system. I tried this a few months ago and was able to get a simple test deployment working. Now that I've got the actual DAQ hardware, I attempted to deploy the full test system. It installed OK on the deployment system, but when I run a sequence, I get a message that states:
    LABVIEW: VI version is too early to convert to the current LABVIEW version.
    The notable differences between the two systems include:
    1. Different PC types
    2. Possibly a different DAQmx version - I installed DAQmx from the CDs that came with the new hardware, not from the original CDs.
    3. XP Pro instead of XP Std
    Any suggestions? Like I said, I don't have a lot of experience with this, so any help is appreciated.
    Thanks,
    Blair

    Thanks, Rick. I tried checking Daqmx 8.0 as one of the drivers to load with the build and got an error. The error indicated that the driver couldn't be loaded as Measurement Studio wasn't installed.
    I'll have to see if I can find the original drivers that were used with the old system and remove the drivers from the new system and install the old drivers. I suppose I could try installing the new drivers on the old system and then doing the build, but I hesitate to do that as I am afraid that something will get broken on the old system and shut down production. I've already had one issue during start-up that caused the license to invalidate and had to re-install the license, so I would rather not make any changes at this time.
    Unfortunately, a subcontractor created the original system, and I don't know if I have the original driver disks.
    The driver disks that came with the new DAQ boards show ver 8.6.
    The version number of Measurement and Automation Explorer is the same.
    Blair

  • Lvwutil32 version too early to covert to current LabVIEW version?

    Hi all,
    I am looking to control the windows panel with some of the useful vis stored inside the lvwutil32 lib. However when I tried to open the vis inside the library, an error message saying that the vi version (4.0) is too early to be converted to my current LabVIEW version (8.5.1).
    Is there anyway to reconvert the vi that my current LabVIEW can use? It is a great shame as from the readme that comes with the lvwutil32, it seems that there are a lot of useful vis that I would find very useful for my projects.
    Hope someone could provide some help on this. Thanks!
    Solved!
    Go to Solution.

                           Hello,
                           I am having the same problem as YuanGe(the topic owner). I wanna open a file from the 5.1.1 LABview version on my LABview 8.6 and occurs the same error message.
                          I would be very grateful, if anybody could help me.
                          Thanks.
                          ps: The file is just down here.
    Attachments:
    ag8614x.zip ‏2795 KB

  • How to convert llb from LabVIEW version 8 to 7.1

    Can someone tell how to convert the llb from LabVIEW version 8 to version 7.1?
    I hope to sent the program to the others, but the other side are using LabVIEW version 7.1 but not version 8.0.
    I know I can save to VI file as previous version, but it contains severals of VI in the library, it is quite time consuming.
    Can everyone sugguest any method or solution to solve my problem.
    Thanks.

    Hi anson,
    it will run also in LV7.1 - but you should check those warnings (probably things not/differently supported by LV7.1...) anyway!
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • TS4.2: VI too early to convert

    Hi,
    I'm getting the error -18002 VI too early to convert when I execute a TestStand 4.2 sequence file with the TestStand Base Deployment Engine. I created the Deployment installer with the deployment tool in TS4.2 and installed it on a second system. I added all needed LV runtimes and drivers incl. TestStand Deployment Engine. All installed softwares shown in the MAX are equal to the Developing system. But on the target system I always get the mentioned error. So I searched the NI Forum and found a similar Problem, but no real solution for that. I think, that the TestStand Base Deployment Engine on the target system chooses the wrong LV runtime engine, something higher then 8.2.1 (this is the version of the VI's). When I change the Labview adapter the the developing system to 8.6.1, I get the same error. But with 8.2.1, everything works fine.
    How can I change the default LabView Runtime Version for the TestStand Base Deployment Engine?
    Thnaks in Advanced
    M. Tiedje
    Solved!
    Go to Solution.

    mtimti wrote:
     [...]I need a something like the LabView Adapter (like in TestStand developing system) in the TestStand Base Deployment System.[...]
    The TestStand deployment has also settings for Adapters. It is possible, that your UI does not supply you with the option to change those settings. You can always install the predefined UIs delievered with TestStand and run it on the deployment system. You can then change the settings for the LV Adapter as needed.
    mtimti wrote:
    [...]All my settings and software version are identical on both systems.[...]
    If this is true, then the LV Adapter settings should already be correct. Therefore, there has to be another reason for this behavior. But please check the settings as described before.
    mtimti wrote:
    [...]The whole problem started when we decided to change the TS version form 3.5 to 4.2. everything was fine with 3.5 and I thought I only need to deploy everything again and that's it, bau then came the VI version error.[...]
    Never heared something like this. I asume that not only TestStand was updated in the process. Is it possible, that you have been working with something older than LV 8.2 when using TS 3.5? If so, please masscompile all VIs using 8.2 before deploying them.
    hope this helps,
    Norbert 
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Help convert from 7 to labview 6.1

    Hi,
    Could anyone help me to convert the code to labview 6.1
    Thankyou very much
    Attachments:
    ag663xxa.zip ‏503 KB

    You can try creating a 6.1 driver yourself. All the IVI drivers are simple wappers around a Call Library Node Function into the DLL created in LabWindows/CVI. The LabVIEW driver is created from the Tools>Instrumentation>Import CVI Instrument Driver selection. Download the CVI driver and install it. The converter will require some files installed in the \VXIpnp\WinNT (.fp) and \VXIpnpWinNT\bin (.dll) folders.

  • HELP: convert instruments' drivers to Labview 6.0?

    Anyone can help me to convert the drivers from labview 7.1 to 6.0? Or anyone can tell me how to do that. I appreciate your help . Thanks! send emails to [email protected]
    Have a nice day!
    Attachments:
    hp8753x.zip ‏832 KB

    Here it is.
    Attachments:
    hp89400_6.zip ‏1194 KB

  • Adobe pro to convert pdf to word (trial version) not installing

    cannot install adobe pro (to convert pdf to word) trial version on my mac

    Hi Joe ,
    Could you please specify ,what exactly are you trying to install ,Adobe Reader or Adobe Acrobat .
    Adobe Reader does not allow you to convert PDF' .It is a software meant to view PDF' only whereas Acrobat is meant to view and edit PDF'.
    If you need Adobe Reader refer the following link .Adobe Acrobat Reader DC Install for all versions
    If you need Acrobat perpetual license ,refer the following link Download Acrobat products | Standard, Pro | DC, XI, X
    And If you wish to subscribe for Acrobat DC ,refer the following link .Download Acrobat DC (Continuous) | Enterprise or VIP
    Regards
    Sukrit Dhingra

  • How do i convert my Photoshop CS 4 version from Windows to Mac

    How do i convert my Photoshop CS 4 version from Windows to Mac.

    You are not likely to be able to convert your CS4 license/version from Windows to Mac.  Platform conversions are only supported for current releases, which would be CS6.  Creative Cloud subscriptions allow for either or both platforms to be supported.

  • Convert these VIs ZLibInflat​e,ZLibDefl​ate of LabVIEW version 5.0 into LabVIEW 2009

    Convert these VIs ZLibInflate.vi,ZLibDeflate.vi of LabVIEW version 5.0 into LabVIEW 2009

    Hi priyash,
    you should be able to download them with the VIPM.
    Mike

  • Is there any problem in converting my 3g phone software version from 3.0 to 4.2.1

    is there any problem in converting my 3g phone software version from 3.0 to 4.2.1

    yes you can upgrade from 3.0 to 4.2.1 without any problem if it's officially unlocked.

  • Labview 7 crashes when opening an earlier Labview version VI

    Hello guys. I am using Labview 7 professional edition. The labview crashes when opening an earlier labview version VI. The error message I'm getting is just "Labview has encounted a problem and eneds to close. We are sorry for the inconvenience." The VI contains a few Tag SubVIs, and It is written with an earlier version of Labview(BridgeView is what it was called).
    Do anyone have any ideas that how I can fix this bug? It's going to be a great help. Thank you very much.

    Hello,
    LabVIEW should not be crashing in this situation. Now, does this happen for other similar VIs too? It could be possible that a particular VI is corrupt. Also could you post your VI here so that I can try and reproduce the problem at my end.
    Regards,
    Chetan K
    Application Engineering
    National Instruments

  • May I get this program converted to readable in Labview 2010?

    May I get the following programs converted to readable in Labview 2010? I think the real files are in Labview 2013!
    Thank you
    Solved!
    Go to Solution.
    Attachments:
    Loop for RAE Read.vi ‏13 KB
    Test to separate bits from Binary.vi ‏9 KB

    http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion

  • Hello, I'm trying to convert my music to mp3 Version but it says that the file is protected. Is there any way I can convert it?

    Hello, I'm trying to convert my music to mp3 Version but it says that the file is protected. Is there any way I can convert it?

    Only by burning the files to an audio CD and then ripping that back into iTunes.

  • Labview version 7.1 is too old to convert to current Labview version 8.0

    I had developed my Labview code sometime back using LV-7.1 and now I am trying to deploy it on a new PC. The Test Stand version that I have is 3.1. I did everything right and after I installed my deployment package, I get the error that the Labview version 7.1 is too old to convert to current Labview version 8.0.
    I am going to look into converting my code using Labview 8.0, but I am puzzled, why would it matter, as am using the same Labview (7.1) and TestStand (3.1) as before, and getting this error? I also installed the old Traditional DAQ drivers (instead of the DAQmx) and so everything is the same except that the PC is new.
    Shoab
    Attachments:
    ErrorMessage.jpg ‏225 KB

    Hey Shoab,
    Are you getting this when you run the sequence in the Sequence Editor?  If so then I would suggest checking the adapter configurations.  Go to Configure>>Adapters select LabVIEW and click the Configure.. button. Once in there you can change the run-time engine to 7.1.
    Let me know if that helps.
    Regards,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

Maybe you are looking for

  • High School highlight video (Widescreen or standard)

    I am making a high school football highlight video for college recruiters. The capture video is widescreen. Should I convert it to a 4:3 project or leave it 16:9. I am not sure if they will be using widescreen televisions.

  • Need Help with Skipping Audio in Slideshows

    I'm trying to burn a simple slideshow with iDVD of about 80 pictures, with an overlay .mp3 playing. I made the slideshow, and during the preview, the audio plays fine. But after I burned it, the mp3 skips slightly while the pictures change. I initial

  • IIS Failed Request Tracing for one specific URI only

    Hey everyone, I tried setting up IIS Failed Request Tracing for one and only one specific URI to debug a problem that persists with this URI. The problem about filtering it is that it's a HTTP 200 response that contains an error message from a 3rd pa

  • Cleaning up obsolete interrupts in process chain

    Hi Everyone, We have just recently started using process chains to manage our forecasting solution. We use Interrupt Processes to wait for triggers from external systems. However, recently we've had a problem wherein certain interrupts no longer wait

  • Short dump while loading from ods1 to ods2

    hi, When iam loading from ODS1 to ODS2 geting shortdump.I generated ODS1 as datasource and iam loading the data.Can i able to delete the generated datasource from datamarts. bye GK