evok not working

[Juergen]

Hi all,
I have installed the Image Unipian-Neuron-OS-2018-92-26 to test th Modbus-TCP

After Startup I try to connect to the Neuron M10x with a browser

I can't see the Inputs and Outputs

Must I do some configuration steps ?

[TomasKnot]

You may need to power-cycle your device first, as it tries to update the device firmware on first boot.

[Juergen]

Hi Thomas
my next attempt as follows.

1. load the Image from 2018-03-07
2. boot neuron, and wait until the run-led is blinking
3. reboot Neuron
4. connect from pc to evok Homepage.
5. same result as in my first post

I did the test with a one yoer old M10x and with a brandnew S103
same result.

Is there a possibility to check that the Firmwareupdate was ok.

best regards Jürgen

[TomasKnot]

I am sorry for the issues you are having. We should be more clear about the flashing procedure. Unfortunately it's the case that the run led starts blinking more rapidly while the flashing is going on, rather than the opposite; and it may take up to two minutes to finish.

If you are able to connect to it via ssh/putty, you can run

"sudo dmesg | grep neuronspi"

which should tell you the information that the driver receives on boot.

[Juergen]

Hi Thomas,

I found the following lines

3.958394] neuronspi: loading out-of-tree module taints kernel.

[ 4.000911] NEURONSPI: Neuronspi Probe Started
[ 4.042699] NEURONSPI: Probe did not detect a valid Neuron device on CS 3
[ 4.042750] neuronspi: probe of spi0.3 failed with error -5
[ 4.043222] NEURONSPI: Neuronspi Probe Started
[ 4.051528] NEURONSPI: Probe did not detect a valid Neuron device on CS 2
[ 4.051582] neuronspi: probe of spi0.2 failed with error -5
[ 4.052068] NEURONSPI: Neuronspi Probe Started
[ 4.052965] at24 1-0057: 128 byte 24c01 EEPROM, writable, 1 bytes/write
[ 4.061926] NEURONSPI: Probe detected Neuron Board 0 v5.6 on CS 1, Uart count: 1 - reg1000: 506, reg1001: 404, reg1002: 311, reg1003: 10, reg1004: 10
[ 4.061941] NEURONSPI: Neuron device on CS 1 uses SPI communication freq. 12000000 Mhz
[ 4.061946] NEURONSPI: LED model detected at CS: 1
[ 4.063726] NEURONSPI: Added UART port 0
[ 4.081361] NEURONSPI: SPI Driver Registered, Major Version: Master Version 1.0:20:12:2017

I'm waiting 10 Minutes the I do the reboot.

No difference, same problem as reported first

Jürgen

[Juergen]

Hi Thomas,

I found on UNIPI-Homepage a new image 2018-03-09

again: evok not working

The i stopped evak and start it again manually:

attached the log

Jürgen

---

pi@S103-sn291:~ $ sudo systemctl stop evok
pi@S103-sn291:~ $ sudo python (opt/evok/evok.py
-bash: syntax error near unexpected token `('
pi@S103-sn291:~ $ sudo python /opt/evok/evok.py
[I 180310 13:46:21 config:63] eprom: UniPi Neuron S103 version: 1.0 serial: 0x123
[I 180310 13:46:21 evok:1628] Starting using config file /etc/evok.conf
[I 180310 13:46:21 config:75] YAML Definition loaded: L20x.yaml, type: 3, definition count 0
[I 180310 13:46:21 config:75] YAML Definition loaded: M30x.yaml, type: 3, definition count 1
[I 180310 13:46:22 config:75] YAML Definition loaded: L50x.yaml, type: 3, definition count 2
[I 180310 13:46:22 config:75] YAML Definition loaded: S10x.yaml, type: 3, definition count 3
[I 180310 13:46:22 config:75] YAML Definition loaded: xS40.yaml, type: 3, definition count 4
[I 180310 13:46:22 config:75] YAML Definition loaded: M10x.yaml, type: 3, definition count 5
[I 180310 13:46:22 config:75] YAML Definition loaded: L30x.yaml, type: 3, definition count 6
[I 180310 13:46:23 config:75] YAML Definition loaded: M50x.yaml, type: 3, definition count 7
[I 180310 13:46:23 config:75] YAML Definition loaded: L51x.yaml, type: 3, definition count 8
[I 180310 13:46:23 config:75] YAML Definition loaded: xS30.yaml, type: 3, definition count 9
[I 180310 13:46:23 config:75] YAML Definition loaded: M40x.yaml, type: 3, definition count 10
[I 180310 13:46:23 config:75] YAML Definition loaded: M20x.yaml, type: 3, definition count 11
[I 180310 13:46:23 config:75] YAML Definition loaded: CUSTOM MODBUS DEVICE.yaml, type: 3, definition count 12
[I 180310 13:46:24 config:75] YAML Definition loaded: L40x.yaml, type: 3, definition count 13
[I 180310 13:46:24 config:75] YAML Definition loaded: xS10.yaml, type: 3, definition count 14
[I 180310 13:46:24 config:75] YAML Definition loaded: xS50.yaml, type: 3, definition count 15
[I 180310 13:46:24 config:75] YAML Definition loaded: evok-alias.yaml, type: 2, definition count 0
[I 180310 13:46:24 evok:1692] HTTP server listening on port: 8080
[I 180310 13:46:24 modbusclient_tornado:122] SPI client started
[I 180310 13:46:24 neuron:157] Reading SPI boards
[I 180310 13:46:24 neuron:172] No board on SPI 1
[I 180310 13:46:24 neuron:172] No board on SPI 2
[D 180310 13:46:24 owclient:377] Entering 1wire loop
[I 180310 13:46:24 neuron:172] No board on SPI 3
[E 180310 13:46:24 neuron:211] 'NoneType' object has no attribute 'do_scan'
Traceback (most recent call last):
File "/opt/evok/neuron.py", line 209, in scan_boards
yield self.modbus_cache_map.do_scan()
AttributeError: 'NoneType' object has no attribute 'do_scan'
[E 180310 13:46:25 neuron:211] 'NoneType' object has no attribute 'do_scan'
Traceback (most recent call last):
File "/opt/evok/neuron.py", line 209, in scan_boards
yield self.modbus_cache_map.do_scan()
AttributeError: 'NoneType' object has no attribute 'do_scan'

[tomas_hora]

@Juergen The FW update is done automatically from the image. If you booted from the new image, the FW starts to updated and evok cannot communicate with the HW which ends up with AttirbuteError: 'NoneType' object has no attribute 'do_scan'. But the FW update is processing in the background. You should wait 2minutes and then power cycle the device. Then evok should work ok.

If not, please send the output of "sudo dmesg | grep neuronspi" and immediately after the log of evok again.

[Juergen]

Hi Thomas,

I spent a lot of hours at sunday to do some test with 3 different NEURONs.

Attached the logs.

On all boxes it is the same error.
Did you test it in your lab?

==================== before starting evok =========================

[ 4.049533] neuronspi: loading out-of-tree module taints kernel.
[ 4.051444] NEURONSPI: Neuronspi Probe Started
[ 4.073184] NEURONSPI: Probe did not detect a valid Neuron device on CS 3
[ 4.073293] neuronspi: probe of spi0.3 failed with error -5
[ 4.073975] NEURONSPI: Neuronspi Probe Started
[ 4.076877] NEURONSPI: Probe did not detect a valid Neuron device on CS 2
[ 4.076926] neuronspi: probe of spi0.2 failed with error -5
[ 4.077432] NEURONSPI: Neuronspi Probe Started
[ 4.081189] NEURONSPI: Probe detected Neuron Board 0 v5.9 on CS 1, Uart count: 1 - reg1000: 509, reg1001: 404, reg1002: 311, reg1003: 10, reg1004: 10
[ 4.081203] NEURONSPI: Neuron device on CS 1 uses SPI communication freq. 12000000 Mhz
[ 4.081207] NEURONSPI: LED model detected at CS: 1
[ 4.083188] NEURONSPI: Added UART port 0
[ 4.093548] brcmfmac: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[ 4.100572] NEURONSPI: SPI Driver Registered, Major Version: Master Version 1.0:20:12:2017
[ 4.192339] at24 1-0057: 128 byte 24c01 EEPROM, writable, 1 bytes/write
[ 4.203374] rtc-ds1307 1-006f: rtc core: registered mcp7941x as rtc0
[ 4.203409] rtc-ds1307 1-006f: 64 bytes nvram
[ 5.488765] Adding 102396k swap on /var/swap. Priority:-1 extents:1 across:102396k SSFS
[ 5.518603] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 5.518616] brcmfmac: power management disabled
[ 5.612027] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 5.612245] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.126774] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 7.127538] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E

==================== starting evok =========================

pi@S103-sn291:~ $ sudo python /opt/evok/evok.py
[I 180312 13:09:52 config:63] eprom: UniPi Neuron S103 version: 1.0 serial: 0x123
[I 180312 13:09:52 evok:1628] Starting using config file /etc/evok.conf
[I 180312 13:09:52 config:75] YAML Definition loaded: L20x.yaml, type: 3, definition count 0
[I 180312 13:09:52 config:75] YAML Definition loaded: M30x.yaml, type: 3, definition count 1
[I 180312 13:09:53 config:75] YAML Definition loaded: L50x.yaml, type: 3, definition count 2
[I 180312 13:09:53 config:75] YAML Definition loaded: S10x.yaml, type: 3, definition count 3
[I 180312 13:09:53 config:75] YAML Definition loaded: xS40.yaml, type: 3, definition count 4
[I 180312 13:09:53 config:75] YAML Definition loaded: M10x.yaml, type: 3, definition count 5
[I 180312 13:09:53 config:75] YAML Definition loaded: L30x.yaml, type: 3, definition count 6
[I 180312 13:09:53 config:75] YAML Definition loaded: M50x.yaml, type: 3, definition count 7
[I 180312 13:09:54 config:75] YAML Definition loaded: L51x.yaml, type: 3, definition count 8
[I 180312 13:09:54 config:75] YAML Definition loaded: xS30.yaml, type: 3, definition count 9
[I 180312 13:09:54 config:75] YAML Definition loaded: M40x.yaml, type: 3, definition count 10
[I 180312 13:09:54 config:75] YAML Definition loaded: M20x.yaml, type: 3, definition count 11
[I 180312 13:09:54 config:75] YAML Definition loaded: CUSTOM MODBUS DEVICE.yaml, type: 3, definition count 12
[I 180312 13:09:54 config:75] YAML Definition loaded: L40x.yaml, type: 3, definition count 13
[I 180312 13:09:55 config:75] YAML Definition loaded: xS10.yaml, type: 3, definition count 14
[I 180312 13:09:55 config:75] YAML Definition loaded: xS50.yaml, type: 3, definition count 15
[I 180312 13:09:55 config:75] YAML Definition loaded: evok-alias.yaml, type: 2, definition count 0
[I 180312 13:09:55 evok:1692] HTTP server listening on port: 8080
[I 180312 13:09:55 modbusclient_tornado:122] SPI client started
[I 180312 13:09:55 neuron:157] Reading SPI boards
[D 180312 13:09:55 owclient:377] Entering 1wire loop
[I 180312 13:09:55 neuron:172] No board on SPI 2
[I 180312 13:09:55 neuron:172] No board on SPI 3

==================== after starting evok =========================
[ 3.969623] usbcore: registered new interface driver brcmfmac
[ 4.049533] neuronspi: loading out-of-tree module taints kernel.
[ 4.051444] NEURONSPI: Neuronspi Probe Started
[ 4.073184] NEURONSPI: Probe did not detect a valid Neuron device on CS 3
[ 4.073293] neuronspi: probe of spi0.3 failed with error -5
[ 4.073975] NEURONSPI: Neuronspi Probe Started
[ 4.076877] NEURONSPI: Probe did not detect a valid Neuron device on CS 2
[ 4.076926] neuronspi: probe of spi0.2 failed with error -5
[ 4.077432] NEURONSPI: Neuronspi Probe Started
[ 4.081189] NEURONSPI: Probe detected Neuron Board 0 v5.9 on CS 1, Uart count: 1 - reg1000: 509, reg1001: 404, reg1002: 311, reg1003: 10, reg1004: 10
[ 4.081203] NEURONSPI: Neuron device on CS 1 uses SPI communication freq. 12000000 Mhz
[ 4.081207] NEURONSPI: LED model detected at CS: 1
[ 4.083188] NEURONSPI: Added UART port 0
[ 4.093548] brcmfmac: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[ 4.100572] NEURONSPI: SPI Driver Registered, Major Version: Master Version 1.0:20:12:2017
[ 4.192339] at24 1-0057: 128 byte 24c01 EEPROM, writable, 1 bytes/write
[ 4.203374] rtc-ds1307 1-006f: rtc core: registered mcp7941x as rtc0
[ 4.203409] rtc-ds1307 1-006f: 64 bytes nvram
[ 5.488765] Adding 102396k swap on /var/swap. Priority:-1 extents:1 across:102396k SSFS

[tomas_hora]

@Juergen The end of the ==================== starting evok ========================= is missing... Could you paste it all?

[TomasKnot]

Could you try the web interface again after starting EVOK manually? It looks like it should work now from the log you've posted here, as the

[I 180312 13:09:55 neuron:172] No board on SPI 2
[I 180312 13:09:55 neuron:172] No board on SPI 3

messages are normal on the S-sized models.

If not there may be some other issue, e.g. with NGINX port forwarding or something else.

[Juergen]

Hi Thomas,

after boot I stopped evok and start it again manually.
pi@S103-sn291:/opt/evok $ sudo python evok.py
[I 180314 17:15:28 config:63] eprom: UniPi Neuron S103 version: 1.0 serial: 0x123
[I 180314 17:15:28 evok:1628] Starting using config file /etc/evok.conf
[I 180314 17:15:29 config:75] YAML Definition loaded: L20x.yaml, type: 3, definition count 0
[I 180314 17:15:29 config:75] YAML Definition loaded: M30x.yaml, type: 3, definition count 1
[I 180314 17:15:29 config:75] YAML Definition loaded: L50x.yaml, type: 3, definition count 2
[I 180314 17:15:29 config:75] YAML Definition loaded: S10x.yaml, type: 3, definition count 3
[I 180314 17:15:29 config:75] YAML Definition loaded: xS40.yaml, type: 3, definition count 4
[I 180314 17:15:29 config:75] YAML Definition loaded: M10x.yaml, type: 3, definition count 5
[I 180314 17:15:30 config:75] YAML Definition loaded: L30x.yaml, type: 3, definition count 6
[I 180314 17:15:30 config:75] YAML Definition loaded: M50x.yaml, type: 3, definition count 7
[I 180314 17:15:30 config:75] YAML Definition loaded: L51x.yaml, type: 3, definition count 8
[I 180314 17:15:30 config:75] YAML Definition loaded: xS30.yaml, type: 3, definition count 9
[I 180314 17:15:30 config:75] YAML Definition loaded: M40x.yaml, type: 3, definition count 10
[I 180314 17:15:31 config:75] YAML Definition loaded: M20x.yaml, type: 3, definition count 11
[I 180314 17:15:31 config:75] YAML Definition loaded: CUSTOM MODBUS DEVICE.yaml, type: 3, definition count 12
[I 180314 17:15:31 config:75] YAML Definition loaded: L40x.yaml, type: 3, definition count 13
[I 180314 17:15:31 config:75] YAML Definition loaded: xS10.yaml, type: 3, definition count 14
[I 180314 17:15:31 config:75] YAML Definition loaded: xS50.yaml, type: 3, definition count 15
[I 180314 17:15:31 config:75] YAML Definition loaded: evok-alias.yaml, type: 2, definition count 0
[I 180314 17:15:31 evok:1692] HTTP server listening on port: 8080
[I 180314 17:15:31 modbusclient_tornado:122] SPI client started
[I 180314 17:15:31 neuron:157] Reading SPI boards
[D 180314 17:15:31 owclient:377] Entering 1wire loop
[I 180314 17:15:31 neuron:172] No board on SPI 2
[I 180314 17:15:31 neuron:172] No board on SPI 3

Then I try to connect with a browser bolded text http://192.168.200.188, the Control Panel is loaded,
without any Outputs or Inputs as described in my first post.

But if I try to connect with port 8080: bolded texthttp://192.168.200.188:8080
I get this message.

[W 180314 17:15:42 web:2063] 404 GET / (192.168.200.105) 5.97ms

Which serverprocess is listening to port 8080 ?

[TomasKnot]

The web interface runs on port 80, while EVOK itself runs on 8080 (by default). Do you still have the EVOK process running in the background? It should show requests from the web interface, which are routed on the controller itself through port 80 to port 8080. These requests happen whenever the control interface is loaded or when a tab is changed in it.

If there are no requests displayed when running EVOK manually it is possible that the requests are being blocked somehow, or that the web interface is asking a wrong port. The port setting is in /etc/evok-nginx.conf; if you could post the contents here as well we can see if there's anything wrong.

[Juergen]

Hi Thomas

attached the evok-nginx.conf, which is from your Image, i did no modifications

server {
listen 80 default_server;
server_name _;

#ssl on;
#ssl_certificate      /etc/nginx/democert.pem;
#ssl_certificate_key  /etc/nginx/democert.key;

access_log  /var/log/evok.access.log;
root /var/www/evok;

location / {
    index index.html;	    
}

location /ws {
	proxy_pass http://localhost:8080;
	proxy_set_header Host $host:$server_port;
	proxy_http_version 1.1;
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header Connection "upgrade";
	proxy_buffering off;
	proxy_cache off;
	#send_timeout 120;
	proxy_read_timeout 180;
	#proxy_set_header X-Real-IP $remote_addr;
}

location /rest {
	proxy_pass http://localhost:8080;
	proxy_set_header Host      $host:$server_port;
	#proxy_set_header X-Real-IP $remote_addr;
}

location /json {
	proxy_pass http://localhost:8080;
	proxy_set_header Host      $host:$server_port;
	#proxy_set_header X-Real-IP $remote_addr;
}

}

[Juergen]

Hi Thomas
I found the reason why the Control Panel does not Show any IO ports.

The problem is the Internet Explorer, i use Version 11

With Chrome it works !!!

Best regards

Jürgen

[TomasKnot]

Oh! It may have to do with security settings perhaps? The website uses websocket listening as a primary means of communicating with EVOK; I'm not sure if IE 11 has support for them, though I believe it should.

E: It looks like IE 11 cannot parse lambdas or dynamically register websockets, at least in the manner in which we do so. Microsoft Edge though does appear to work. It's not an easy problem to fix, but we'll have a look.

Glad you managed to solve the problem anyhow.

[TomasKnot]

EVOK GH Master should now work with IE 11, as of the latest GitHub commit (b73e5cc)

[tonytee]

Hi guys,

I would like to tag along on this one

• little sidenote: this is probably a different problem than the problem mentioned earlier in this thread...
  in this case the board is actually not found on SPI at all, so no browser or socket problem i guess *

if i start out with image UniPian-Neuron-OS-2018-03-09.img all works fine out of the box

Evok fine everything fine

But when i just apt-get update / apt-get upgrade things get broken

Does anybody know where i need to look for this?

My guess is that its a kernel thing... it breaks after i reboot, not before taht

under here i have both "good" and "broken" log blurbs

thanks and greetz from holland

---

all is fine:

root@S103-sn488:/boot# uname -a
Linux S103-sn488 4.9.41-v7+ #1023 SMP Tue Aug 8 16:00:15 BST 2017 armv7l GNU/Linux

root@S103-sn488:/home/pi# dmesg | grep neuronspi
[ 6.246724] neuronspi: loading out-of-tree module taints kernel.
[ 6.257603] neuronspi: probe of spi0.3 failed with error -5
[ 6.270814] neuronspi: probe of spi0.2 failed with error -5

root@S103-sn488:/boot# python /opt/evok/evok.py
[I 180321 08:09:18 config:63] eprom: UniPi Neuron S103 version: 1.0 serial: 0x1e8
[I 180321 08:09:18 evok:1628] Starting using config file /etc/evok.conf
[I 180321 08:09:18 config:75] YAML Definition loaded: L20x.yaml, type: 3, definition count 0
[I 180321 08:09:18 config:75] YAML Definition loaded: M30x.yaml, type: 3, definition count 1
[I 180321 08:09:18 config:75] YAML Definition loaded: L50x.yaml, type: 3, definition count 2
[I 180321 08:09:18 config:75] YAML Definition loaded: S10x.yaml, type: 3, definition count 3
[I 180321 08:09:18 config:75] YAML Definition loaded: xS40.yaml, type: 3, definition count 4
[I 180321 08:09:19 config:75] YAML Definition loaded: M10x.yaml, type: 3, definition count 5
[I 180321 08:09:19 config:75] YAML Definition loaded: L30x.yaml, type: 3, definition count 6
[I 180321 08:09:19 config:75] YAML Definition loaded: M50x.yaml, type: 3, definition count 7
[I 180321 08:09:19 config:75] YAML Definition loaded: L51x.yaml, type: 3, definition count 8
[I 180321 08:09:20 config:75] YAML Definition loaded: xS30.yaml, type: 3, definition count 9
[I 180321 08:09:20 config:75] YAML Definition loaded: M40x.yaml, type: 3, definition count 10
[I 180321 08:09:20 config:75] YAML Definition loaded: M20x.yaml, type: 3, definition count 11
[I 180321 08:09:20 config:75] YAML Definition loaded: CUSTOM MODBUS DEVICE.yaml, type: 3, definition count 12
[I 180321 08:09:20 config:75] YAML Definition loaded: L40x.yaml, type: 3, definition count 13
[I 180321 08:09:20 config:75] YAML Definition loaded: xS10.yaml, type: 3, definition count 14
[I 180321 08:09:20 config:75] YAML Definition loaded: xS50.yaml, type: 3, definition count 15
[I 180321 08:09:20 config:75] YAML Definition loaded: evok-alias.yaml, type: 2, definition count 0
[I 180321 08:09:20 evok:1692] HTTP server listening on port: 8080
[I 180321 08:09:20 modbusclient_tornado:122] SPI client started
[I 180321 08:09:20 neuron:157] Reading SPI boards
[D 180321 08:09:20 owclient:377] Entering 1wire loop
[I 180321 08:09:20 neuron:172] No board on SPI 2
[I 180321 08:09:20 neuron:172] No board on SPI 3
[I 180321 08:09:21 web:2063] 101 GET /ws (::1) 7.53ms
[D 180321 08:09:21 evok:158] New WebSocket client connected
[I 180321 08:09:21 web:2063] 304 GET /rest/all (::1) 9.60ms

---

things got broken:

root@S103-sn488:/home/pi# uname -a
Linux S103-sn488 4.9.80-v7+ #1098 SMP Fri Mar 9 19:11:42 GMT 2018 armv7l GNU/Linux

root@S103-sn488:/home/pi# dmesg | grep neuronspi
root@S103-sn488:/home/pi#
nothing

root@S103-sn488:/home/pi# python /opt/evok/evok.py
[I 180321 08:24:14 config:63] eprom: UniPi Neuron S103 version: 1.0 serial: 0x1e8
[I 180321 08:24:14 evok:1628] Starting using config file /etc/evok.conf
[I 180321 08:24:14 config:75] YAML Definition loaded: L20x.yaml, type: 3, definition count 0
[I 180321 08:24:14 config:75] YAML Definition loaded: M30x.yaml, type: 3, definition count 1
[I 180321 08:24:15 config:75] YAML Definition loaded: L50x.yaml, type: 3, definition count 2
[I 180321 08:24:15 config:75] YAML Definition loaded: S10x.yaml, type: 3, definition count 3
[I 180321 08:24:15 config:75] YAML Definition loaded: xS40.yaml, type: 3, definition count 4
[I 180321 08:24:15 config:75] YAML Definition loaded: M10x.yaml, type: 3, definition count 5
[I 180321 08:24:15 config:75] YAML Definition loaded: L30x.yaml, type: 3, definition count 6
[I 180321 08:24:15 config:75] YAML Definition loaded: M50x.yaml, type: 3, definition count 7
[I 180321 08:24:16 config:75] YAML Definition loaded: L51x.yaml, type: 3, definition count 8
[I 180321 08:24:16 config:75] YAML Definition loaded: xS30.yaml, type: 3, definition count 9
[I 180321 08:24:16 config:75] YAML Definition loaded: M40x.yaml, type: 3, definition count 10
[I 180321 08:24:16 config:75] YAML Definition loaded: M20x.yaml, type: 3, definition count 11
[I 180321 08:24:16 config:75] YAML Definition loaded: CUSTOM MODBUS DEVICE.yaml, type: 3, definition count 12
[I 180321 08:24:16 config:75] YAML Definition loaded: L40x.yaml, type: 3, definition count 13
[I 180321 08:24:17 config:75] YAML Definition loaded: xS10.yaml, type: 3, definition count 14
[I 180321 08:24:17 config:75] YAML Definition loaded: xS50.yaml, type: 3, definition count 15
[I 180321 08:24:17 config:75] YAML Definition loaded: evok-alias.yaml, type: 2, definition count 0
[I 180321 08:24:17 evok:1692] HTTP server listening on port: 8080
[I 180321 08:24:17 modbusclient_tornado:122] SPI client started
[I 180321 08:24:17 neuron:157] Reading SPI boards
[I 180321 08:24:17 neuron:172] No board on SPI 1
[I 180321 08:24:17 neuron:172] No board on SPI 2
[D 180321 08:24:17 owclient:377] Entering 1wire loop
[I 180321 08:24:17 neuron:172] No board on SPI 3
[I 180321 08:24:17 web:2063] 101 GET /ws (127.0.0.1) 3.58ms
[D 180321 08:24:17 evok:158] New WebSocket client connected
[I 180321 08:24:17 web:2063] 304 GET /rest/all (127.0.0.1) 4.17ms
[E 180321 08:24:17 neuron:211] 'NoneType' object has no attribute 'do_scan'
Traceback (most recent call last):
File "/opt/evok/neuron.py", line 209, in scan_boards
yield self.modbus_cache_map.do_scan()
AttributeError: 'NoneType' object has no attribute 'do_scan'

[TomasKnot]

Hi @tonytee!
Apt-get upgrade can be dangerous; you can upgrade almost all packages, but there are some caveats: raspberry-pi-bootloader, kernel packages and Tornado should not be updated. This is because our drivers can only link to a specific version of the kernel (as, indeed, is the case for all binary-distributed Linux drivers).

We'll think about adding a debian package which would lock the kernel and Tornado version to the ones we use, so that apt-get upgrade will not break them.

In any case we do an apt-get upgrade (sans the aforementioned packages) at the same time as the image is created.

[tonytee]

Hi Tomas,

Thanks for the suggestions... i'll keep an eye on the git issues ticket, do you want to keep this one alive here too?

Do I understand correctly that it's just a question of pinning the packages you mention too keep my running (remote)neurons safe for now?

i'm so happy I did the upgrade on my desk first, instead of doing it on the remote sites already

i have to say that normally i do apt-get update/upgrade on a regular basis on most of our systems without giving it much thought, so it's good to know that in this case it's a bit more dangerous :/

i'll get back to you after i tried an upgrade with pinned packages...

cheers, tony

[tonytee]

I looked into your package pinning suggestion.

apt-mark hold raspberrypi-bootloader
apt-mark hold python-tornado
apt-mark hold raspberrypi-kernel

before an upgrade at least prevents things getting broken

so at least there's a temporary prevention scheme