lm-sensors
- Bug #418246 “it87 (sensors) module broken, needs automatic addin...” : Bugs : “linux” package : Ubuntu
- $ sudo modprobe -v it87
insmod /lib/modules/2.6.32-42-generic/kernel/drivers/hwmon/it87.ko FATAL: Error inserting it87 (/lib/modules/2.6.32-42-generic/kernel/drivers/hwmon/it87.ko): Device or resource busy
- $ sudo modprobe -v it87
SystemTap
Zabbix
Watt Checker
- ログ記録型ワットチェッカーを比較!TAP-TST10とF-PLUG、REX-BTWATTCH1のどれを選ぶ!?
- 仕様が公開されている F-PLUG115 BSCESFP0103 が良さそうだが、販売終了とのこと (F-PLUG 販売終了に関するご案内(PDF)
- 現在所持しているもの
- TAP-TST5
- TAP-TST10
TAP-TST10
- Arch Linux 4.1.6-1-ARCH
- $ pacaur -S python2-pyusb-git
- aur:python2-pyusb-git (python2-pyusbは0.4.3-7とバージョンが古い)
- $ sudo sh -c 'echo -n "0003:040B:2201.0004" > /sys/bus/hid/drivers/hid-generic/unbind '
- $ sudo sh -c 'echo -n "3-1:1.0" >/sys/bus/usb/drivers/usbhid/unbind'
- echo > unbind はこちらだけで良いかも。
- $ vim taptst10ctl.py
-
taptst10ctl.py
diff --git a/taptst10ctl.py b/taptst10ctl.py index 1207fef..f5e8724 100644
a b watts = [] 83 83 kWhs = [] 84 84 outep.write('\x02\x18\x0a') 85 85 while True: 86 data = dev.read(ENDPOINT, 17, intf,1000)86 data = dev.read(ENDPOINT, 17, 1000) 87 87 # dump raw data 88 88 #print(" ".join("{:02x}".format(x) for x in data)) 89 89
-
- $ sudo python2 taptst10ctl.py
No.,DateTime,Watt,kWh 1,2015/09/23 10:30,4.5,0.00 2,2015/09/23 10:40,41.5,0.00 3,2015/09/23 10:50,41.3,0.01 4,2015/09/23 11:00,40.3,0.02
bug?
- github:nonakap/taptst10ctl は消費電力が増えるとオーバーフローするのか値がおかしくなる模様
- 100W~ 程度の負荷下
- $ sudo python2 taptst10ctl.py
No.,DateTime,Watt,kWh 1,2015/09/23 11:00,40.0,0.01 2,2015/09/23 11:10,106.0,0.02 3,2015/09/23 11:20,3251.0,2.56 4,2015/09/23 11:30,3251.0,5.10 5,2015/09/23 11:40,3251.0,7.64
- 3251Wになってしまう
- $ sudo python2 taptst10ctl.py
- TAP-TST10 Watt Monitor USB Program (公式アプリ)
F-PLUG115
- F-PLUG(エフプラグ) - 電力、温度、湿度、照度を同時に測定して見える化する電力測定機器 : 富士通ビー・エス・シー
- F-PLUG メッセージ一覧 : 富士通ビー・エス・シー 本サイトではF-PLUG制御用メッセージに関する情報を提供いたします。
- Windows 10からユーティリティを用いて接続する場合、事前にファームウェアバージョン 1300 にアップデートが必要 http://www.fujitsu.com/jp/group/bsc/services/f-plug/downloads/
Linux
- github:goto2048/fplug_for_linux
- OBDNマガジン: (.tested) 富士通ビー・エス・シー F-PLUG (AX3)(A6)
- YANO's digital garage - fplug_for_linux
- $ sudo ./fpstatus -with /dev/rfcomm0
FP_WATT=21.4;FP_ILLUM=83;FP_TEMP=25.0;FP_HUMID=33;
- $ sudo ./fpstatus -with /dev/rfcomm0
- github:hasegaw/pyfplug
- pyfplug2.py
-
.py
old new 355 355 self.sfile.flush() 356 356 357 357 def test_fplug_dev(): 358 dev = FPlugDevice('/dev/rfcomm0', debug = True)358 dev = FPlugDevice('/dev/rfcomm0', debug = False) 359 359 # print "init:", dev.plug_init() 360 360 361 361
-
- $ sudo python2 pyfplug2.py
on: 1 off: 0 set_datetime: True TMP: 25.0 degree C HUM: 33 % ILL: 84 PWR: 21.4 W ACC: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 22] HIST PWR: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 22] HIST MISC: [(None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (None, None, None), (26.0, 33, 83), (26.0, 33, 82)]
- $ sudo python2 fplugctl init
- 履歴を初期化(ACC, HIST *が0に戻る)
- pyfplug2.py
- 機能面ではpyfplug、応答性ではfplug_for_linuxがよさそう(Cで書かれているので予想通りではあるが…)
- $ time for i in `seq 1 100`; do for opt in w i t h ; do sudo ./fpstatus -$opt /dev/rfcomm0 ; done; done
real 2m43.929s user 0m0.407s sys 0m0.187s
- $ time for i in `seq 1 100`; do for opt in t h i p ; do sudo python2 fplugctl get $opt ; done ; done
real 4m57.676s user 0m3.840s sys 0m0.817s
- $ time for i in `seq 1 100`; do for opt in w i t h ; do sudo ./fpstatus -$opt /dev/rfcomm0 ; done; done
- Raspberry PiにF-PLUGを2個繋いでみた ( UNIX ) - ロードバイクときどきiPad/Airなblog - Yahoo!ブログ
- Raspberry Pi で F-PLUG のログ収集 - Qiita
Smart Meter
Windows
- windows - Troubleshoot High CPU usage by the "System" process - Super User
To diag the CPU usage issues, you should use Event Tracing for Windows (ETW) to capture CPU Sampling data / Profile. To capture the data, install the Windows Performance Toolkit, which is part of the Windows SDK.
Last modified 7 years ago
Last modified on Mar 18, 2018 6:54:05 PM
Attachments (2)
- TAP-TST10.png (57.2 KB) - added by mitty 9 years ago.
- F-PLUG115-update.png (353.1 KB) - added by mitty 9 years ago.
Download all attachments as: .zip