I recently installed the Hypervisor on an APC4100 running Debian 12, and everything is working properly. The machine is running mappView and Motion Control without any issues.
I have a question regarding the startup behavior. Debian (OS2) boots significantly faster than the B&R Runtime (OS1). During this time, Chromium displays a local HTML page because the mappView URL (http://192.168.137.1:81) is not yet accessible. After approximately one minute, mappView becomes available and is displayed correctly.
What I would like to know is whether it is possible to display the startup status of OS1 during this waiting period. On the Embedded OS, I remember seeing information such as the Runtime version, boot progress, and startup timer. Is there a way to access similar information from Linux while Automation Runtime is still booting?
At the moment, I use a simple HTML page that periodically checks whether the mappView server is available and then automatically starts the visualization once the connection succeeds.
I also noticed that, using the terminal and the ADI sample applications, I can retrieve hardware information such as battery status and voltages. Therefore, I am wondering whether any target or runtime information is available during the boot phase that could be displayed on a local HTML page in Chromium.
Has anyone implemented something similar or can recommend an interface or service that provides OS1 startup status information to OS2?
Hypervisor do not have any specific API, that would return to you status of runtime. So I think your solution you have right now is the only available.
I’ve also thought about the question some time, but I agree to Jaroslav, I haven’t found any idea / solution.
Maybe SDM starts a bit earlier then mappView server, I haven’t tried it (I assume: if that, then only a few seconds). So deriving some information out of SDM response makes also no sense in my opinion… but at least, you could forward your browser to SDM if there’s still no reaction from mappView server after the expected boot-up time + some buffer time? This would give the user at least some hint to check the boot state in case of service or diag boot of AR (or even the information that something went completely wrong, if even SDM is not reachable)?
Getting data about the state as early as possible would mean using the online protocol ANSL. There’s a possibility named ANSLUIF where you can programmatically access the protocol with Linux, but ANSLUIF is like PVI on windows - nothing to use out-of-the-box, just a DLL-like interface that you have to use in your own C program… and even ANSL starts somewhen later as the Hypervisor and AR itself, so even if investing some time to derive this information and inject it into a web page by some own program, I’m not sure if it’s really worth to do so… I just wanted to mention it.
Just for completeness: you mentioned ADI to access battery status and voltages for example. The Automation Device Interface (ADI) gives you access to the MTCX controller of the hardware itself to read some common, but also some B&R specific hardware informations. But this controller is hardware which is not driven by AR / Hypervisor or by the GPOS - it’s a integrated hardware device, which also don’t have any information about the OS running.