Skip to content

Commit 99ff034

Browse files
committed
Armin Update2
1 parent 22b08c7 commit 99ff034

5 files changed

Lines changed: 11 additions & 14 deletions

File tree

51.7 KB
Loading
112 KB
Loading

docs/usage/pro/frame/tutorials/day-1/first-connection/README.md

Lines changed: 11 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,6 @@ Now insert the power adapter's plug into that jack:
2626
| ---------------------------- | ------------------------ |
2727
| ![unplugged](unplugged.jpeg) | ![plugged](plugged.jpeg) |
2828

29-
30-
3129
Plug the wall plug of the power adapter into a wall outlet.
3230

3331
The FRAME includes a small embedded Raspberry Pi computer, which we'll refer to as the FRAME's *RPi*. It has a statistically-unique *machine name*, which is also written on a sticker on the FRAME:
@@ -44,8 +42,6 @@ Throughout this process, the indicator LEDs on the RPi will report what it's doi
4442

4543
Now that the FRAME has finished booting up, we're ready to connect your computer to the FRAME in order to access the FRAME's software.
4644

47-
48-
4945
The RPi makes a Wi-Fi network from its internal Wi-Fi module; we call this network the FRAME's *Wi-Fi hotspot*.
5046
The name of the Wi-Fi hotspot has the format `openuc2-{machine name}`, where `{machine name}` should be replaced with the RPi's machine name.
5147
For example, if the machine name is `separate-bath-30666`, then the Wi-Fi hotspot will be named `openuc2-separate-bath-30666`.
@@ -97,29 +93,30 @@ Open your computer's web browser and try navigating to each of address in the fo
9793

9894
3. [http://192.168.4.1](http://192.168.4.1)
9995

100-
The resulting web page is your FRAME's *landing page*, and it will look something like this:
96+
The resulting web page is your FRAME's *landing page*, and it will look something like this (in this case Machine name: long-comfort-3229):
97+
10198

102-
![landing page (top)](./landing-page-1.png)
103-
![landing page (continued)](./landing-page-2.png)
99+
![](C:\Users\ArminGrundmann\Documents\GitHub\docs\docs\usage\pro\frame\tutorials\day-1\first-connection\Landing%20page%20260709.png)
104100

105101
The landing page provides some information about your FRAME machine, and it's an easy way to access the apps running on your FRAME.
106102

103+
You have 2 main options to go from here: to the *Microscope Control* (ImSwitch GUI) to start working with the microscope or to *Machine Adiministration* to access advanced settings.
104+
105+
If you want to shortly checkout the *Machine Adiministration* page, it will look something like below.
106+
107+
![](C:\Users\ArminGrundmann\Documents\GitHub\docs\docs\usage\pro\frame\tutorials\day-1\first-connection\Machine%20Administration%20page.png)
108+
107109
:::tip
108110

109111
You can bookmark this page in your web browser for easy access, so that you don't have to type the address of this page whenever you want to open it.
110112

111113
:::
112114

113-
## Open ImSwitch
115+
## Open ImSwitch (Microscope Control)
114116

115117
Now that you have the landing page open in your web browser, we're ready to open *ImSwitch*, which is the app for operating the microscopy-related functions of your FRAME machine.
116118

117-
On the landing page, click on the "ImSwitch dashboard" link; it can be seen under the "Browser applications" section of the screenshot above (in the previous section).
118-
The link will open ImSwitch in a new tab, and you will see something like this:
119-
120-
![ImSwitch Live View](./imswitch-live-view.png)
121-
122-
This screenshot shows ImSwitch's "Live View" page, which is a general-purpose interface for previewing the FRAME's camera, adjusting its camera settings, and moving the FRAME's sample stage.
119+
On the landing page, click on the *Microscope Control* link. ImSwitch will open in a new tab.
123120

124121
## What's next
125122

Binary file not shown.
Binary file not shown.

0 commit comments

Comments
 (0)