Changes by last author:
Added:
|
--------
2020 update -------------------------- I have acquired bit nicer version of raspberry pi called nano pi https://www.antratek.com/nanopi-r1-1gb-ram-8gb-emmc has nice hardware, rtc on board, wifi and other stuff software options for it at the moment I have tested is openWRT version called FriendlyWRT and ubuntu xenial core. http://wiki.friendlyarm.com/wiki/index.php/NanoPi_R1 datalogging stuff works fine on ubuntu, but does not start on WRT based operating system this is the error I got root@FriendlyWrt:/mnt# ./OrangeVemslog.armhf -ash: ./OrangeVemslog.armhf: not found root@FriendlyWrt:/mnt# some hw info root@FriendlyWrt:/# cat proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 root@FriendlyWrt:/# uname -r 4.14.111 LDD option as asked root@FriendlyWrt:/mnt# ldd OrangeVemslog.armhf /lib/ld-linux-armhf.so.3 (0xb6f6b000) libc.so.6 => /lib/ld-linux-armhf.so.3 (0xb6f6b000) Error loading shared library ld-linux-armhf.so.3: No such file or directory (needed by OrangeVemslog.armhf) Error relocating OrangeVemslog.armhf: __printf_chk: symbol not found Error relocating OrangeVemslog.armhf: __fprintf_chk: symbol not found as I understand problem is that openwrt uses ld-musl-arm.so.1 instead ld-linux-armhf.so.3 any idea how this stuff can be sorted? Orangevemslog has to be recompiled with different option or maybe there is some other workaround? |
|
-----
so I have tested it for a few days playing with it and so on. not really want to work over internal uart's, with external usb no problem. |
| managed to write small script which checks is the OrangeLogger working and if not it will try to start it again. added it to crontab so it works nice now and checks for that every minute. |
| made vemstune to connect to ecu over the vpn with help of ser2net, if I try to connect with it over internal network, no problem, it just breaks logging process and I'm online, if i try that over vpn ip's sadly cant connect until I stop logging process :) |
|
the only issue now is that after it boots up, start's to log, it works just fine, if it crashes it get's autorestart and so on.
problem is when I try to connect to ecu with vemstune over ser2net, it interrupts the logging process and it wont resume after I disconect from ecu, it just writes huge amount on error messages into the log file (500689) IDLE: ecu not responding, likely OFFLINE (504201) IDLE: ecu not responding, likely OFFLINE |
| rebooting ecu does not help for it to start working again, restarting process does. as I understand when the process starts it execute some special command to query the data from the ecu and later are not using that again. anyway if that gets working it will break ser2net process if I'm online, thinking about the solution how to manage 2 apps using same serial port :) |
| btw, if I switch power off for ecu and later start it again OrangeLogger understands it and no problem creates new log file for it |
| thinking that it needs somekind of com port mirroring to get working with 2 devices |