Dlab-1 errors: reasons and solutions

Here are the Dlab 1 errors, their reasons and solutions.

Error: "+++ init sequence of image pc +++"

Reason: This happens when there is a connection problem between MPU and IPU. It happends due to one of these reasons:
- IPU is set to boot first from hard drive instead of LAN (Network card)
- time on IPU and MPU is different
- Linux image on the IPU hard drive is gone, because .done files were deleted, but new Linux images hasn't been created yet (in this case solution is to restart dlab one more time by turning off and then turning on, not just restart dlab software)

Solution:

1. Turn dlab off, connect a keyboard to IPU, then turn dlab on;

2. Let dlab boot until there is a message "+++ init sequence of image pc +++" on the monitor;

3. At this time disconnect the DVI cable from the IPU, then switch the VGA cable from MPU and to IPU and wait for white letters on black screen (it means that IPU started booting).

4. When you will see the first white letters on black background (the name of your processor and size of the memory), hit DEL on the keyboard many times until you get into BIOS.

5. In BIOS 1) set current date and time, 2) find "boot options", set network card as first boot device, hard drive as second.

6. Save changes and exit BIOS.

7. Turn dlab off from the side (there is a switch). Connect VGA cable back to MPU, connect DVI cable back to IPU. Turn dlab on.

8. Now MPU will boot, then it will turn on the IPU, which will connect to MPU and boot from it.

9. If the problem ("+++ init sequence of image pc +++") still there, press simultaneously ALT and CTRL on a keyboard, it will show a "watchdog" window, in that window click on "execute", find a folder with a lot of .done files and delete them, then shutdown the dlab and start it again. During IPU boot process, it will recreate Linux image and dlab should be working again.

We've done it many times and it worked.

01/30/2021

Error: "Communication between the EC and IP failed"

Reason: This error comes when the DVI cable is not connected to the IPU.

Solution: Shutdown dlab completely, connect the DVI cable to the IPU, turn dlab back on.

03/12/2021

Error: "Network communication error with d-workflow: it may happen that no other network orders are processed" OR "No connection possible to d-workflow. Autosave cannot be performed."

Reason: d-workflow software running on dlab can't connect to the d-workflow client that's supposed to be running on the imagebox. There are several reasons for that:
- network cable is broken (replace it)
- network switch/router is bad (replace it)
- network configuration on ImageBox is incorrect (it should NOT be automatic (DHCP), ImageBox should have specific IP address assigned to it)
- d-workflow client is not running on ImageBox (to run it, connect the USB keyboard to Imagebox, press Windows key on the keyboard, in the Start menu find "d-workflow client" and click on it)

Solution: In order to set correct network settings on the ImageBox:
1. Connect a USB keyboard to the Imagebox (if you have only PS-2 keyboard, then turn off imagebox, connect the PS-2 keyboard, turn imagebox back on).
2. Press "Windows" key.
3. Click on "Settings", then on "Network places".
4. Find your network card, open its settings and switch IP address configuration from automatic to manual, then type the IP address, that is shown on dlab in Settings > Network settings. In our case it was 192.168.1.120. After you type it, click Tab on the keyboard and "subnet mask" field will be set automatically to 255.255.255.0 . If it doesn't, please set it to 255.255.255.0 . Then click OK, OK and restart the imagebox computer and dlab altogether.

03/12/2021