Page 1 of 1

Issue with RevPi DIO config

Posted: 18 Oct 2018, 10:42
by g.wickes
I’ve been trying to run some tests with a RevPi Core and a RevPi DIO connected via Bridge, but in spite of the PiCtory config checking out and writing to, and loading from default correctly, the system still seems to fail at loading it in a usable manner (such as revpimodio2).

  • the owner/group of _config.rsc is www-data/www-data
  • I reset drivers (piTest -x) each time I adjust the config (and upon that not working restart the device)
  • the image I am using is jessie3005

I’ve tried sourcing a solution by searching the forums and the various pages of documentation provided by your website, but have not been successful.

Thank you in advance!

Re: Issue with RevPi DIO config

Posted: 23 Oct 2018, 13:23
by dirk
Hello g.wickes,
please excuse the long delay for my response. We have checked all the steps you have performed - everything looks well. We have had once a problem which was related to insufficient write permissions to the "_config.rsc" file only with a small amount of devices. Although you have already checked this please update the PiCtory package as follows:

Code: Select all

sudo apt update
sudo apt install pictory
If the problem still exists please provide the "/var/log/kern.log" file.
Please check if this symbolic link exists:

Code: Select all

pi@RevPi8165:~ $ ls -al /etc/revpi/config.rsc
lrwxrwxrwx 1 root root 37 Jul 17 15:13 /etc/revpi/config.rsc -> /var/www/pictory/projects/_config.rsc
Check if the file changes when you modify and save your configuration. You may pretty print the JSON format as follows:

Code: Select all

cat /etc/revpi/config.rsc | json_pp -f json | more
The "saveTS" field holds this information:

Code: Select all

{
   "App" : {
      "saveTS" : "20181018135113",
[...]

Re: Issue with RevPi DIO config

Posted: 25 Oct 2018, 13:57
by g.wickes
Thank you for your help!

I've discovered that the config symbolic link was not present where it should have been.

Code: Select all

/etc/revpi/config.rsc
I created it manually and now the Module is being recognized when I check piTest -d.