thiagoralves
For those of you that want to create nice graphical screens for your project, I've now added instructions to install ScadaBR on your computer. The instructions are very simple and are based on a ScadaBR image for VirtualBox that I created. This means that ScadaBR will run on your computer, no mater if your computer runs Windows, Linux or MacOS.

You can check the instructions on the OpenPLC Project website. Just go to Reference -> Installing ScadaBR
Direct link:  http://www.openplcproject.com/reference-installing-scadabr
Quote 0 0
rwalford
I have tired to deploy the ScadaBR appliance under vmware workstation.
It boots up to the login prompt but is not getting an IP address. The admin/admin credentials do not work for the OS login and OS credentials are not in the documentation.  DO you make the OS login credential available?
Thank you for all your great work. 
Quote 0 0
thiagoralves
The VM is configured to bridge one of your network adapters and get IP from your router. On VMWare the configuration is a little different. If you need access to the OS, the login : password is scadabr:scadabr. Root account is root:scadabr 
Quote 1 0
rwalford
Apparently there is a change to the default network interface naming convention.
using the login you provided and this link

https://www.itzgeek.com/how-tos/linux/debian/change-default-network-name-ens33-to-old-eth0-on-debian-9.html

I was able to get the adapter to register as eth0 instead of ens33 on the image running on vmware workstaiton.. The welcome prompt on the cli of ScadaBR still does not show the IP address so you have to log in and issue ifconfig to get the dhcp address. I am now able to access the ScadaBR UI and communicate with the OpenPLC on my Raspberry pi.
Thank you

Quote 0 0
thiagoralves
This is because on VirtualBox, virtual machines get the "enp" naming convention for their network adapters, where on VMWare they use the "ens" naming. Since the image was created for VirtualBox, all references to the network adapter use the "enp" naming, which means that network-wise it just doesn't work. To have it fully working, you need to edit the /etc/network/interfaces file and change the lines:

allow-hotplug enp0s3
iface enp0s3 inet dhcp

to

allow-hotplug ens33
iface ens33 inet dhcp

(or, instead of ens33, use whatever name your network adapter is using under VMWare, which now seems to be eth0 on your setup, right?)

You need to do the same thing with the /update_ issue.sh script. This script is executed during boot, gets the IP address of your adapter, and updates the issue message at the login prompt. Just change the name of the adapter on the 5th line (enp0s3) to be the name of your adapter. Reboot and now you should be getting the IP address at the login prompt.
Quote 0 0
jean-jean
Hi Thiago,

Thanks again for all this work.
I fallowed your guide but when I run the ScadaBR machine on VirtualBox, it starts and stops to a promp with nothing else.
I can't get an hand on it, even with a CTRL+C.

Do you have any idea?
Quote 0 0
thiagoralves
It should stop on a prompt with a welcome message like this:
c439d6_dcec5296ce434e4b87e3f68a4df13939_mv2.png 
To access it you need to open the browser on your machine and type in the address shown on the message (in this case http://192.168.137.49:8080/ScadaBR). You don't have to interact with this prompt to use ScadaBR. You will use it on your browser instead.
Quote 0 0
jean-jean
Thanks for your fast reply.
I just have a promp on a black screen.

Like if the virtual machine wasn't booting.
Do you know if it is necessary to have OpenPLC running on the network?
Quote 0 0
thiagoralves
You don't have to have anything running on the background. If you followed the instructions, once you start VirtualBox, you should see the VM on the list, click on that and then it should boot into the system. It looks like a computer booting up. If you're not seeing any of this, either your VM is corrupted or your VirtualBox installation is spoiled.
Quote 0 0
jean-jean
Solution found:
http://www.fixedbyvonnie.com/2014/11/virtualbox-showing-32-bit-guest-versions-64-bit-host-os/#.WxmSme6FNrS

Virtualisation wasn't enabel in the BIOS.

Now it works!
Thanks Thiago!

I'm looking forward to use the OpenPLC_V3!
May the force be with you!
Quote 0 0
thiagoralves
jean-jean wrote:

May the force be with you!

🙃
Quote 0 0