Hi,

I just programmed a PV380, now it keeps bringing up the start-up(splash) screen, over and over again.
I used a new (to me) laptop with WIndows 10.

I tried to reflash with my old laptop (windows 7) but for some reason I can not get it going again.

I tried full install and load bootloader, but keep getting the message that file could not be transferred, because the configuration hardware definition is not connected with the connected device.

When I am at the configuration screen, it shows following parameters in the bos (right top of screen):

Available:
Built with 2.8.10366
App: 2.8.10028
OS 5.2
Loader 2.7.10112

Installed:
Built with: (empty, no information)
App: (empty, no information)
OS: (empty, no information)
Loader: 2.7.10112

Any tips or advice?
Is there a way to do a reset to manufacturer settings for the PV380?

Thanks,
Karel Vermeeren

Hi Karel,

Sorry for the issue. I know it is frustrating when it should be so simple.

In PowerVision, in the black ribbon near the top, be sure the hardware type matches the type of PV380 you are reprogramming. There is a difference between PV380 (the old hardware) and the PV380r2 (the new hardware). Some PV380r2 hardware has been shipped, but we haven't yet released a version of PowerVision that supports the new hardware.

[Edit - The PowerVision Configuration Studio 2.8.10491, patch 1, recognizes the R2 hardware.]

On the Configuration tab, you can tell what kind of device you are connected to as well as version numbers of the firmware on the device and what is available with the PowerVision Configuration Studio being used.

In the "Installed" box you don't see anything, it means PowerVision isn't connected to the device. That is why you get the message about not being connected. When PowerVision is able to communicate to the PV380 or any of our displays, the version numbers of the application, boot loader on the device and the version of PowerVision used to build the config on the device will be shown under Installed.

On the left side is a line, Communicate over:, just to the right of the box that lets you select the type of communication adapter to use, it should tell you a connection status. This can be information such as, Connection timed out or No devices found or it will tell the type of device communicating to PowerVision. If you have two configurations open, PowerVision ca get confused about who it is talking to.

You can change the hardware type using the link I the black ribbon.

Thanks Sara.

I eventually got it going again, I just kept trying "Load Full Install" and after about 50 times the programming did work, and I can use the display again.


I do see the PV380 (5-Key) in the black ribbon, but I can not find PV380 r2.

If I click on the PV380 link, I only get the option to select either "Controllers and IO" or "PowerView Displays".
After selecting PowerView Displays I get a list with:
Change to PV350 (5-key)
Change to PV380 (5-key)
Change to PV450 (8-key)
Change to PV780 (10-key touch)
Change to PV780 (10-key)

Is my software outdated? Or do I have to connect to a PV380 r2 to see it?

BTW my PowerVision software is Build 2.8.10366, Part nr: 78-33-3154


Anyway, the display is working again, that was the most important for now.

Thanks,
Karel

Hi Sara,

I'm having the same problems again.
The display seems to keep resetting. Over and over again evry couple of seconds.

I was trying to send a configuration to my PV380, and now I keep getting the following message:
"The file was not transferred succesfully due to the following error:
The configuration hardware definition is not compatibel with the connected device"

I send this configuration to several PV380's before without any problems, but to be sure it is not the configuration, I now opened the Murphy Standard PV380 configuration, and try to send this, but still the same message.

In the black ribbon it says: Murphy Standard PV380 PV380 (5-key) Editing in English
In the box in the right of my screen it says:
Available Installed
Built with 2.8.10366 0.0
App 2.8.10028
OS 5.2
Loader 2.7.10112 2.7.10112


BTW: This is the same PV380 as the one that was causing problems earlier.

Please advise, I spent too many hours already trying to get this going.

Thanks,
Karel Vermeeren

Hello Karel,

I know it is frustrating.

What is different about this one PV380 where you have the problem? Are there other devices on the CAN network when you are reprogramming? As you know, the PV380s are reprogrammed using the CAN so it is best to have an isolated network when reprogramming.

Would you be able to capture the CAN traffic and send to us? Then we could analyze the data to understand why PowerVision can't stay connected to the PV380.

We want to help you find the problem so that this doesn't keep happening. Any information you have that could help, I appreciate. If you can send the configuration to me using the private message, I could use it to try to recreate the problem also.

Regards,