FIXME **Diese Seite wurde noch nicht vollständig übersetzt. Bitte hilf bei der Übersetzung.**\\ //(diesen Absatz entfernen, wenn die Übersetzung abgeschlossen wurde)// ====== jump-start ====== Here I have put together some things to help you with the first start of **PiCQ**. The access data to PiCQ are as follows: Username: **pi** Password: **picq** //This applies to **ssh**, the **Web-UI** and **Samba**.// Address for the Web UI: ''http://picq'' Address for the guest page of the Web-UI: ''http://picq:1234'' ===== PiCQ's own W-LAN ===== Since version 1.29 PiCQ provides its own W-LAN (*). The following data are of interest for this purpose: * SSID: **PiCQ** This can be set in the menu since V 1.30. * Encryption: **WPA2** * WPA key: **1a-funkfeuer.de** This can be set in the menu since V 1.30. * IP address of the PiCQ in this network: **192.168.10.1** This can be set in the menu since V 1.30. * PiCQ **provides a DHCP server**, which automatically provides the registered clients with an address from this range. * PiCQ is also able to establish a connection via W-LAN to the router itself despite its own AP. (*2) * = //Raspberry Pi3 on its built-in card / Raspberry Pi2 with an optional USB Wifi card.// *2= //If the card supports AP mode. Unfortunately, not all USB WiFi sticks can support this mode, and unfortunately not all that support it are fast enough to switch between client mode and access point mode, so some dongles don't support access point mode.// ===== preliminary work ===== Since PiCQ is still in the **test phase**, **malfunctions cannot be excluded**. Therefore I suggest to install it on a separate SD card or to make at least one backup copy of your running gateway. ===== Create accounts ===== By popular request, I have developed PiCQ as a **dual client**. That means it provides //2 Gateways// on **one Raspberry**. Therefore you need **2 working accounts** with FRN at the beginning. So please create 2 working accounts with FRN first of all. Simply use the Windows client of Edwin (**WATCH OUT FOR THE RIGHT MONITOR SERVER!!!**), get the password and write down the data well. For security reasons, connect to a server of your choice once with each new account to see if the account works. Use **valid** e-mail addresses where you can be reached and **no one-time addresses!** Please also make sure that you can be reached at these addresses (//check your mailbox regularly//). On the one hand, this is mandatory (for operators of an automated, stationary land radio station) and on the other hand, I plan to have PiCQ send the text messages sent to the gateway via FRN to these addresses later on. Furthermore it gives the operators of the monitor servers the possibility to contact you in case of problems. **TIP:** When choosing your **callsign** and **QTH** information, please use as short but meaningful information as possible and refrain from using complete novels (//because for this is the "Description" field//). PiCQ can control an LCD display with I2C bus and output some information about it during operation. However, only one display with 20 characters per line is provided. If possible, select information that does not require more than 20 characters in total. Example: The callsign of my gateway: MZG-1 The location of my gateway: Besseringen The display shows: "MZG-1 Besseringen" (17 characters, everything fits on the display) ==== Specifying WiFi parameters via the SD card ==== ---- If you want to start PiCQ with a W-LAN connection right at the beginning (//not recommended//), you can't enter it via the Web-UI yet. You can enter this configuration via the SD card. For this you create a file called "**wpa_supplicant.conf**" with the following content in the main path of the SD card (//Windows accessible "FAT" partition//): ---- ''# Datei wpa_supplicant.conf in der Boot-Partition (Raspbian Stretch)'' ''country=DE #omit if US'' ''ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev'' ''update_config=1'' ''network={'' '' ssid="wlan-bezeichnung"'' '' psk="passwort"'' '' key_mgmt=WPA-PSK'' ''}'' ---- //Please replace the "wlan-bezeichnung" and "passwort" with your data.// ===== Samba ===== PiCQ is dancing samba now. -No, now fun aside. I have moved the location for the sound files for the receipt tones from the Windows accessible partition of the card back to the Linux partition, because I find it better there. To give you easy access to the files without having to fiddle with FTP programs, I installed the so called Samba server. This now provides you with Windows shares that most operating systems can access. Workgroup: **WORKGROUP** Computer name : **PICQ** network share : **SOUNDS** network share2 : **ACTION** A typical Windows call now looks like this: **\\picq\sounds** or **\\IP-ADDRESS\sounds** Calling the shares under Windows 10: {{ :einfuehrung:freigaben_10.png?400 |}} Calling the shares under Windows XP {{ :einfuehrung:freigaben_xp.png?400 |}} ===== Action-Skripts ===== Also a completely new function for PiCQ are **Action-Scripts**. With them you will get the possibility to execute different commands through PiCQ later on. With the introduction of this simple interface even complicated processes can be triggered. NOTHING happens by itself, but needs your help. Although PiCQ listens to a "//magic spell//",but it does nothing until you have uploaded the appropriate action script. (4 Eyes Safety) The share "**action**" is responsible for the action scripts. It contains a dummy file named "**remote.sh**". You are not allowed to remove or change this file **without consulting me**, because this will cause an error in the Python parser, which spams a log file full with time. ====== Download ====== The [[en:einfuehrung:download|Download]] is now available.