I am connecting to a PV350 with the ECOM driver and PV Studio 2.6.20023 tells me it is a PV380 and will not load to it. If I change the display type in PV Studio to PV380, it sometimes tells me I am connected to a PV350, and other times a PV380. Change it back, and the problem follows. If I disconnect the display (timeout), then reconnect it, it says it is connected to PV350 bootloader, then back to PV380 again. I now have been able to load PV380 software to the PV350; it runs, but obviously no second CAN port.

Can you send any more info. For example have you loaded it at all from PowerVision or did it come with this behavior? We may need to look at production or a bug in PowerVision.

You can most likely fix it yourself by entering the bootloader(hold the outside two keys while booting). From here you can connect PowerVision (with a 350 configuration) and load it.

The software is suppose to prevent a cross load but as you saw there may or may not be a bug there.

Jake,

It was this way from the beginning, but with a twist. I noticed it when I tried to load a modified version of the downloaded Standard PV350 configuration (downloaded from forum), and it gave me the error that it was not compatible. I looked at PV Studio and it said it was connected to a PV380. I changed the type in PV Studio to PV380, then it told me it was connected to a PV350. I changed it back to PV350, and it then said connected to PV380. It did that a couple of times (I could not load any software at all) until I restarted PV studio. Since then, it has continually stated that it is connected to a PV380 (PV350 bootloader during power on). It allows PV380 software to be sent to it and seems to function.

It sounds like the Unit has the correct bootloader. I think we can correct the Application by loading a "full Install" from the bootloader.
1- force the unit to stay in the bootloader by pressing and holding the far left and far right buttons at power up. The RED lamp should stay on and the AMBER lamp should flash. The unit should then report as a "PV350 Bootloader" to PowerVision.
2- start PowerVision and open the desired PV350 configuration
3 - click the Tools Button and select "Generate Full Install"
4 - click the Tool Button and select "Load Full Install"
the unit will load and jump to the application. It should then report to PowerVision that it's a PV350.
I hope this helps...

After Jake had suggested it, I loaded a full install from the bootloader and it was corrected.