March-1st-2018, 01:51 PM
188 Wrote:As per your suggestion I need to have the latest netpi-nodered-fieldbus image to get my reported errror resolved.
No this is not what I was saying. I said it is worth it to update the system software to version 1.1.0.0 and also to update the fieldbus node to the latest version. I did not say it will solve your reported error. With the latest version I see a chance in case the error will happen again to have access to the latest source here to debug and reconstruct than with the first fieldbus node version we made 1 year ago.
The second thing I have to mention is that the fieldbus node is 100% a development made by us. In contrast the FRAM node is just 10% ours cause it is based on the very official i2c npm package from the www we do not own. We just added the front end node red bubble to it. So what I am saying is that I am not 100% sure that the i2c npm package we rely on is compatible with debian stretch at all. I saw in your log file that exactly at this point the Docker hub stopped operation with an error.
Also you should recognize that the latest fieldbus node container uses npm in the version 8.x.x, while the fram node is using npm in the versio 6.x ... "&& curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash - \". So this can be also a reason why it is not working. So you can go back to npm v6.x.x in your conatiner too while using jessie.
I will have a look on the fram container next week, if I can upgrade it.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
