Hello
I used the original CAN ID from the other day but I set the PV380R2, but when I set the PV380R2 using the original CAN ID, a problem occurred connecting with PowerVision. By using sample configuration data for PV380R2 which is standard in PowerVision, you can connect with PowerVision normally.
If you can advise on this condition, please let me know. Describe the equipment and version you are currently using below.
Thanking you in advance.

Component equipment
PV380R2
PowerVision 2.8.10546
ECOM Standard Cable E2046000
ECOM Software Driver ver 3.1.0.15

The information that you have given looks fine. I'm not sure what the CAN ID is referring to. I think from what you said that PowerVision can connect to the display when you have a standard configuration loaded and not otherwise. Something that I'm thinking about is if the CAN port baud rate is changed in the configuration then PowerVision will not be able to connect to the display unless it is in the bootloader. To stop the display in the bootloader hold buttons 1 and 4 while powering on. If this is not the problem then please describe the CAN ID and the changes that were made. If you can send the configuration to me in a Private Message then I might can help.

Hi boyce
Thank you for your reply

Certainly the baud rate was set at 500 kbps. So, after changing the baud rate to 250 kbps, I was able to connect properly.
However, the baud rate of the device connecting the set display is determined to be 500 kbps, and it is necessary to set it at 500 kbps from now on, but there is a way to connect PowerVision and PV 380 R 2 according to the reference manual while keeping the baud rate at 500 kbps do you have?
By the way CANID used this time is original ID based on J1939.

Thank you for your help in advance.

PowerVision can connect to a display that is running CAN at 500 kbps by changing the Connection Settings. Click on the Edit Connection Settings... link and select 500 Kbps.

Hi boyce
I'm really helped by the answer from you. Thank you!

I tried that way many times, but the message "CAN Target ....." is displayed when connecting the display to PowerVision and transferring the configuration data set with CANID to the display. .. I am unable to confirm the detailed message by removing the seat now, but I think that it was such a message.
What I'm looking for now is a method to easily transfer the configuration data with the baud rate set at 500 kbps while keeping the bus bit rate at 250 kbps, according to the reference manual. Is there a good way to do it?

Was the message "CAN target device failed to reply"? If it was, when did it happen? Was it during or after completing a configuration or a full install?

If you are programming the display on a bus that is 250 kbps and the configuration is 500 kbps the display will restart at the faster speed and PowerVision will not connect with it. The display will have to be taken off the slower bus.

Hi boyce
The message display compiled the configuration file and the message "CAN target device failed to reply" was displayed just before transferring the data to the display. In the current situation, the display recognizes when setting Bus Bit Rate from 250 kbps to 500 bps, but the above message is displayed when transferring at 500 bps, Boot Loader is started when Bit Rate is set to 250 kbps, feeling that the configuration data is transferred to the display is.
In this way it will give similar results even if you try it multiple times, so I am planning to proceed with development in this way.

Boyce Can I ask another question?
When setting parameters on PowerVision display, setting it with Smart Gauge will not display on the display.
On the other hand, if you set it using Text Gauge, you can set it properly, and if you give data (Hex) to the parameter using PCAN - View, display will be displayed as desired.
Can I use Super Gauge to set it very easily like Text Gauge?
If you have a simple setting method, I would like to tell. It is quite impatient.

Okay, I see the problem now. The display has to be programmed at 250 kbps. When trying to program at 500 kbps it actually switches to the bootloader to download the application and configuration. When it goes to the bootloader it expects the programming to be done at 250 kbps and that is what is causing the "CAN target device failed to reply" message. Forgive me for not understanding the problem right away.

Your second question about the Smart Gauge, could you please send me (Private Message) a small sample configuration that demonstrates the problem that you are describing?