Power panel PP400

“Hello everyone, I am reaching out with the following question. Recently, the memory card of an HMI Power Panel 4PP420.1043-K41 failed. I have the visualization project for this panel, but I cannot find this specific hardware model in the Automation Studio 3.x hardware catalog or on the manufacturer’s website. I can find the runtime for the …-K44 model, but not for the ..-K41. Could you advise on how to obtain this runtime upgrade? I am using Automation Studio 3.xxx.”

Regards

Hello;

I am quite sure that the model 4PP420.1043-K41 is a customer specific model that was designed for the specific machine manufacturer, that only them has access to it. If you belongs to the machines manufacturer, then by logging into B&R page should allow you to access to download it.

1 Like

I see that on our website, AS 3.0 Upgrade 4PP320.1043-K41:

@valerio.manenti
likely you have your user logged in. if you do it in a private sessions, you wont have access to it.

Correct @wenbo.ruan , I have just followed your instruction

So to sum it up, if you are logged in to our webpage and you cannot see this upgrade, then you have to get in touch with the machine manufacturer. If you have a backup, you can just restore it to a new CF. If you do not have a backup and the machine manufacturer does not exist anymore (it is quite old hardware), get in touch with your local B&R office. We can not provide you because of legal reason, sorry :frowning:

Thank you all for your help. At the end of the day, the manufacturer confirmed that the ready to use card has been shipped and also sent the missing file for the ..K41 panel. Essentially, the problem should be resolved tomorrow once the new card is installed. However, when we received the file, it was already the end of the workday. I had very little time and wasn’t able to successfully write the project to the CF card. I’m curious to know what was missing, could you please tell me what steps I might have skipped? I followed these steps: 1. Compiled the program without errors (AS3.0.90) . 2. Selected Tools → Create compact flash. 3. Specified the drive. 4. Clicked Generate disk. However, there are fewer files created in the three disks in comparison with the original failed one. When I insert this newly written disk into the HMI, it starts booting, then restarts, boots again, and ends up with a black screen. Which steps do I need to perform in order to write a working project to CF.

Regards

Hi @Afilimon ,
In our system since Automation Runtime V3.0 there is available a tool, System Diagnostics Manager (SDM), it can be used to diagnose your PP400 using a standard web browser.

You need an ETH cable, connect your laptop to the eth port of your power panel and type: http://IP-address/sdm/index.html, then select logger:


You should see some error messages.

SDM is not activated by default so I hope your machine builder enabled that in Automation Studio prj.
Thanks
Ciao
Valerio

Any news @Afilimon ?

Thanks
Ciao
Valerio

Good evening. As I mentioned, a new CF card has been ordered, and the decision was made to wait for it. It didn’t arrive today, perhaps it will arrive tomorrow. Most likely, my work here is finished, unless it turns out that the new card doesn’t work either. However, I am curious where I went wrong. If you still can, please describe in basic steps how to prepare a functioning CF card with the program and visualization included. Is it even possible to write the entire project to the card offline using AS3.x? I am a bit confused because it appears to be less intuitive than I thought.

You can do that. During the installation you can select some files (recipes, machine configurations files) from your laptop and copy them to the CF too, that’s why I asked you to check the logger, because maybe some files are missing; you can double check with your machine manufacturer too.

Ciao
Valerio

Hello, I wanted to share an update. The new CF card prepared by the equipment manufacturer arrived today. However, it did not work and showed the same symptoms. It failed to work with either of our two existing HMIs.

Out of desperation, we had ordered a third HMI (model ending in ..K42). This unit also arrived today and, surprisingly, it works even with the old card that we thought was demaged. The machine now is operating with this slightly different HMI model.

However, the question remains: what is wrong with the other two panels? They display an image during boot-up, but once loaded, the screen goes black. One detail I should mention is that both non-working HMIs were previously repaired due to power supply failures. I am unsure if this is relevant or if it could have corrupted the BIOS settings. The manufacturer reviewed the BIOS and saw nothing unusual.

Is there anything else I could test? In the project settings, I found IP addresses 192.168.1.105 and ..106, but they do not respond to pings. I also cannot access the SDM. I tried connecting the panel via the COM port using a 3-wire null modem cable, but when attempting ‘Online → Services → Transfer Runtime’, I get the error: ‘BootMGR error, com port in use?’.

Are there any further diagnostics you would recommend?

Regards

Hi @Afilimon ,
I’m sorry for your issues but if with new hw and both CFs no issue as you said should be some issue in the hw.
The positive thing (we have to find at least one in all situations), your sequence to write the working prj to CF was correct.

There is a way (if the system has generated the system logger…) to read the system logger from CF:
Storing data on the CF

When you have black screen, power off the main power, unplug the CF and upload arlogsys.br file (system logger); inside arlogsys.br we should see the reason of the problem.
Thanks
Ciao
Valerio

Hello, thank you for your continued help. As it turns out, there is a possibility to connect with AS via the COM port and go online. I tried performing the following functions: transfer automation runtime, then after compiling, sending the project to the HMI, but the result did not change. I also extracted the files from the newly prepared card after the black screen was showing. There are three partitions on the card, and I found this file in the data 1 and data 2 partitions, so I will attach both files.

Than you

arlogsys_2.br (201.8 KB)

arlogsys_1.br (201.8 KB)

1 Like

Hi @Afilimon ,
arlogsys_1 and arlogsys_2 are the same:

Regarding the logger:

Which card do you have plugged on your 4PP420.1043-K41? It seems there are some issues related to that card:


Thanks
Ciao
Valerio

Good morning, I am attaching photos of the card and the AS configuration. Do you see anything wrong?

Regards

Hi @Afilimon ,
I’m not sure if the B&R Community is the correct channel to find the information you need, I suggest calling our Support in your area.

You have 2 interesting messages: error in HWD, func <6>/<7>, dev , I checked in our database similar message, and I found one very old ticket (from 2007) where the customer reported a saving retained values on his machine, and He reported new message in the logger:

error in HWD, func <2>, dev
at the end there was an hw issue.

I asked AI more details about that message:
In B&R Automation systems, the error "HWD, func <2>, dev " typically indicates a hardware-related failure involving the SRAM (Static Random Access Memory) on the controller or a specific I/O module.

Error Breakdown

  • HWD: Stands for HardWare Driver. This prefix means the error was generated by the low-level firmware or driver layer rather than the application code.

  • func <2>: Usually refers to a Read or Initialization function that failed.

  • dev : Specifies the device or memory area affected. In this case, it is the SRAM used for I/O data or remanent variables.

    Thanks
    Ciao
    Valerio

I agree with @valerio.manenti; it looks like an HW issue. But this is only a guess based on the discussion that has been posted so far. For a deep technical analysis, the local B&R office support is the right channel.

Hello, thank you for your patience and help. It appears that both panels are not easy or even possible to repair. The local B&R representative confirmed these units are no longer supported, so no official assistance is available. I am now certain the issue is at the hardware level.

Based on the errors like , I ran some AI-assisted diagnostics and concluded that while the HMI reads the disk and somehow boots, it fails to fully identify metadata of the CF card and its memory type. It does not allow the system to start normally. I investigated whether corrupted BIOS settings could be the cause, according to the AI, this is possible, voltage issues are also possible.

During repeated reboot cycles, I noticed that entering BIOS (DEL key) became increasingly inconsistent. At first, it worked fine, then it required multiple attempts (pressing “DEL”), and eventually, it stopped responding altogether. After while I noticed, that I could only access BIOS if the CF card was removed, but now I cannot enter it at all.

Furthermore, I noticed the USB port is not providing power. Although I haven’t checked it with a multimeter yet, the keyboard backlight (which normally powers up even from a basic phone charger) remains off. I consulted my collogue who is a very good at repairing PC hardware at deep level, his opinion is that issue is either with power supply inside the motherboard or the North bridge. And he says, that usually it is difficult to fix such devices, because there are no components available on the market.

I am not sure if I will proceed further with this, but it there will by any new findings I will definitely share it. Thank you all

1 Like

Thanks for the summary. You are right; this HW is very old. Maybe it’s time to update your machine to a new control system; there are certainly companies that offer this service. I think even the local B&R service team can help you in same way. All these options are connected with some cost. Maybe you can try to buy used HW if you do not want to update the machine. There are so many options; all have some pros, cons, and risks connected. If there is anything B&R or the B&R Community can help you with, feel free to reach out to us :slight_smile: