LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Mac OS X troubles!

Hi All,

We just got bought a full copy of Mac OS X Lab View and are very
frustrated. Is there anybody out there who is successfully doing
developement with Lab View 7 on Mac OS X 10.2?

The first problem we have is that context help is fubar. Getting help
on a item brings up not the items help, but the overall help. Then if
you get the index to try to find that object, you click on "i" you get
the i's but no scroll bar! This is basic html frames stuff, right?
Is there a hack to make this work?

Then with VESA serial stuff, we were promissed that mac osx was fully
supported, but to build a VESA doc, the manual says that the setup
programs are Windows only!!! That's not mac support.

Then with serial ports, how do you know that you are opening the
right
serial port. A mac (12" G4 laptop) with no serial ports reports 4
ports... then we want to add multiport keyspans to talk to the
instruments.

We got our who lab working on Mac OS 9 with Lab View, but would like
to get everything to OS X since it is sooo much better than 9!

Anyone have any good war stories/good hacks they'd like to share? We
really don't want to go back to OS 9 or Windows.

This is ALMOST a really great product, but it sounds like the QA team
isn't setup for the OS X yet.

Thanks!
-kurt
0 Kudos
Message 1 of 11
(4,035 Views)
The following known issues are listed in the Mac OS X readme that was included on the LabVIEW 7.0 CD:

  • If you click a link in the Context Help window or when you click a Help button, the exact page for that object does not appear in the Web browser. This is a bug in the Mac OS and is not fixed as of Mac OS X 10.2.5.
  • If you click the Index button in the LabVIEW Help, the scrollbar might not appear in the left pane of the Web browser. Resize the browser window to display the scrollbar.

We are looking into the latter issue for a future release of LabVIEW. It is difficult to reproduce reliably. Could you please email your Mac OS version and browser name and version to techpubs@ni.com ? That will help us troubleshoot the problem.

Thank you,

Kelly Holmes
LabVIEW Documentation
Kelly H
LabVIEW Documentation
National Instruments
0 Kudos
Message 2 of 11
(4,035 Views)
>
  • If you click a link in the Context Help window or when you click a
    > Help button, the exact page for that object does not appear in the Web
    > browser. This is a bug in the Mac OS and is not fixed as of Mac OS X
    > 10.2.5.

    That seems crazy that this is an OS bug! I just don't believe that's
    the cause.


    >
  • If you click the Index button in the LabVIEW Help, the scrollbar
    > might not appear in the left pane of the Web browser. Resize the
    > browser window to display the scrollbar.

    That means they left out a scrolling="AUTO" in the frame tag... this
    is basic QA stuff and very frustrating for a commercial program....
    for a company that wants to break into the Mac market....
  • 0 Kudos
    Message 3 of 11
    (4,035 Views)
    In article , "Kurt"
    wrote:

    > Hi All,
    >
    > Then with VESA serial stuff, we were promissed that mac osx was fully
    > supported, but to build a VESA doc, the manual says that the setup
    > programs are Windows only!!! That's not mac support.
    >
    >
    Hi Kurt,

    I can't help with other stuff but I have some ideas your VISA problem. I
    don't have a Mac nor have ever used one with LV but I do run LV on Linux.
    Since I hear that OS X is unix based, it may be ok to assume it handles
    VISA configuration in a similar way to LV for Linux.

    When I want to configure VISA I go to the path
    /usr/local/vxipnp/linux/NIvisa/ and run visaconf. The path is probably
    different on a Mac. If you don't have it you may need to ins
    tall the
    nivisa package. Here's a link to NI's ftp site:

    ftp://ftp.ni.com/support/visa/drivers/mac/3.0MacOsX/

    The VISA package didn't come with the LV7 installation for Linux. This
    may be true for Mac too. There are some other packages installed on my
    sytem: nicvirte and nivisaserver. Not sure if you need these too.

    Hope this helps.
    -Kevin
    0 Kudos
    Message 4 of 11
    (4,035 Views)
    Kurt,
    Has NI given you any answers on this botched LV 7 for OS X? I have contacted an executive to get some answers about his previous affirmation that NI will continue to support the Macintosh on OS X. Today that statement is not true. What appears clear but has not been confirmed is whether this is a misstep or a deliberate phase out.

    We can't resort to compatibility mode because LV can't find the hardware.

    I choose LV because of the product range and the versatility. They just took that away.

    Regards,

    Raymond
    0 Kudos
    Message 5 of 11
    (4,035 Views)
    They have been sort of responsive... but I'm still not totally
    pleased. I've been messing with some stuff being in Virtual PC to run
    windows. They say Mac OS X is "fully supported" but some
    functionality will not be available until Mac OS X 10.3...

    -kurt

    > Kurt,
    > Has NI given you any answers on this botched LV 7 for OS X? I have
    > contacted an executive to get some answers about his previous
    > affirmation that NI will continue to support the Macintosh on OS X.
    > Today that statement is not true. What appears clear but has not been
    > confirmed is whether this is a misstep or a deliberate phase out.
    >
    > We can't resort to compatibility mode because LV can't find the
    > hardware.
    >
    > I choose LV because of the product range and the versatility. They
    > jus
    t took that away.
    >
    > Regards,
    >
    > Raymond
    0 Kudos
    Message 6 of 11
    (4,035 Views)
    RE: some functionality will not be available until Mac OS X 10.3

    Kurt,
    You have my attention. Has there been any rumours about getting better support or are they killing the product line by forcing this Real-Time issue.

    I don't think that a two OS system is the way to go. Not only will it be more unstable there will be increased compatibility issues not to mention buying a new version of Labview.

    Regards,
    Raymond
    0 Kudos
    Message 7 of 11
    (4,035 Views)
    > RE: some functionality will not be available until Mac OS X 10.3
    >
    > Kurt,
    > You have my attention. Has there been any rumours about getting
    > better support or are they killing the product line by forcing this
    > Real-Time issue.
    >
    > I don't think that a two OS system is the way to go. Not only will it
    > be more unstable there will be increased compatibility issues not to
    > mention buying a new version of Labview.
    >

    The RT solution is what is available today, and it works for both Mac
    and Windows. It isn't intended to kill the product, but rather to allow
    LV on a new OS, an OS that has a totally new driver model by the way, to
    have access to some I/O. The other way to access HW is to use the RLP
    (register level programmi
    ng) features of LV7.

    What will the future hold for OSX I/O. It is a bit hard to tell. The
    newer versions of the NI drivers are much more portable than older
    versions, but that doesn't make it automatic that the drivers will get
    ported. The key is to keep requesting the functionality and support the
    products that are available.

    Greg McKaskle
    0 Kudos
    Message 8 of 11
    (4,035 Views)
    > The key is to keep requesting the functionality and support the products that are available.

    Please Greg, every Macintosh LabView user that is affected by this misconceived NI strategy has spent thousands of dollars on both hardware and software supporting NI. The high handedness and total lack of concern by NI has shown that the support is not reciprocal. Surely, unless you are trying to eliminate support of the platform, NI could share with its supporters a description the path that they are following.

    The difference is that they only have to choose RT if they have a use for it. The popularity of this Mac RT strategy probably lies in th
    e percentage of Window users that opt for RT VS other DAQ.

    I have accepted that I have to ride at the back of the bus, but I would like that to be inside.

    RL
    0 Kudos
    Message 9 of 11
    (4,035 Views)
    > I have accepted that I have to ride at the back of the bus, but I would like that to be inside.

    Understood. As one of the "mechanics" of the bus, my typical ride is in the engine compartment or beneath it all. But I knew that when I signed on, and I rather enjoy it.

    Here is the story from my point of view.

    Apple badly needed to rennovate their OS, so they did. In doing so, they invalidated most of the work already done to support it. NI has spent the money to port LV to this totally new OS. Being an application, we were able to reuse a decent amount of our code, but it still took quite a bit of time and money. It will take more than a handful of LV purchases on OSX to go from red to black, but NI did the port anyway.

    Drivers are not application SW, and don't get to reuse nearly as much code from the old driver. And to be honest, they wouldn't want to. The driver groups long ago started working on DAQmx, making it a more nimble, more componentized, and more portable driver architecture. It was a very big investment, so the goals became more and more focused -- meaning that DAQmx is only available for Windows.

    Some drivers and some I/O is already available for OSX, but not all. The decision to port a particular driver to OSX will come down to how much technical effort is required, and a forecast of how many can be sold.

    In the meantime, the way to do I/O with NI HW on OSX has been spelled out. It was conceived in part by looking at the users that had VXI chassis with a Mac acting as the UI front end, and this solution is a good migration path for them. It isn't as good for the person with a simpler system that doesn't need or want RT, but that was the only technical solution available at the time. With the release of LV7, there is now register level programming support as well. Again, a good solution for some, not for others.

    > The high handedness and total lack of concern by NI has shown that the support is not reciprocal.

    I'm not sure what was expected or how you reached this conclusion. Within NI, there was much fretting about what the technical solutions were and estimating the cost of those solutions. Marketing and sales was given the not-so-pleasent task of being the primary delivery path for this news.

    If you have more comments on how the strategy was delivered, you can voice them, but going forward, the decision will be market driven to an extent. Many people within NI like Apple products and believe that it now has a super OS. But it is difficult to decide not to work on a sure thing in order to gamble on an OSX product. NI had a great excuse to drop all Mac products when OSX was released. They made the investment to release a number of products and are still investing in the OSX product line.

    Greg McKaskle
    Message 10 of 11
    (4,035 Views)