Am FRUSTRATED, trying to download an application from PanelBuilder 32 (ver 3.71) to a PanelView 1000 (Cat# 2711-T10G8, Ser D), using RS-232 (from real port). PB32 uses PFTSERV.DLL and PVDF1F32.DLL as it's communication panel.

The printer terminal is disabled on the PV. Cable, serial port and software verified good by up/downloading to/from PV600 with no problems.

When downloading to the PV, PB32 shows that it is starting the download, as does the terminal. Both show the process get to 3% (512 bytes of 14522 transferred) and stop. Terminal displays "File not supported"; software displays "Application file is incompatible type", then gives error 4091. Also will not upload the original program residing in the terminal.

I'm trying to download an application modified from a PV900 to work on the 1000. It worked fine with the 900. I actually have two PV1000s and both do the same, so am doubtful of it being a firmware issue (one has earlier firmware, the other more recent).

Am I just not holding my tongue right? Are the planets aligned in such a way to screw up communication? Do I need to throw it in the pond? Any suggestions?

Thanks,
Jimmy

What message do you get when you try to upload? The download problem you describe DOES sound like the wrong firmware revision was selected when writing the panelview program, either that or the wrong model of terminal was chosen, etc.

If you could get it to upload you could take a look at the terminal setup parameters and compare them to what you put in your program.

Oh, and I seem to be saying this a lot lately but, if you have a Flash ATA PCMCIA card on hand, you could avoid upload/download problems alltogether by using the card to do the file transfers.

[/quote]

What message do you get when you try to upload? The download problem you describe DOES sound like the wrong firmware revision was selected when writing the panelview program, either that or the wrong model of terminal was chosen, etc.

If you could get it to upload you could take a look at the terminal setup parameters and compare them to what you put in your program.

Oh, and I seem to be saying this a lot lately but, if you have a Flash ATA PCMCIA card on hand, you could avoid upload/download problems alltogether by using the card to do the file transfers. [/quote]


When uploading, it goes to 100% but then PB32 says "Unable to load file. Not a PanelBuilder 32 file or file is corrupted or disk space is low."

And I meant to mention, I tried the flash memory card and it gave the very same error as if trying to load from RS-232.

The program is config'd for the model no. and rev. no. I don't see anywhere to tell the software what the firmware version is. Also tried changing some of the RS-232 parameters, but that made no change other than the software didn't see the terminal.

Any ideas about telling PB32 what firmware it needs?

You said you're using PB32 version 3.71.. The latest version is 3.82. My suspicion regarding the upload problem, since your software doesn't recognise something that MUST be a valid .PVA file, is that it was written with a newer version of PB32.

As for the download, it still sounds like one of the terminal setup parameters in your program don't match the terminal.

and BTW, you choose the firmware level when you first create the application (see pic). You can go into Terminal Setup later on if you need to change it.




and BTW, you choose the firmware level when you first create the application (see pic). You can go into Terminal Setup later on if you need to change it.

Well, right... the terminal setup was the trick! I had been thinking the terminal setup was setting up how the terminal talks to the PLC - RIO. Had not noticed that with it selected for RIO that a different model number was displayed!

Now, my terminal still doesn't talk to the PLC, dangit!!! Is there another comms tab I need to congifure? Am paterning this after a PV600 program that works using RIO, but building it over a PV900 touch screen program of questionable origin. The PV600 configs comms for RIO, but loads via DF1 (?!?).



Seems like since the 600 and the 1000 have same comms ports (232 and RIO) the setup should be the same.