Открыть главное меню
Главная
Случайная
Войти
Настройки
О Wiren Board
Отказ от ответственности
Найти
Экспорт переводов
Параметры
Группа
1-Wire
ADC
ADC:Измерение сопротивлений - технические детали
Backup power for Wiren Board devices
Bluetooth
BMP085
Buzzer
CAN
CMUX
CODESYS
Consumer IR
Controller hardware revisions
CryptodevATECCx08 Auth
DDM845R
Device Tree
DI
Disassembling the controller case
Documentation
Fast Modbus
First power-on Wiren Board 2.8
Gas sensor WB-MSGR
GPIO
Hardware Overview rev. 2.8-rus
Hardware Watchdog Disable
How To Build Linux Kernel
I/O Mapping Matrix
ILI9341
IMX233-OLinuXino-MICRO
Includes. Relay tuning
Inspektor SCADA
IntraHouse
IO modules
LAN9514
MediaWiki:Sitenotice
MOD-MRF24J40
Modbus
Modbus RTU/TCP Slave
Modbus-client
Modem-stretch
MQTT KNX V.0.1.x
NFC
Node-RED
Notification module
NRF24L01
Pin pull-up
Power Meter WB-MAP12H
Power Meter WB-MAP12H Measuring Parameters
Power Meter WB-MAP12H Measuring Registers
Power over Ethernet
Reg
Relay Module Modbus Management
RS-485
RS-485: Wiring and Connection
RS-485:Configuration via Web Interface
Rule Examples
SC16IS752
Sensors Modbus Management
Serial Port
SIM5300E
SIM68V
SIM900R
SNMP
SSH
SVG-Dashboards
TFT01-2.2SP
UART Communication Settings
UEXT-разъемы
Using Wiren Board with peripheral devices
Using Wiren Board with pulsed output devices
View controller files from your computer
Watchdog
WB 4: Errata
WB 5: Errata
WB 6: Errata
WB 7: Errata
WB AC rev. E1.0
WB AC rev. E2.0
WB Dimmers Modbus Registers Map
WB Modbus Devices Firmware Update
WB SH 3.5: Errata
WB SH 3.5: GPIO List
WB SH 3.5: UEXT2
WB-IMX233-CORE
WB-M1W2 1-Wire to Modbus Temperature Measurement Module
WB-MAI2-mini/CC 4-20mA Modbus Analog Inputs
WB-MAO4 0-10V Modbus Analog Outputs
WB-MCM16 Модуль счетных входов 16-канальный
WB-MCM8 Modbus Count Inputs
WB-MGE Modbus-Ethernet Interface Converter
WB-MIO Modbus Interface Converters
WB-MIO-Modbus-Registers
WB-MIR v1 - Modbus IR Remote Control
WB-MIR v2 - Modbus IR Remote Control
Wb-mqtt-db-cli
Wb-mqtt-serial driver
Wb-mqtt-serial templates
WB-MR3xV and WB-MR6xV Modbus Relay Modules
WB-MR6F Modbus Relay Module
WB-MR: Errata
WB-MRM2-mini Modbus Relay Modules
WB-MRPS6 Modbus Relay Modules
WB-MRWL3 Modbus Relay Modules
WB-MSW v.3 Modbus Sensor
WB-MSW v.4 Modbus Sensor
WB-MSWv 3 registers
WB-MSx Consumer IR Manual
WB-UPS Backup power supply for DIN rails
WB5 root password recovery
WB6 root password recovery
WBC-4G v.2
WBE-DI-DR-3
WBE-MICROSD Extension Module
WBE2-AO-10V-2 Analog Outputs 0-10V Extension Module
WBE2-DI-DR-3 Dry Contact Inputs Extension Module
WBE2-DO-OC-2 Open Collector Outputs Extension Module
WBE2-DO-R6C-1 Relay Extension Module
WBE2-DO-SSR-2 Dry Contact Outputs Extension Module
WBE2-I-1-WIRE 1-Wire Extension Module
WBE2-I-CAN-ISO CAN Extension Module
WBE2-I-KNX KNX Extension Module
WBE2-I-KNX: Errata
WBE2-I-RS232 RS-232 Extension Module
WBE2-I-RS485-ISO RS485 Extension Module
WBE2R-R-GPS GPS/GLONASS Extension Module
WBE2R-R-LORA v.1 Extension Module
WBE2R-R-ZIGBEE v.1 ZigBee Extension Module
WBE2S-MICROSD MicroSD Extension Module
Wbincludes:1-Wire Network
Wbincludes:1-Wire Warning
Wbincludes:Configuration MOD
Wbincludes:Configuration WBC
Wbincludes:GSM Modem Default Connection Parameters
Wbincludes:How to enter
Wbincludes:Installation MOD WBE2
Wbincludes:Installation MOD WBE2R
Wbincludes:Installing Software In Console
Wbincludes:Mount MOD
Wbincludes:Mount Relay
Wbincludes:Peripherals
Wbincludes:Relay Purpose2
Wbincludes:Revision
Wbincludes:Setup MOD
Wbincludes:WB-MSW v.3 Body Painting
Wbincludes:WB-MSW v.3 Functions
Wbincludes:WB-MSW v.4 Difference v.3
Wbincludes:WBC-4G Info
Wbincludes:WBC-4G Specifications
Wbincludes:WebUI Change Access Level
WBIO-AI-DCM-4 I/O Module
WBIO-AI-DV-12 Analog Inputs
WBIO-AI-DV-12/4-20mA Analog Inputs
WBIO-AO-10V-8 Analog Outputs 0-10V
WBIO-DI-DR-14 I/O Module
WBIO-DI-DR-16 I/O Module
WBIO-DI-DR-8 I/O Module
WBIO-DI-HVD-16 16-Channel 230V Detector Module
WBIO-DI-HVD-8 8-Channel 230V Detector Module
WBIO-DI-WD-14 Discrete Inputs
WBIO-DO-HS-8 Discrete Outputs
WBIO-DO-R10A-8 Relay Module
WBIO-DO-R10R-4 Relay Module For Roller Shutter
WBIO-DO-R1G-16 1A Relay Module
WBIO-DO-SSR-8 Discrete Outputs Dry Contact
WBMZ-BATTERY - модуль резервного питания
WBMZ2-BATTERY Backup Power Module
Wellpro
Wi-Fi Old
Wiren Board 2.8. Исходные файлы
Wiren Board 4: GPIO List
Wiren Board 4: Модуль расширения RS-232
Wiren Board 4:Аппаратная часть
Wiren Board 4:Первое включение
Wiren Board 5.1: GPIO List
Wiren Board 5.5: GPIO List
Wiren Board 5.8:Список GPIO
Wiren Board 5: Build an image to download in USB Mass-Storage mode
Wiren Board 5: GPIO List
Wiren Board 5: Recovery
Wiren Board 5: Модуль расширения 1-Wire
Wiren Board 5: Модуль расширения ADC
Wiren Board 5: Модуль расширения GPS/Glonass
Wiren Board 5: Модуль расширения RS-232 (WBE-I-RS232)
Wiren Board 5: Модуль расширения RS485-ISO
Wiren Board 5:Аппаратная часть
Wiren Board 5:Первое включение
Wiren Board 5:Схемотехника
Wiren Board 6.1: GPIO List
Wiren Board 6.2: Peripherals
Wiren Board 6.7: Peripherals
Wiren Board 6: Hardware
Wiren Board 6: WBE2R-R-GPS GPS/GLONASS Extension Module:NTPD PPS Setup
Wiren Board 6: Модуль расширения 433MHz (WBE2S-R-433MHZ)
Wiren Board Device Modbus Address
Wiren Board Devices Modbus Management
Wiren Board NETMON-1
Wiren Board NETMON-1: GPIO List
Wiren Board NETMON-2
Wiren Board Smart Home 3.5
Wiren Board Smart Home rev. 3.5
Wiren Board Software
Wiren Board Web Interface
Wiren Board Web Interface 1.0
Wiren Board: Extension Modules
Wirenboard6:InstallingOnTheRemoteSite
Z-Wave
Zabbix
Датчик SHT1x
Движок правил wb-rules 1.7
Доступ к порту RS-485 контроллера Wiren Board с компьютера
Как разрабатывать ПО для Wiren Board
Консоль
Модули расширения
Модуль ввода-вывода с TTL-уровнями (WBIO-DIO-TTL-8)
Модуль выходов "Открытый коллектор" WBE-DO-OС-2
Модуль выходов "сухой контакт" (оптореле) WBE-DO-SSR-2
Модуль наличия напряжения (WBIO-DI-LVD-16)
Модуль наличия напряжения (WBIO-DI-LVD-8)
Модуль расширения CAN (WBE-I-CAN-ISO)
Модуль расширения CAN (WBE-I-CAN-ISO) wb6
Модуль расширения DAC (WBE-AO-10V-2)
Модуль расширения KNX (WBE-I-KNX)
Модуль релейных выходов 3A (WBIO-DO-R3A-8)
Модуль релейных выходов WBE-DO-R6C-1
ПО МКА-3
Первое включение Wiren Board Smart Home
Периферийные устройства
Периферийные устройства с интерфейсом RS-485 серии WB-xxxx
Питание USB-портов
Получение точного времени через GPS/Glonass
Потеря файлов при обновлении ПО
Работа с GPIO
Сounters Pulsar
Сборка образа
Сборка образов прошивки
Создание microSD-карты с образом
Список GPIO
Стандартный образ ФС
Уникальные идентификаторы
Управление низковольтной нагрузкой
Устарело: низкоуровневая работа с ADC в Wiren Board 2, 3 и 4
Участник:EvgenyBoger/CT309-test
Участник:EvgenyBoger/test2
Участник:EvgenyBoger/testtrans
Участник:EvgenyBoger/testtrans2
Участник:EvgenyBoger/Wbincludes:Revision
Шаблон:Node-RED Installing plugin
Шаблон:Testtrans3
Язык
aa - Afar
ab - Abkhazian
abs - Ambonese Malay
ace - Achinese
ady - Adyghe
ady-cyrl - Adyghe (Cyrillic script)
aeb - Tunisian Arabic
aeb-arab - Tunisian Arabic (Arabic script)
aeb-latn - Tunisian Arabic (Latin script)
af - Afrikaans
ak - Akan
aln - Gheg Albanian
alt - Southern Altai
am - Amharic
ami - Amis
an - Aragonese
ang - Old English
anp - Angika
ar - Arabic
arc - Aramaic
arn - Mapuche
arq - Algerian Arabic
ary - Moroccan Arabic
arz - Egyptian Arabic
as - Assamese
ase - American Sign Language
ast - Asturian
atj - Atikamekw
av - Avaric
avk - Kotava
awa - Awadhi
ay - Aymara
az - Azerbaijani
azb - South Azerbaijani
ba - Bashkir
ban - Balinese
ban-bali - ᬩᬲᬩᬮᬶ
bar - Bavarian
bbc - Batak Toba
bbc-latn - Batak Toba (Latin script)
bcc - Southern Balochi
bci - wawle
bcl - Central Bikol
be - Belarusian
be-tarask - Belarusian (Taraškievica orthography)
bg - Bulgarian
bgn - Western Balochi
bh - Bhojpuri
bho - Bhojpuri
bi - Bislama
bjn - Banjar
bm - Bambara
bn - Bangla
bo - Tibetan
bpy - Bishnupriya
bqi - Bakhtiari
br - Breton
brh - Brahui
bs - Bosnian
btm - Batak Mandailing
bto - Iriga Bicolano
bug - Buginese
bxr - Russia Buriat
ca - Catalan
cbk-zam - Chavacano
cdo - Min Dong Chinese
ce - Chechen
ceb - Cebuano
ch - Chamorro
cho - Choctaw
chr - Cherokee
chy - Cheyenne
ckb - Central Kurdish
co - Corsican
cps - Capiznon
cr - Cree
crh - Crimean Turkish
crh-cyrl - Crimean Tatar (Cyrillic script)
crh-latn - Crimean Tatar (Latin script)
cs - Czech
csb - Kashubian
cu - Church Slavic
cv - Chuvash
cy - Welsh
da - Danish
dag - Dagbani
de - German
de-at - Austrian German
de-ch - Swiss High German
de-formal - German (formal address)
din - Dinka
diq - Zazaki
dsb - Lower Sorbian
dtp - Central Dusun
dty - Doteli
dv - Divehi
dz - Dzongkha
ee - Ewe
egl - Emilian
el - Greek
eml - Emiliano-Romagnolo
en - English
en-ca - Canadian English
en-gb - British English
eo - Esperanto
es - Spanish
es-419 - Latin American Spanish
es-formal - español (formal)
et - Estonian
eu - Basque
ext - Extremaduran
fa - Persian
ff - Fulah
fi - Finnish
fit - Tornedalen Finnish
fj - Fijian
fo - Faroese
fr - French
frc - Cajun French
frp - Arpitan
frr - Northern Frisian
fur - Friulian
fy - Western Frisian
ga - Irish
gag - Gagauz
gan - Gan Chinese
gan-hans - Gan (Simplified)
gan-hant - Gan (Traditional)
gcr - Guianan Creole
gd - Scottish Gaelic
gl - Galician
glk - Gilaki
gn - Guarani
gom - Goan Konkani
gom-deva - Goan Konkani (Devanagari script)
gom-latn - Goan Konkani (Latin script)
gor - Gorontalo
got - Gothic
grc - Ancient Greek
gsw - Swiss German
gu - Gujarati
guc - Wayuu
guw - gungbe
gv - Manx
ha - Hausa
hak - Hakka Chinese
haw - Hawaiian
he - Hebrew
hi - Hindi
hif - Fiji Hindi
hif-latn - Fiji Hindi (Latin script)
hil - Hiligaynon
ho - Hiri Motu
hr - Croatian
hrx - Hunsrik
hsb - Upper Sorbian
ht - Haitian Creole
hu - Hungarian
hu-formal - magyar (formal)
hy - Armenian
hyw - Western Armenian
hz - Herero
ia - Interlingua
id - Indonesian
ie - Interlingue
ig - Igbo
ii - Sichuan Yi
ik - Inupiaq
ike-cans - Eastern Canadian (Aboriginal syllabics)
ike-latn - Eastern Canadian (Latin script)
ilo - Iloko
inh - Ingush
io - Ido
is - Icelandic
it - Italian
iu - Inuktitut
ja - Japanese
jam - Jamaican Creole English
jbo - Lojban
jut - Jutish
jv - Javanese
ka - Georgian
kaa - Kara-Kalpak
kab - Kabyle
kbd - Kabardian
kbd-cyrl - Kabardian (Cyrillic script)
kbp - Kabiye
kcg - Tyap
kg - Kongo
khw - Khowar
ki - Kikuyu
kiu - Kirmanjki
kj - Kuanyama
kjp - Eastern Pwo
kk - Kazakh
kk-arab - Kazakh (Arabic script)
kk-cn - Kazakh (China)
kk-cyrl - Kazakh (Cyrillic script)
kk-kz - Kazakh (Kazakhstan)
kk-latn - Kazakh (Latin script)
kk-tr - Kazakh (Turkey)
kl - Kalaallisut
km - Khmer
kn - Kannada
ko - Korean
ko-kp - Korean (North Korea)
koi - Komi-Permyak
kr - Kanuri
krc - Karachay-Balkar
kri - Krio
krj - Kinaray-a
krl - Karelian
ks - Kashmiri
ks-arab - Kashmiri (Arabic script)
ks-deva - Kashmiri (Devanagari script)
ksh - Colognian
ku - Kurdish
ku-arab - Kurdish (Arabic script)
ku-latn - Kurdish (Latin script)
kum - Kumyk
kv - Komi
kw - Cornish
ky - Kyrgyz
la - Latin
lad - Ladino
lb - Luxembourgish
lbe - Lak
lez - Lezghian
lfn - Lingua Franca Nova
lg - Ganda
li - Limburgish
lij - Ligurian
liv - Livonian
lki - Laki
lld - Ladin
lmo - Lombard
ln - Lingala
lo - Lao
loz - Lozi
lrc - Northern Luri
lt - Lithuanian
ltg - Latgalian
lus - Mizo
luz - Southern Luri
lv - Latvian
lzh - Literary Chinese
lzz - Laz
mad - Madurese
mai - Maithili
map-bms - Basa Banyumasan
mdf - Moksha
mg - Malagasy
mh - Marshallese
mhr - Eastern Mari
mi - Maori
min - Minangkabau
mk - Macedonian
ml - Malayalam
mn - Mongolian
mni - Manipuri
mnw - Mon
mo - Moldovan
mr - Marathi
mrh - Mara
mrj - Western Mari
ms - Malay
ms-arab - بهاس ملايو
mt - Maltese
mus - Muscogee
mwl - Mirandese
my - Burmese
myv - Erzya
mzn - Mazanderani
na - Nauru
nah - Nāhuatl
nan - Min Nan Chinese
nap - Neapolitan
nb - Norwegian Bokmål
nds - Low German
nds-nl - Low Saxon
ne - Nepali
new - Newari
ng - Ndonga
nia - Nias
niu - Niuean
nl - Dutch
nl-informal - Nederlands (informeel)
nn - Norwegian Nynorsk
no - Norwegian
nov - Novial
nqo - N’Ko
nrm - Norman
nso - Northern Sotho
nv - Navajo
ny - Nyanja
nys - Nyungar
oc - Occitan
ojb - Ojibwemowin
olo - Livvi-Karelian
om - Oromo
or - Odia
os - Ossetic
pa - Punjabi
pag - Pangasinan
pam - Pampanga
pap - Papiamento
pcd - Picard
pdc - Pennsylvania German
pdt - Plautdietsch
pfl - Palatine German
pi - Pali
pih - Norfuk / Pitkern
pl - Polish
pms - Piedmontese
pnb - Western Punjabi
pnt - Pontic
prg - Prussian
ps - Pashto
pt - Portuguese
pt-br - Brazilian Portuguese
pwn - Paiwan
qu - Quechua
qug - Chimborazo Highland Quichua
rgn - Romagnol
rif - Riffian
rm - Romansh
rmc - Carpathian Romani
rmy - Vlax Romani
rn - Rundi
ro - Romanian
roa-tara - Tarantino
ru - Russian
rue - Rusyn
rup - Aromanian
ruq - Megleno-Romanian
ruq-cyrl - Megleno-Romanian (Cyrillic script)
ruq-latn - Megleno-Romanian (Latin script)
rw - Kinyarwanda
sa - Sanskrit
sah - Sakha
sat - Santali
sc - Sardinian
scn - Sicilian
sco - Scots
sd - Sindhi
sdc - Sassarese Sardinian
sdh - Southern Kurdish
se - Northern Sami
sei - Seri
ses - Koyraboro Senni
sg - Sango
sgs - Samogitian
sh - Serbo-Croatian
shi - Tachelhit
shi-latn - Tachelhit (Latin script)
shi-tfng - Tachelhit (Tifinagh script)
shn - Shan
shy - Shawiya
shy-latn - Shawiya (Latin script)
si - Sinhala
simple - Simple English
sjd - Kildin Sami
sje - Pite Sami
sk - Slovak
skr - Saraiki
skr-arab - Saraiki (Arabic script)
sl - Slovenian
sli - Lower Silesian
sm - Samoan
sma - Southern Sami
smn - Inari Sami
sn - Shona
so - Somali
sq - Albanian
sr - Serbian
sr-ec - Serbian (Cyrillic script)
sr-el - Serbian (Latin script)
srn - Sranan Tongo
ss - Swati
st - Southern Sotho
stq - Saterland Frisian
sty - себертатар
su - Sundanese
sv - Swedish
sw - Swahili
szl - Silesian
szy - Sakizaya
ta - Tamil
tay - Tayal
tcy - Tulu
te - Telugu
tet - Tetum
tg - Tajik
tg-cyrl - Tajik (Cyrillic script)
tg-latn - Tajik (Latin script)
th - Thai
ti - Tigrinya
tk - Turkmen
tl - Tagalog
tly - Talysh
tly-cyrl - толыши
tn - Tswana
to - Tongan
tpi - Tok Pisin
tr - Turkish
tru - Turoyo
trv - Taroko
ts - Tsonga
tt - Tatar
tt-cyrl - Tatar (Cyrillic script)
tt-latn - Tatar (Latin script)
tum - Tumbuka
tw - Twi
ty - Tahitian
tyv - Tuvinian
tzm - Central Atlas Tamazight
udm - Udmurt
ug - Uyghur
ug-arab - Uyghur (Arabic script)
ug-latn - Uyghur (Latin script)
uk - Ukrainian
ur - Urdu
uz - Uzbek
uz-cyrl - Uzbek (Cyrillic script)
uz-latn - Uzbek (Latin script)
ve - Venda
vec - Venetian
vep - Veps
vi - Vietnamese
vls - West Flemish
vmf - Main-Franconian
vo - Volapük
vot - Votic
vro - Võro
wa - Walloon
war - Waray
wls - Wallisian
wo - Wolof
wuu - Wu Chinese
xal - Kalmyk
xh - Xhosa
xmf - Mingrelian
xsy - Saisiyat
yi - Yiddish
yo - Yoruba
yue - Cantonese
za - Zhuang
zea - Zeelandic
zgh - Standard Moroccan Tamazight
zh - Chinese
zh-cn - Chinese (China)
zh-hans - Simplified Chinese
zh-hant - Traditional Chinese
zh-hk - Chinese (Hong Kong)
zh-mo - Chinese (Macau)
zh-my - Chinese (Malaysia)
zh-sg - Chinese (Singapore)
zh-tw - Chinese (Taiwan)
zu - Zulu
Формат
Экспорт для оффлайнового перевода
Экспорт в родном формате
Вывести
{{DISPLAYTITLE:WirenBoard6:InstallingOnTheRemoteSite}}<languages/> {{DISPLAYTITLE:Wiren Board 6: Installing On The Remote Site}} This article highlights the network aspects of professional installation of the controller in industrial and commercial facilities. == Choosing a network configuration controller == The Wiren Board 6 controllers come with a different set of network devices. It is necessary to understand in what conditions the controller will be operated and what equipment will be optimal. === Minimum equipment === Controllers Wiren Board 6 have two Ethernet-interfaces 100 Mbit/s (eth0, eth1) on board in any configuration. === Advanced features === Optionally, the controllers come with Wi-Fi interface (wlan0) (802.11 bgn 2.4 G), 3G modem (WCDMA/HSPA, GSM/GPRS/EDGE) or 2G modem (GPRS). With any of them you can connect the controller to the Internet, and with Ethernet and Wi-Fi — also connect to the local network. 3G-modem is implemented on SIMCom SIM5300E chip, 2G-modem is implemented on SIMCom SIM800 or Neoway M660A chips, Wi-Fi — on Realtek 8723BU chip. == Factory configuration of network devices == ===Ethernet=== In the factory configuration, both Ethernet interfaces and Wi-Fi and loopback are configured in the controller. The network settings file is <code>/etc/network/interfaces</code>. Interfaces eth0/1 have no fixed address and get Sammie settings via DHCP. ===Wi-Fi=== On Wi-Fi interface wlan0 by default is the open hotpoint with the fixed address 192.168.42.1, clients receive addresses on DHCP which are distributed by dnsmasq daemon in the range of <code>192.168.42.50 — 192.168.42.150</code>. The SSID of the wireless controller network is formed from the prefix “WirenBoard-” and the serial number of the controller printed on the side sticker. In a wireless network, the controller has not only an IP address, but also DNS aliases for easy connection, <code>wiren</code>, <code>wiren.local</code>, <code>wiren_board</code>, <code>wirenboard.local</code>, <code>wirenboard</code>. === GPRS === Cellular data connection is not enabled by default and requires configuration. The controller has slots for installation of SIM-cards, but currently the software is only supported first. Optionally, the controller is equipped with 3G or 2G-modems (modems are non-removable and soldered on the Board at the factory). ==== 3G-модем ==== The modem is represented in the system by two devices: <code>/dev/ttyGSM</code> (link to one of the console ports ttymxc), connected to the UART-interface of the modem chip, and a composite USB-device <code>/dev/ttyACM0-6</code>, used for communication <code>ttyACM0</code>. The limitations of the UART port do not allow to realize the full potential of data transfer rate in 3G networks (theoretically up to 7.2 Mbit/s for reception and up to 5.76 Mbps for transmission). The port ttyACM0 is limited only by the transmission speed of USB2.0 (theoretically, up to 280 Mbps). The presence of two interfaces allows you to simultaneously use the first device (<code>/dev/ttyGSM</code>) to send AT-commands (to know the level of the cellular signal, send SMS, USSD-balance request etc) through minicom or gammu programs, and the second is (<code>/dev/ttyACM0</code>) for network communication. hardware control in the controller is represented by turning on/off the modem through its PWRKEY input, the state of which is controlled by one of the GPIOs of the processor. For the user, the modem power management interface provides the command <code>wb-gsm</code> with the options on, off, reset, restart_if_broken. ==== 2G-modem ==== The maximum data transfer rate in GPRS is 85.6 kbit/s, which is clearly not enough to transfer large amounts of data. The GPRS channel can be used to access the command line interface (ssh) or to send SMS. 2G modems are represented in the system by one device, <code>/dev/ttyGSM</code>. Simultaneous transmission of data and AT commands in the 2G modem is not implemented. ==== GSM-antennas ==== The controller is optionally equipped with one of two GSM antennas: a remote one, on a 2.5 m cable, with a gain of 3.5 dB, or - a short pin antenna screwed directly onto the SMA(female)-controller connector. When mounting the controller in metal boxes, use an external antenna. Regular antennas of the controller provide communication in conditions of good reception. In difficult radio conditions, it is necessary to purchase antennas with high gain or directional antennas. Frequency range of 3G-antennas — 1900-2100 MHz, 2G — 900/1800 MHz. Antenna cable connector — SMA(male). == Network interface configuration == === Ethernet interface configuration === It is often necessary for the controller to have a permanent address on the local network. This is achieved either by configuring the DNCP server (binding the IP address to the MAC address of the network interface of the controller) or by explicitly specifying the IP address in the network settings. Let's take a closer look at how to set a fixed address on the Ethernet interface. For static address settings, specify the following configuration: <pre> auto eth0 iface eth0 inet static address 192.0.2.7 netmask 255.255.255.0 gateway 192.0.2.254 hostname Wirenboard </pre> By default, if the address is static, the DNS servers listed in the <code>/etc/resolv.conf</code> file are used, and there is a symbolic link to <code>/mnt/data/etc/resolv.conf</code>. You can add your DNS servers: <pre> nameserver 192.168.0.1 nameserver 8.8.8.8 nameservеr 8.8.4.4 </pre> These servers use the dnsmasq service, which serves local DNS queries on the controller. To understand what upstream server are used by dnsmasq at the moment, run the command <pre> service dnsmasq stop dnsmasq --no-daemon --log-queries ^C service dnsmasq start </pre> The dnsmasq program displays in the console which servers are used, for example: <pre> dnsmasq: using nameserver 192.168.0.1#53 dnsmasq: using nameserver 8.8.8.8#53 dnsmasq: using nameserver 8.8.4.4#53 </pre> === Wi-Fi Setting === The settings of the access point are determined by the daemon hostapd (settings file <code>/etc/hostapd.conf</code>). To connect to the controller via Wi-Fi over a secure channel, write to the end of the file<code>/etc/hostapd.conf</code> the following configuration: <pre> wpa=2 wpa_passphrase=your_password wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP CCMP rsn_pairwise=TKIP CCMP </pre> Restart hostapd: <code>/etc/init.d/hostapd restart</code>, after which connection to the controller via Wi-Fi will be possible only with the password'''your_password'''. An example of how to configure Wi_Fi adapter to connect to a local network can be found [[Wi-Fi/en|in our wiki]]. === PPP settings === The pppd daemon is pre-installed on the controller, which is used to create a connection to the provider's network via 3G/2G modem. The PPP daemon creates when you connect the network interface ppp (ppp0 is the default). In the factory configuration settings for the ppp0 port is commented out, and there is no connection with the mobile provider. In our [[GSM/GPRS/en|Wiki]] we recommend using the following settings for the ppp0 interface in the <code>/etc/network/interfaces</code>file: <pre> auto ppp0 iface ppp0 inet ppp provider mts #Restart modem if it's frozen pre-up wb-gsm restart_if_broken #Then wait for it to load and find the network. pre-up sleep 10 </pre> Even if the modem is in a hung or disconnected state, the <code>pre-up wb-gsm restart_if_broken</code> command will reboot the modem and make sure it is available before starting the connection. A ten-second delay (<code>pre-up sleep 10</code>) before connection is usually enough to establish a network connection from the first time. String <code>provider</code> makes <code>pppd</code> find the settings file for a specific provider in the directory <code>/etc/ppp/peers</code>, in this example it is the file <code>/etc/ppp/peers/mts</code>. For compatibility reasons, this file specifies that the modem device <code>/dev/ttyGSM</code>should be used as the modem device in the factory setting. If you have a 3G modem installed on your controller, replace it with a faster one <code>/dev/ttyACM0</code>. To ensure that the controller does not stop trying to communicate when the connection is lost, the options in the provider settings file <code>/etc/ppp/peers/</code> must be uncommented <pre> persist maxfail 0 </pre> The packet data Protocol parameters and connection numbers for each provider are stored in the /etc/chatscripts directory. In most cases, you do not have to change anything in these files. == PPP is for a primary and backup Internet access == The easiest way to provide access to the Internet, if ppp0 — the only WAN-interface. The ppp0 interface is configured as described above, and then, with the <code>ifup ppp0</code> command, an Internet connection is established through the network of the cellular operator. Difficulties begin when the controller is connected to Ethernet and has a default gateway in one network, and also connects to a cellular data network. In this configuration, we are faced with the following feature: the PPP Protocol provides a point-to-point connection and does not assume a default gateway. In the case of a PPP connection where there is no default gateway (for example, we have not connected an Ethernet cable), pppd will add the IP address of the ppp partner as the default gateway to the routing table in the system. If a default gateway is already specified, a new default gateway is not added to the routing table. And then when the main Ethernet channel falls, the Internet connection is lost, despite the active connection. In this case, you must add a second default gateway through the ppp0 interface. The metric of any new gateway must be different from the metrics available, so we explicitly specify the metric when creating a new default gateway. To ensure failover of connections we need to provide for any procedure for raising and fall of the interfaces. The task is to provide communication regardless of the order of raising the interfaces and switching when one of them crushes. The default gateway with metric 0 in the routing table is created for the eth0 interface, which we will consider to be the primary interface for Internet access. Set the default gateway via the ppp0 interface to 100 metric (or any metric other than 0). The daemon uses the <code>/etc/ppp/ip-up directory to execute commands after any ppp interface is initialized.d</code>. The name of the ppp interface is also passed to the script as command-line parameters (in our case, there is only one such interface — ppp0). Create the add_routes script in the <code>/etc/ppp/ip-up directory.d</code> and make it executable (<code>chmod +x /etc/ppp/ip-up.d/add_routes</code>): <pre> #!/bin/sh route del default dev ppp0 2>/dev/null route add default dev ppp0 metric 100 2>/dev/null </pre> The first command removes the default gateway, in case it was created with metric 0. The second adds a default gateway with a metric of 100 for the ppp0 interface. Therefore, we have two default gateways with different metrics: [[Special:MyLanguage/Файл:Two_def_gateways.png|||| ]] If one of them falls, the traffic will be transmitted through the other and Vice versa. Start ping 8.8.8.8 and then remove and insert the RJ-45 plug: [[Special:MyLanguage/Файл:Channel_switch.png|||| ]] Sometimes there is a problem with the availability of provider DNS servers. For all connections prescribe public servers from Google and OpenDNS. "'eth0:"' From <code>/etc/dhcp/dhclient.conf</code> remove the <code>domain-name-servers</code> parameter from the request parameter, and after the request parameter specify the open DNS servers Google and OpenDNS: <pre>prepend domain-name-servers 8.8.4.4, 8.8.8.8, 208.67.222.222, 208.67.220.220;</pre> "'ppp0:"' In the <code>/etc/ppp/ip-up directory.d</code> create a script (and give it execute permissions) that will add Google DNS servers and OpenDNS to the <code>resolv file.conf</code> when the interface is up. <pre> if [ ! -e /etc/resolv.conf ]; then : > /etc/resolv.conf fi #OpenDNS printf '%s\n%s\n' "nameserver 208.67.222.222" "$(cat /etc/resolv/conf)" >/etc/resolv.conf printf '%s\n%s\n' "nameserver 208.67.220.220" "$(cat /etc/resolv.conf)" >/etc/resolv.conf #Google DNS printf '%s\n%s\n' "nameserver 8.8.8.8" "$(cat /etc/resolv.conf)" >/etc/resolv.conf printf '%s\n%s\n' "nameserver 8.8.4.4" "$(cat /etc/resolv.conf)" >/etc/resolv.conf </pre> == VPN == For remote access to the controller we will use OpenVPN. It is assumed that the server is already present and configured, you must install and configure the client on the controller. To ensure greater reliability, two server processes are started on a server with 2 IP addresses, one of which listens on port 1194 TCP on IP1 and the other - on port 1194 UDP on IP2. (This is optional, you can use a single server process). On the controller, we enable 2 OpenVPN clients and explicitly set the route for IP2 via the <code>ppp0</code> interface for one of them. OpenVPN installation is standard, using <code>open-rsa</code>. To do this, install <code>openvpn</code> and <code>easy-rsa</code>on the controller: <pre>apt-get install openvpn easy-rsa</pre> Copy <pre>cp -R /usr/share/easy-rsa /etc/openvpn/</pre> Copy the CA certificate <code>ca.crt</code> to the controller in <code>/etc/openvpn/easy-rsa/keys</code> folder In the folder <code>/etc/openvpn/easy-rsa</code> create a subfolder <code>keys</code>: <pre>mkdir keys && chmod 600 keys && cd keys</pre> Create a certificate signing request (with the name corresponding to the serial number of the controller, in this case that's A7ZO7UCC): <pre> cd /etc/openvpn/easy-rsa/ source ./vars ln -s openssl-1.0.0.cnf openssl.cnf ./build-req A7ZO7UCC </pre> Copy the received request <code>A7ZO7UCC.csr</code> to the server in an arbitrary directory and sign it. <pre> cd /etc/openvpn/easy-rsa source ./vars ./sign-req /root/certs/A7ZO7UCC </pre> Signed <code>A7ZO7UCC certificate.crt</code> copy to the controller in the directory <code>/etc/openvpn/easy-rsa/keys</code>. On the server in the configuration file (<code>/etc/vpn/server.conf</code>) see which client-address match file is specified in the <code>ifconfig-pool-persist < /code> parameter and add the address for the client-controller from the network address range described in the <code>server</code> parameter of the configuration file to this file. For example, <pre> service openvpn stop mcedit /etc/openvpn/ipp.txt </pre> Add the line <code>A7ZO7UCC,10.8.0.48</code> <pre>service openvpn start</pre> For the second server instance, we perform the same operation with its configuration files, the IP addresses should be different, for example, add an entry <code>A7ZO7UCC,10.9.0.48</code> The configuration files for the client on the controller for the two connections will be stored in the <code>/etc/openvpn/client files.conf</code> and <code>/etc/openvpn/client1.conf</code>. Contents of the client configuration file: <pre> client dev tun proto udp remote vpn.mydomain.com 1194 resolv-retry infinite nobind persist-key persist-tun ca /etc/openvpn/easy-rsa/keys/ca.crt cert /etc/openvpn/easy-rsa/keys/A7ZO7UCC.crt key /etc/openvpn/easy-rsa/keys/A7ZO7UCC.key remote-cert-tls server verb 3 link-mtu 1542 keysize 128 #keysize 128 - for compatibility with existing clients </pre> In the configuration file of the second vpn connection, <code>CLIENT1.conf</code> replace <code>proto udp</code> with <code>proto tcp</code> and specify the second IP address of the server in the <code>remote</code>parameter. Startup of the OpenVPN service on the controller is enabled by the command: <pre>update-rc.d openvpn defaults</pre> Check server availability <code>ping 10.8.0.1</code> == AutoSSH == Another fallback controller connection will be based on the <code>AutoSSH</code>. The mechanism of work is as follows: SSH-connection from the controller to the server is established, and the ssh-port of the controller is forwarded to one of the free ports on the localhost server. Service аutossh ensures that the ssh connection is not broken, and in case of the gap restores it. Recovery is not instantaneous — for a while, the port used on the server's <code>localhost</code> is held by the <code>sshd</code>daemon. Install on the controller <code>apt-get install autossh</code>. Generate a key pair for the user <code>root</code>: <pre>ssh-keygen </pre> Password is empty. To maintain remote connections, create a user <code>remote</code> on the server with the shell <code>/bin/false</code>: <заранее>команду adduser --Home /для дома/дистанционный --оболочку /bin/false в удаленных и </pre> Here, in file <code>/home/remote/.ssh/authorized_keys</code> on the server, we add key created on the controller <code>/root/.ssh/id_rsa.pub</code> with the preamble <code>no-agent-forwarding,no-X11-forwarding,permitopen="localhost:62001" </code> this will provide additional security for the server when the controller is connected. Port 62001 is the port of the localhost server to which the ssh port of this controller will be redirected. The first time we connect from the controller to the server manually: <pre>ssh remote@vpn.mydomain.com </pre> On the controller, create a file <code>\etc\systemd\system\autossh.service</code> to run it <code>autossh</code> as a service: <pre> [Unit] Description=Keeps an ssh tunnel to remote host open After=network.target [Service] User=root # -p [PORT] # -l [user] # -M 0 --> no monitoring # -N Just open the connection and do nothing (not interactive) # LOCALPORT:IP_ON_EXAMPLE_COM:PORT_ON_EXAMPLE_COM ExecStart=/usr/bin/autossh -M 0 -N -o ServerAliveInterval=15 -o ServerAliveCountMax=5 -o ExitOnForwardFailure=yes -R 62001:127.0.0.1:22 -p 22 remote@vpn.mydomain.com #ExecStop=/usr/bin/killall -9 autossh RestartSec=5 Restart=always [Install] WantedBy=multi-user.target </pre> Add service to autorun on the controller <pre>systemctl enable autossh.service</pre> After starting the service, we can connect to the controller on the server using the command <pre>ssh 127.0.0.1 -p 62001</pre> == Data transfer from controller to the cloud == To send MQTT messages from the controller to the cloud service, the MQTT bridge is used, the configuration of which is configured on the controller in the file <code>\mnt\data\etc\mosquito\conf.d\bridge.conf</code> <pre> connection wb_devices_cloud.wb_A7ZO7UCC address cloud_server.com notifications true notification_topic /client/wb_A7ZO7UCC/bridge_status topic /devices/# both 2 "" /client/wb_A7ZO7UCC topic /config/# both 2 "" /client/wb_A7ZO7UCC topic /rpc/# both 2 "" /client/wb_A7ZO7UCC username wb_A7ZO7UCC password your_mqtt_cloud_password </pre> Then run the command <pre> service mosquitto restart </pre> If you want to transfer data to multiple servers at the same time, create multiple <code>connection</code>partitions. == Possible GPRS connection problems == There can be several possible reasons for the lack of GPRS connection. * The paid traffic limit has ended. * Low voltage, poor contact to the antenna. * SIM cards of some operators are designed only for 4G-network, 3G-connection to install them will not work. * Check if the SIM card is inserted correctly into the slot. * The SIM card may not be working. * Your data plan does not include packet data. Before you go to your personal account and call the provider, you can perform a number of simple checks. Run the command <pre>gammu networkinfo</pre> <pre> Network state : home network Network : 250 01 (MTS, Russian Federation), LAC 18A6, CID 796B11 Name in phone : "MTS RUS" Packet network state : home network Packet network : 250 01 (MTS, Russian Federation), LAC 18A6, CID 796B11 Name in phone : "MTS RUS" GPRS : attached </pre> It is important that the controller is connected to the packet data network <pre>(GPRS : attached)</pre> and GPRS connection is established. Then evaluate the signal strength in minicom with <code>AT+CSQ</code> You will get the result as <code>13.99</code> The first digit shows the signal strength: > 9 — satisfactory, > 14 — good, > 19 — excellent. Low and unstable CSQ values mean that the antenna is poorly positioned, carelessly connected, radio placement is unfavorable. If both checks are passed, but there is no connection, contact your provider (check in your personal account), you can check the SIM card in your smartphone.