Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:hw:02-neuron:01-first-steps:preparation-of-controller-hidden [2021/06/09 06:40]
lpolcerova
en:hw:02-neuron:01-first-steps:preparation-of-controller-hidden [2023/07/24 07:32] (current)
avsetula
Line 1: Line 1:
-====== Preparation and access to the controller ​====== +====== Preparation and access to the unit ====== 
-Before the first startup, it is necessary to insert an SD card with a flashed OS into the controller. \\+Before the first startup, it is necessary to insert an SD card with a flashed OS into the unit. \\
 ** Instructions for flashing the OS can be found [[en:​hw:​02-neuron:​image|on this link]].** ** Instructions for flashing the OS can be found [[en:​hw:​02-neuron:​image|on this link]].**
  
-After startup, the controller ​processes the uploaded program and the Mervis HMI website and other Mervis services communicating with the controller ​are also available. The device will startup fully a few seconds after the power supply is plugged in, it may take even longer for the first startup. The mode is physically indicated by PWR LED continuous emitting and RUN LED emitting with short flashes ([[en:​hw:​02-neuron:​led-indication#​pwr_is_on_and_run_blink_slowly|ukázka zde]] / [[en:​hw:​02-neuron:​led-indication#​controller_startup_simulator|simulace spuštění zde]]).+After startup, the unit processes the uploaded program and the Mervis HMI website and other Mervis services communicating with the unit are also available. The device will startup fully a few seconds after the power supply is plugged in, it may take even longer for the first startup. The mode is physically indicated by PWR LED continuous emitting and RUN LED emitting with short flashes ([[en:​hw:​02-neuron:​led-indication#​pwr_is_on_and_run_blink_slowly|demonstration here]] / [[en:​hw:​02-neuron:​led-indication#​unit_startup_simulator|startup simulator here]]).
  
-===== mDNS record ===== 
-For newer versions of the flashed OS, after connecting the controller in the network, an **mDNS** (multicast DNS) record is published, which is used to assign the device name to the IP address. 
  
-We can simply say that you do not need to know its IP address to connect to the required device, but you only need to know its name. In the case of Unipi Neuron, it is a combination of model marking and serial number separated by a dash in the form: **model-serialNumber**. You can find both information on the product label of the device.+{{page>​mdns-hidden}}
  
-<​html><​span class="​kbBlueText">​Examples of use:</​span></​html>​ \\ 
-This "​raw"​ form is suitable, for example, for SSH connections [[en:​files:​software:​tools:​putty-hidden|by PuTTY program]]. 
  
-<​code>​s103-sn1</​code>​ +===== First connection of the unit ===== 
- +Unipi Neuron ​unit size **S** must be powered by [[https://​www.unipi.technology/​power-supply-for-din-rail-24v-dc-0-63a-p18| 24 V⎓ power supply; 0.63 A]], sizes **M** and **L** must be powered by [[https://​www.unipi.technology/​power-supply-for-din-rail-24v-dc-1-5a-p19|24 V⎓ power supply; 1,5 A]]. To access the introductory HMI web page, it is necessary to connect to the unit from a computer or tablet, with any modern web browser. ​
-In order to connect to the Mervis web interface (so-called Mervis HMI) through a web browser, you need to complement this mDNS format by adding the **http:​⁄⁄** prefix, i.e.: +
- +
-<​code>​http://​s103-sn1</​code>​ +
- +
-Alternatively,​ in some browsers, add **.local** to the end of the string: +
- +
-<​code>​http://​s103-sn1.local</​code>​ +
- +
- +
-===== First connection of the controller ​===== +
-Unipi Neuron ​controller ​size **S** must be powered by [[https://​www.unipi.technology/​power-supply-for-din-rail-24v-dc-0-63a-p18| 24 V DC power supply; 0.63 A]], sizes **M** and **L** must be powered by [[https://​www.unipi.technology/​power-supply-for-din-rail-24v-dc-1-5a-p19|24 V DC power supply; 1,5 A]]. To access the introductory HMI web page, it is necessary to connect to the controller ​from a computer or tablet, with any modern web browser. ​+
  
 <WRAP center round info 90%> <WRAP center round info 90%>
-For the **programming** option, it is necessary to connect to the controller ​from a computer with the MS Windows ​operating system or higher with the Mervis IDE installed. The installation procedure is described [[#​installation_of_mervis|below]].+For the **programming** option, it is necessary to connect to the unit from a computer with the MS Windows ​10 operating system or higher with the Mervis IDE installed. The installation procedure is described [[#​installation_of_mervis|below]].
 </​WRAP>​ </​WRAP>​
  
Line 34: Line 19:
  
 ==== Connection via local network with DHCP server ==== ==== Connection via local network with DHCP server ====
-Despite its somewhat complex name, this approach is a simple and most commonly used variant. All you have to do is connect the controller ​to a computer network using an Ethernet cable and connect a computer or tablet (either via an Ethernet cable or Wi-Fi) to the same network. Your DHCP server (router or Wi-Fi router) on this network will automatically assign an IP address to both of them from the available range.+Despite its somewhat complex name, this approach is a simple and most commonly used variant. All you have to do is connect the unit to a computer network using an Ethernet cable and connect a computer or tablet (either via an Ethernet cable or Wi-Fi) to the same network. Your DHCP server (router or Wi-Fi router) on this network will automatically assign an IP address to both of them from the available range.
  
-The IP address of the controller ​can be found either from a DHCP server or by a suitable program to scan the network (such as [[en:​files:​software:​tools:​advanced-ip-scan-hidden|Advanced IP Scanner]]). **In most cases, however, an [[#​mdns_record|mDNS address variant]] will suffice.**+The IP address of the unit can be found either from a DHCP server or by a suitable program to scan the network (such as [[en:​files:​software:​tools:​advanced-ip-scan-hidden|Advanced IP Scanner]]). **In most cases, however, an [[#​mdns_record|mDNS address variant]] will suffice.**
  
 ;#; ;#;
Line 45: Line 30:
  
 ==== Direct connection ==== ==== Direct connection ====
-A direct connection requires the physical connection of the computer and controller ​with an Ethernet cable. Because this solution does not include a DHCP server, both the computer and the controller ​automatically assign itself a random IP address from the range 169.254.XXX.XXX.+A direct connection requires the physical connection of the computer and unit with an Ethernet cable. Because this solution does not include a DHCP server, both the computer and the unit automatically assign itself a random IP address from the range 169.254.XXX.XXX.
  
-You can find the IP address of the controller ​with a suitable program for scanning the network (such as [[en:​files:​software:​tools:​advanced-ip-scan-hidden|Advanced IP Scanner]]). **In most cases, however, an [[#​mdns_record|mDNS address variant]] will suffice.**+You can find the IP address of the unit with a suitable program for scanning the network (such as [[en:​files:​software:​tools:​advanced-ip-scan-hidden|Advanced IP Scanner]]). **In most cases, however, an [[#​mdns_record|mDNS address variant]] will suffice.**
  
 ;#; ;#;