Hopefully a simple question.
I’m thinking of upgrading my EmonPI. It has a couple of issues (LCD is stuck, and it won’t update from Emoncms) and I was thinking of starting again from the latest SD Card image.
I purchased the EmonPI back in July 2015, so I am assuming that it is a Pi 2 B. I have a PI 3 B+ in the house that is just being used to display the Node Red dashboard on a screen. So, my questions are:
Can I just replace the PI currently in the EMonPI with the PI 3 I have, or are there any physical changes that would stop me?
If I can, Should I - I’m assuming there would be a performance increase, but I haven’t noticed it being slow…
Is emonSD-30Oct18 the image to go for?
Is it just a case of backing up from the Emoncms backup menu, and the Node Red files?
Yes and no. We are just in the process of generating some new scripts for installing emoncms and I suggest holding off for a couple of weeks if there is no desperate need for the update. There are a couple of issues with that image. The scripts will work off a vanilla Raspbian Lite image.
Yes; but use a new SD Card so you have a roll back strategy!
I also cannot remember of Node-Red was installed on that image (check the release notes).
Me neither. But if we have to, then if it’s at all possible to detect the hardware reliably, why does the user have to find out there’s a problem, search the forums/Google/S.O. to find a fix, and then find the file to edit and edit it to do the change manually?
Because despite being suggested almost a year ago, as a means to help avoid issues like this,
the two sections in /boot/config.txtdon’t deal with the CPU frequency.
i.e. the suggestion was never implemented. The CPU freq is “hard coded” to 1200 MHz
One section is for the Pi4. It deals with video. (framebuffer)
The other section deals with disabling bluetooth.
Taken from /boot/config.txt emonSD-17Oct19 only the relevant lines are shown.
#uncomment to overclock the arm. 700 MHz is the default.
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
Replacing the Pi2B with a Pi3 worked out fine! It even makes Emoncms more reactive, for instance when looking at the history. Specially ‘Show all’ (4y data) is much faster now.
USB Import did not work.
=== USB Emoncms import start ===
Backup module version:
"version" : "2.2.3"
Location of data databases: /var/opt/emoncms
Location of emonhub.conf: /etc/emonhub
Location of Emoncms: /var/www/emoncms
Scanning for USB card reader:
- Found: /dev/disk/by-id/usb-USB_2.0_SD_MMC_Reader_842341670035-0:0 at /dev/sda
- No card reader found on sdb
- No card reader found on sdc
USB drive not found
I did the fsck, but that did not help.
Instead I did the manual import of an older backup…