Hello,

Our customer tried to load configuration created by PowerVision Ver.2.7-Patch4 into PV780 but it failed frequently. The connection is LAN. When click LOAD, the error shown in the attached screen shot was displayed. After that, they updated BOOT LOADER from Ver.2.3.20006 to Ver.2.3.20019, then it works correctly. Given the situation, please kindly confirm the items below.

1) BOOT LOADER is uploaded to the latest version when FULL INSTALL is clicked. Is it correct?

2) The customer has two PV780 whose lot numbers are "J8" and "M6" (Rev-D). Why these lots have older version of BOOT LOADER Ver.2.3.20006?

3) Will the new PV780 have the older BOOT LOADER Ver.2.3.20006 as well in the future?

4) Such load error caused by different BOOT LOADER version is also occurred when it is loaded by USB connection?

Thank you,
tshiii

Hello tshii,

I am sorry there is a problem. I have put my answers after your questions.

1) BOOT LOADER is uploaded to the latest version when FULL INSTALL is clicked. Is it correct?

• A full install includes the operating system, applications and configuration. The bootloader is programmed separately.

2) The customer has two PV780 whose lot numbers are "J8" and "M6" (Rev-D). Why these lots have older version of BOOT LOADER Ver.2.3.20006?

• I need the part numbers of the PV780s to verify the bootloader version used in production.

3) Will the new PV780 have the older BOOT LOADER Ver.2.3.20006 as well in the future?

• It is very possible, I need the part numbers of the PV780s to verify the bootloader version.

4) Such load error caused by different BOOT LOADER version is also occurred when it is loaded by USB connection?

• Not sure, but I will find out when I know the part numbers.

Thanks!

Hello Sara,

Thank you for your prompt reply.

2)-4)
The part number of the PV780s is 78700560.

Please kindly confirm and reply to me on the 2)-4).

Thank you,
tshiii

Hi tshii,

Reply, part 2.

2) The bootloader will only be changed for production units when a change to the firmware is requested, such as the hardware reliability change.

3) Yes.

4) Probably not. The problem is most likely with the USB/ethernet communication. Having a mismatch between the applications and operating system versions on the display and PowerVision Configuration Studio can cause problems. Sometimes the 192.168.0.n. network space is used for corporate networks and this can cause problems. The Monoprice USB/ethernet adapters seem to have more problems than the Plugable adapters sold by Enovation Controls now.

There is a helpful post and a document about troubleshooting the USB/ethernet connection here. The information is mostly about using the static address 193.168.0.1/255.255.255.0.

It is important when changing major versions, such as 2.6 to 2.7, to create a full install of the new version and reprogramming the display. As we mentioned, this will get the application and OS in sync with PowerVision Configuration Studio.

We recommend doing the full install when you change to a new patch of PowerVision Configuration Studio also and reprogram the display.

I find I have fewer problems if the Available and Installed versions on the Configuration tab in PowerVision Configuration Studio match.

Hi Sara,

Thank you for the comments.

tshiii