Re : labview RT ETS - can't install correctly

[Jorge_Amaral]

hello,

general idea of the question... IT'S SO HARD TO PUT A DESKTOP WITH LABVIEW REALTIME.

Creating systems that uses this OS with a Desktop implies that with buy lots of material only to build a single machine.

The last try was the following:

 - SBC Adlinktech 851

 - Network intel pro100

 - IDE disk (Master)

with all the requirements filled (PC Eval says that it's good)

The first system worked ok. But as a safety, we tried to creat a second system. And only changing the disk (with another one of the same brand) and standing all the rest, we never could put the system to work.

The solution that we found with another computer (with the exact same hardware) was with the boot by floppy. Cause the system couldn't start by him self.

So, in conclusion:

 - PCEVAL: says that it's all good but it's not true

 - formatdisk (RT tool): doesn't work every time.

This operation of making a desktop be a Labview realtime, implies that we experiment lots of disks, lots of floppies (cause they give errors and we think that the problem it's on it) restart MANY times.

So, I'm quite tired of that. But I'had some systems that already use it. So i've to create some backup systems. But it's very difficult. Can any one give some ideas. All the requirements on the NI site was taken cared. 

Thanks all

[ElRambo]

Hello,

Which version of LabVIEW RT ETS are you trying to install ? 

What is the processor of your desktop PC on which you are trying to install LabVIEW RT ETS ?

Is your hard drive formatted in FAT32 ?

Regards,

[Riconquistiamola]

Hello Jorge,

I am sorry to hear you are having such trouble reliably setting up a Desktop ETS system for LabVIEW Real-Time.

You mention setting up a second system, only changing the disk. Is the HDD on the second computer identical to the HDD on the first computer? If so, there is likely a BIOS setting or physical cable connection causing the problem you see. If not, what error messages do you receive on boot? Does swapping HDDs cause the first computer to not boot and the second computer to boot successfully?

The PC Eval actually boots LabVIEW Real-Time on the PC from the floppy, nearly identical to the Desktop PC Boot Disk, which is why your workaround to boot with floppy was successful. With both of these disks, the only files installed to the target are RT configuration files in a set directory structure.

Because of this, we have seen cases of the PC Eval returning successfully and not being able to fully install RT on the system. Typically the HDD cannot write all the files because it is configured incorrectly, has not been formatted properly, or is set incorrectly in hardware (as mentioned above).

Regarding the format disk, our developer posted a very good overview of this issue in another forum.

Cheers.

[Jorge_Amaral]

Hello All and sorry on the late reply. But i didn't received the usual mail when someone replies.

Which version of LabVIEW RT ETS are you trying to install ? 

Created with labview 8.5.1 ( i don't know if this answers your question - but the floppy disk for Labview RT ETS were created here MAX 4.1.1f0)

What is the processor of your desktop PC on which you are trying to install LabVIEW RT ETS ?

Pentium 4 - 3GHz

Is your hard drive formatted in FAT32 ?

Yes

_________________________

You mention setting up a second system, only changing the disk. Is the HDD on the second computer identical to the HDD on the first computer? If so, there is likely a BIOS setting or physical cable connection causing the problem you see. If not, what error messages do you receive on boot? Does swapping HDDs cause the first computer to not boot and the second computer to boot successfully?

I'de one computer. two disks. The first time i tried to install labview rt worked fine. Has a backup I wanted to have a second disk with OS already installed. Everytime I swap disks, the first worked fine but not the second. So, this tells me that it's not a connection or setting error (no?).

Second HD says that the OS wasn't found on HD. So, I let the boot to be by Floppy. And when I used Floppy Boot, the messages told me that the OS was found on HD (strange).

Regarding the format disk, our developer posted a very good overview of this issue in another forum.

I can't see this post. It returns error.

Thanks for the support

[Riconquistiamola]

Jorge,

Here is the post I mentioned. Sorry for the bad link.

For clarification, you have one computer and two disks? Are the two disks identical models? Is the hardware jumpers or switches identical between the disks?

If so, I recommend formatting the second disk for FAT32 to start from scratch.

[Jorge_Amaral]

Hello Michael! Thanks for the help.

My last post was refering to only one computer (this was made because we couldn't install RT on the others that we tried - but lets talk first only about this situation).

so:

 - 1 computer

 - 2 disks, same model and in Master

 - formating fat32 was made several times

One thing that i found strange it's that it seems that few persons had the same problems. Here the tests are made by a team of 4 persons. So, if we're making something stupid... It's a group of persons that are wrong.

[Riconquistiamola]

Jorge,

What program are you using to format FAT32? The format utility built into our software isn't as dilligent at checking for bad sectors as the Windows format. If you haven't already, can you format the hard disk for FAT32 using Windows?

Also, I don't think I read the exact error message coming from the second disk. Can you provide that information?

Cheers.

[Jorge_Amaral]

Hello,

i'm formating using a floppy disk created on windows XP. MSDOS startup disk.

The error on the second disk, i can't remember now. But i know that i couldn't use RT format disk correctly.

I know that this is few info.

When i receive the hardware i would do more tests and report you the errors.

[Jorge_Amaral]

Another issue its related with labview 8.6.

We sucessfully installed labview rt on a computer. Installing the base software worked ok. But after installing vision software, the system rebooted and after that, disappear on remote systems in MAX. Connecting a monitor to the ETS, we saw that the CPU indicator was freezed to a value near 30%.

[Riconquistiamola]

Hi Jorge,

Please let me know the error message when you can. It's difficult to move forward in our troubleshooting without it.

For your second post, I recommend reviewing Why does my Real-Time Target Hang on Reboot After Installing the 8.6 NI Vision Development Module? If that doesn't work, please create a service request with your local Applications Engineering Department.

Cheers.