Export translations
Перейти к:
навигация
,
поиск
Параметры
Группа
1-Wire
Allen Bradley DF1
API - Запись нового значения в регистр
API - Получение данных для графика
API - Получение данных для события
API - Получение данных о локальном времени
API - Получение лога регистров
API - Получение текущих значений регистров
API - Список блоков панелей
API - Список графиков
API - Список изображений
API - Список панелей
API - Список регистров
API - Список словарей
API - Список соединений
API - Список трендов
BACnet IP
Broadlink SP3S
Delta DVP
ModBus ASCII
ModBus RTU
Modbus RTU в виде custom protocol
ModBus TCP
Siemens PPI
Siemens S7 Communication
Test
Troubleshooting - Решение типовых проблем при работе в WebHMI
Аварии
Аннотация - функциональные возможности WebHMI
Битовые операции
Быстродействие при обмене данными
ВНИМАНИЕ! ДАННАЯ ВЕРСИЯ ВИКИ УСТАРЕЛА - см. docs.webhmi.com.ua
Внутренние регистры WebHMI
Демо-приложение для Android
Дополнительные СОМ порты
Доступ по ftp
Журнал регистров
Интеграция в другие системы
Использование MultiWan
Исторические графики
Как проверить уровень приема сигнала у 3G модема
Календарь
Назначение и применение
Настройка виртуального UART
Настройка связи с CDC-модемами на примере модема Huawei E3531
Настройка сетевых соединений
Обновление версии прошивки
Описание API
Описание внешних разъемов
Оптимизация производительности
Особенности работы с некоторыми модемами
Отладка сложных скриптов
Первое включение
Перевод на англ 2
Поддерживаемые протоколы
Подключение 3G модем ZTE K3806 Киевстар
Подключение WebHMI к Level2
Подключение внешних устройств
Подключение к Allen-Bradley MicroLogix 1200
Подключение к Kиевстар на примере модема ZTE MF100
Подключение к People.net
Подключение к S7-1200
Подключение к МТС Коннект
Подключение к ОВЕН160
Подключение к ПЛК с Codesys
Подключение к интернету через 3G модем
Полезные программы
Полезные советы
Пользовательские графики и тренды (Аналитика)
Пользовательские протоколы
Построение графиков в Level2
Пример доступа к данным из C/C++
Пример доступа к данным из Excel
Пример протокола ModBus ASCII
Пример протокола ModBus TCP
Примеры подключения к разным устройствам
Просмотр регистров по запросу
Работа с контроллером холодильного оборудования Danfoss AK-CC 550
Работа с регистрами
Рецепты
Сброс настроек
Синхронизация времени
Системные настройки и сервис
Скрипты
События
Соединения
Сравнение карт SD
Тренды
Удалённый сервисный доступ
Формирование отчетов
Функции управления соединениями
Функция Modbus/TCP сервер
Шаблоны дешбордов
Экраны
Язык
aa - Afar
ab - Abkhazian
ace - Achinese
ady - Adyghe
ady-cyrl - адыгабзэ
aeb - Tunisian Arabic
aeb-arab - تونسي
aeb-latn - Tûnsî
af - Afrikaans
ak - Akan
aln - Gheg Albanian
am - Amharic
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
av - Avaric
avk - Kotava
awa - Awadhi
ay - Aymara
az - Azerbaijani
azb - تۆرکجه
ba - Bashkir
bar - Bavarian
bbc - Batak Toba
bbc-latn - Batak Toba
bcc - Southern Balochi
bcl - Bikol Central
be - Belarusian
be-tarask - Belarusian (Taraškievica orthography)
bg - Bulgarian
bgn - Western Balochi
bho - Bhojpuri
bi - Bislama
bjn - Banjar
bm - Bambara
bn - Bengali
bo - Tibetan
bpy - Bishnupriya
bqi - Bakhtiari
br - Breton
brh - Brahui
bs - Bosnian
bto - Iriga Bicolano
bug - Buginese
bxr - буряад
ca - Catalan
cbk-zam - Chavacano de Zamboanga
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 Turkish (Cyrillic script)
crh-latn - Crimean Turkish (Latin script)
cs - Czech
csb - Kashubian
cu - Church Slavic
cv - Chuvash
cy - Welsh
da - Danish
de - German
de-at - Austrian German
de-ch - Swiss High German
de-formal - German (formal address)
diq - Zazaki
dsb - Lower Sorbian
dtp - Central Dusun
dty - डोटेली
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
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 - Simplified Gan script
gan-hant - Traditional Gan script
gd - Scottish Gaelic
gl - Galician
glk - Gilaki
gn - Guarani
gom - Goan Konkani
gom-deva - Goan Konkani (Devanagari script)
gom-latn - Goan Konkani (Latin script)
got - Gothic
grc - Ancient Greek
gsw - Swiss German
gu - Gujarati
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
hy - 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 - Адыгэбзэ
kg - Kongo
khw - Khowar
ki - Kikuyu
kiu - Kirmanjki
kj - Kuanyama
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 - 한국어 (조선)
koi - Komi-Permyak
kr - Kanuri
krc - Karachay-Balkar
kri - Krio
krj - Kinaray-a
ks - Kashmiri
ks-arab - Kashmiri (Arabic script)
ks-deva - Kashmiri (Devanagari script)
ksh - Colognian
ku - Kurdish
ku-arab - كوردي (عەرەبی)
ku-latn - Kurdish (Latin script)
kv - Komi
kw - Cornish
ky - Kyrgyz
la - Latin
lad - Ladino
lb - Luxembourgish
lbe - лакку
lez - Lezghian
lfn - Lingua Franca Nova
lg - Ganda
li - Limburgish
lij - Ligurian
liv - Livonian
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
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
mo - молдовеняскэ
mr - Marathi
mrj - Western Mari
ms - Malay
mt - Maltese
mus - Creek
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
niu - Niuean
nl - Dutch
nl-informal - Nederlands (informeel)
nn - Norwegian Nynorsk
nov - Novial
nrm - Nouormand
nso - Northern Sotho
nv - Navajo
ny - Nyanja
oc - Occitan
olo - Livvi-Karelian
om - Oromo
or - Oriya
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
qu - Quechua
qug - Chimborazo Highland Quichua
rgn - Romagnol
rif - Riffian
rm - Romansh
rmy - Romani
rn - Rundi
ro - Romanian
roa-tara - tarandíne
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 - Tašlḥiyt
shi-tfng - ⵜⴰⵛⵍⵃⵉⵜ
si - Sinhala
sk - Slovak
sl - Slovenian
sli - Lower Silesian
sm - Samoan
sma - Southern 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
su - Sundanese
sv - Swedish
sw - Swahili
szl - Silesian
ta - Tamil
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
tn - Tswana
to - Tongan
tokipona - Toki Pona
tpi - Tok Pisin
tr - Turkish
tru - Turoyo
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 - ўзбекча
uz-latn - oʻzbekcha
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
wo - Wolof
wuu - Wu Chinese
xal - Kalmyk
xh - Xhosa
xmf - Mingrelian
yi - Yiddish
yo - Yoruba
yue - Cantonese
za - Zhuang
zea - Zeelandic
zh - Chinese
zh-cn - Chinese (China)
zh-hans - Simplified Chinese
zh-hant - Traditional Chinese
zh-hk - Chinese (Hong Kong)
zh-mo - 中文(澳門)
zh-my - 中文(马来西亚)
zh-sg - Chinese (Singapore)
zh-tw - Chinese (Taiwan)
zu - Zulu
qqq - Message documentation
Format
Экспорт для оффлайнового перевод
Экспорт в родном формате
{{DISPLAYTITLE:System settings and maintenance}}<languages/> == System settings == <languages/> <br clear=all> System settings specify the performance parameters, the depth of data storage in logs and their idealization, as well as additional functions - ModBus / TCP server, WebHMI Cloud. [[Файл:Setting tab1.png|1024px|left]] <br> <br clear=all> :: '''Interface language''' - 4 options: UKR., RUS., ENG. and auto select. :: '''Communication interval''' - Specifies the period of data exchange with the connected devices (time of scanning devices or 'scan'). After this time, WEBHMI starts a cycle of continuous exchange with devices at their respective speeds with minimal delays between consecutive polls. A short interval increases the polling frequency, reduces the response when changing the register on the dashboard, and the 'response' of changes in the trends, but with a large number of interrogated data, they may not fit in the interval at the time, which will actually increase the scan, increase load on the system. This settings should be set reasonably. If you need to 'have time' to query a large amount of data for a second, first you need to increase the speed of communication with devices, use the priority of reading the registers in conjunction with the option 'strict scan', do not read the auxiliary registers unnecessarily (use the Read On Demand option for this). ::: The option '''Strict scan''' - this option allows to get a time-determined scan. If all registers fail to "fit in scan", high-priority registers should be given high priority in the register properties, and registers with normal priority should set individually longer polling time than the default interval. Then, after reading the high-priority registers, the remainder and the number of registers with normal priority will be subtracted in the remaining sequence before the scan ends. :: '''Dashboard refresh interval''' is the frequency of data update on the dashboard. Adjustable in steps of 50 ms. up to 5 sec. :: '''Trends refresh interval'''- the frequency of trend data update, possible values: ::* 50, 100, 200, 333, 500, 800 ms ::* 1, 1.5, 2, 5 sec. :: '''Log level''' - level of the system log detail, possible values: ::* Disable log - disabled; ::* Errors - errors only; ::* Info+Errors - errors and informing messages; ::* Debug+Info+Errors - previous plus debug info; ::* Trace+Debug+Info+Errors - previous with trace data; :: '''Communication log limit, MB''' - Max. size of the communication log, Mb; :: '''Keep data in log for '''- setting the depth of storage of the stored data (logs of registers, events, data of graphs) '''Battery operation mode''' - 3 scenarios for operation with external power off: off. immediately, wait 20 minutes, or work until the battery is completely discharged <br clear = all> '''MobBus server''' - when turned on, allows external client to poll the project register using Modbus/TCP protocol. (see [[Функция Modbus/TCP сервер| function description]]) <br> [[Файл:Modbus tab2.png | 1024 px]] <br clear = all> '''Level2''' - turning this option on allows integrating with level2 server [[Файл:L2 tab3.png |1024px | left]] <br clear = all> ::*API key - this key will be used for sending WebHMI data to level2 ::* The interval of sending the register current values of (Real-time registers values send interval) and collected data (Log data send interval) is adjusted in steps of 1 sec. up to 1 day. == Managing users == In WebHMI, there is a mechanism for managing users and their roles. On the new device, three roles are configured by default: ::'''Admin''' - can perform any actions in the project ::'''Operator''' - can use the ready project to change the values on the dashboard and access only to allowed pages of the project ::'''read-only user ''' - can only view the project running and one user with admin role: <br clear = all> <p> However, there may be more roles and users. Users start from the Configuration / Users menu, there is also a button for switching to the role editing menu.</p> [[Файл:Users list.png| 1024 px | left]]<br clear = all> [[ Файл:Roles list.png | 1024px | left]] <br clear = all> The user can specify a name, an entry password, a page after entering the interface: [[Файл:Users Edit.png | 1024px | left]] <br clear = all> <br clear = all> For each role, you can define valid actions for accessing parts of the project for viewing or editing. The following is an example of setting up a predefined role "Operator" <br> [[Файл:Role edit 1.png | 1024px|left]]<br clear = all> продолжение:<br> [[Файл:Role edit 2.png| 1024px | left]]<br clear = all> == Project backup and restore functions == <p> The menu item '''Save configuration (Setup / Backup & Restore)''' allows you to backup the project, restore it from the archive. To save the log, you can copy it from the SD card, or by logging into WEBHMI using the ftp protocol (with the same settings as for logging in [http://wiki.webhmi.com.ua/index.php/%D0%9D%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B0_%D1%81%D0%B5%D1%82%D0%B5%D0%B2%D1%8B%D1%85_%D1%81%D0%BE%D0%B5%D0%B4%D0%B8%D0%BD%D0%B5%D0%BD%D0%B8%D0%B9 network setup] ) and copying '''\log''' folder. In order to restore the data, you must also copy this folder back to the SD card (provided that databases structure are identical, see below and consult with supplier). [[Файл:Backup 1.png|1024px|left]]<br clear = all> The tab '''Restore''' - download a backup copy of the project. See the note for a description of the Backup function. [[Файл:Restore.png| 1024 px |left]]<br clear = all> == Maintenance == === Logs === Menu '''Configuration / Logs''' serves for viewing current logs: *Communication *Level2 exchange log *OS kernel log In the communication log messages are categorized (see System Settings). Below is a fragment of the log with the maximum level of detail. For example, string Feb 01 16:06:43.859: DEBUG: Scan done indicates the completion of the polling cycle of external devices (debug level). Strings Feb 01 16:06:44.278: TRACE: ModBus: Sending message, 01 03 00 00 00 0A C5 CD Feb 01 16:06:44.283: TRACE: UART: Sending data to port... Feb 01 16:06:44.349: TRACE: ModBus: Received message, 01 03 14 00 00 00 01 00 02 00 03 00 report the transfer of data to the serial port and show the actual contents of telegrams sent and received (trace level). [[Файл:Log screen.png|1024px]]<br> Basically, these logs are intended for for system diagnostics and for the user are of interest only in the case of debugging programs or other kind of problems- in this case, these logs should be sent to the seller's technical support. === Firmware upgrade === WebHMI is constantly evolving and improving - new opportunities are emerging, the old ones can be modified, some become unnecessary and go away, and the identified errors are also corrected. However, you must bear in mind that an existing project created in a version other than the WebHMI version where it is planned to be installed may not be fully compatible. As a rule, versions with a small difference in numbers in the last positions of the firmware version are compatible 100%, but with a very large version difference, partial compatibility is possible. For example, this was the case when switching from 1.9 to 1.10. Then Lua scripts were added and old visual scripts were removed because they were much less functional. Thus, after downloading the project version to 1.9 to a higher version, it is possible (if the project used scripts) to write scripts in Lua. Therefore, you should take this moment into account before updating. As already mentioned, the neighboring versions are usually 100% compatible, and although a warning is issued when trying to restore a project with an excellent version, you can disable this check by checking the 'Ignore check version' flag. <br> [[Файл:Restore_2.png | 1024px]]<br clear = all> If you have a replicated solution based on WebHMI and your project works well for a specific firmware version, then so to not waste time in the future to adapt an existing project to a newer firmware, you can simply use the same version in which the project was created. When updating the firmware, the current project is always erased. After the upgrade, the project needs to be restored from the previously saved backup. If you have questions about the compatibility of the firmware before upgrading, consult the supplier. To obtain the update key, you need to send an application to info@ webhmi.com.ua with information about the company, the current version of the project, the WebHMI serial number and the version number to which you want to update - (the latest or the specific version in order to preserve the compatibility of the project). '''Operation procedure for updating the firmware version''': * You need to make sure that WebHMI is connected to the Internet and there is a connection to the update server by sending an echo request to webhmicloud.com. You can do this from the network settings by going to the 'Diagnostics' menu item. The normal result of the command is shown below. To configure an Internet connection on WebHMI, see [[http://wiki.webhmi.com.ua/index.php/%D0%9D%D0%B0%D1%81%D1%82%D1%80%D0%BE%D0%B9%D0%BA%D0%B0_%D1%81%D0%B5%D1%82%D0%B5%D0%B2%D1%8B%D1%85_%D1%81%D0%BE%D0%B5%D0%B4%D0%B8%D0%BD%D0%B5%D0%BD%D0%B8%D0%B9 здесь]]. [[Файл:Ping.png|1024px]] <br clear = all> * You need to make sure that WebHMI has the correct date and time. If necessary, you need to synchronize them with your computer manually. [[Файл:Syncronization.png|1024px]] * In the Setup menu in the Backup & Restore menu, the Upgade Firmware tab, you must enter the update key received from the vendor (manufacturer) and click the Upgrade button [[Файл:FW upgd.png|1024px]] Immediately after the update, you must clear the browser cache to prevent problems with caching old files. Allows you to update the software version. To do this, it is necessary to obtain the upgrade key from the supplier. ATTENTION! All project data will be lost. === Reboot === Allows you to reboot WebHMI or make software shutdown.<br> [[Файл:Reboot.png|1024px]] === About === Page with device information (firmware version). <br> [[Файл:About.png | 1024 px]] === SD card usage === Contains summary information about the available space in the key folders of the memory card. Also here you can do performance test for your SD card. [[Файл:Disk_usage.png|1024px]]
Навигация
Персональные инструменты
русский
127.0.0.1
Обсуждение для этого IP-адреса
Войти
Пространства имён
Служебная страница
Варианты
Просмотры
Ещё
Поиск
Навигация
Заглавная страница
Свежие правки
Случайная статья
Справка
Инструменты
Спецстраницы
Версия для печати