RevPi Connect not saving changes in Pictory

[daniel.correa]

Hello,

I've been facing some issues regarding all configurations made in Pictory. The configuration isn't held after a system's reboot, even after pressing the "Save as start config button" in Pictory. Sometimes the configuration vanishes even if I don't reboot the system.

I have tried possible solutions from:
https://revolution.kunbus.com/forum/vie ... ecd5#p3157
https://revolution.kunbus.com/forum/vie ... php?t=1087

Hardware: Revolution Pi connect recently flashed with Stretch image following instructions from https://revolution.kunbus.com/tutorials ... ll-jessie/

uname -a:
Linux RevPi1002748904 4.19.95-rt38-v7+ #1 SMP PREEMPT RT Tue, 16 Jun 2020 13:25:43 +0200 armv7l GNU/Linux

Pictory version 1.4.7

Please let me know if you require further information.

[dirk]

Hi daniel.correa, we can see that you have updated PiCtory to the latest version - which is quite useful.
Unfortunately PiCtory needs a deleted browser cache afterwards. So please clear the browser cache and try it again.
Secondly have a look at this directory:

Code: Select all

/var/www/pictory/projects/

There might be backup files which you have to delete.

[daniel.correa]

Hello Dirk,

I've already cleared browser's cache on Revolution Pi and looked into /var/www/pictory/projects/. There are no files besides _config.rsc _README.txt and _userSettings.json. I've also disabled cache in Pictory settings area.

The problem still persists.

I've tried changing chown and chgrp to www-data, nothing works. After restart i lose all configurations made.

Code: Select all

pi@RevPi1002748904:/var/www/pictory/projects $ ls -al _config.rsc
-rw-r--r-- 1 www-data www-data 1307 dez  3 14:24 _config.rsc

When i press the "Set as start config" button in pictory, opening the _config.rsc with nano, i can see that the Profibus module is configured properly in the file and i can see the module using piTest -d

Code: Select all

pi@RevPi1002748904:/var/www/pictory/projects $ piTest -d
Found 2 devices:

Address: 0 module type: 105 (0x69) RevPi Connect V1.0
Module is present
     input offset: 1024 length: 6
    output offset: 1030 length: 5

Address: 31 module type: 77 (0x4d) Gateway Profibus V1.0
Module is present
     input offset: 0 length: 244
    output offset: 512 length: 244

When i reboot, both piTest -d and _config.rsc returns only RevPi Connect.

Any other thoughts?

Thank you

[dirk]

To narrow down the problem we have the following idea:
Set or review the RTC by "timedatectl" so that you are sure it is set properly.

Then please compare the timestamps and the contents of the PiCtory configuration after saving and after reboot or as soon as you notice the error during operation.
Are there any changes to the content and timestamps of the PiCtory configuration?

Could the problem be related to Codesys - I think from your other posts that your are using Codesys?

To sum it up - we cannot explain what could cause the configuration to be changed during operation.
Except for example by calling the command "piTest -x".

[daniel.correa]

Hello Dirk,

Timedatectl returns the correct time, according to my region

Code: Select all

pi@RevPi1002748904:/var/www/pictory/projects $ timedatectl
      Local time: Mon 2020-12-07 14:24:58 -03
  Universal time: Mon 2020-12-07 17:24:58 UTC
        RTC time: Mon 2020-12-07 17:24:59
       Time zone: America/Sao_Paulo (-03, -0300)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

Saving configuration as start config, I can see that the time in "config last saved" from pictory matches the current timestamp. Analyzing the data, i can find the Profibus gateway correctly configured.

Code: Select all

pi@RevPi1002748904:/var/www/pictory/projects $ stat _config.rsc
  File: _config.rsc
  Size: 3806            Blocks: 8          IO Block: 4096   regular file
Device: b302h/45826d    Inode: 3105        Links: 1
Access: (0644/-rw-r--r--)  Uid: (   33/www-data)   Gid: (   33/www-data)
Access: 2020-12-07 14:26:00.494073183 -0300
Modify: 2020-12-07 14:26:00.494073183 -0300
Change: 2020-12-07 14:26:00.494073183 -0300
 Birth: -

After rebooting at approximatelly 14:28

Code: Select all

stat _config.rsc
  File: _config.rsc
  Size: 1307            Blocks: 8          IO Block: 4096   regular file
Device: b302h/45826d    Inode: 3105        Links: 1
Access: (0644/-rw-r--r--)  Uid: (   33/www-data)   Gid: (   33/www-data)
Access: 2020-12-07 14:26:00.494073183 -0300
Modify: 2020-12-07 14:28:29.569999995 -0300
Change: 2020-12-07 14:28:29.569999995 -0300
 Birth: -

The file was overwritten somehow. The Profibus gateway's configuration vanished from the file.

To be sure, i disabled Codesys runtime on Revpi, made a new configuration and set it to start config. After rebooting, the configuration was not overwritten and was according to what was configured before.

In summary, this problem is solved - Codesys's boot was changing my Pictory's configuration to an empty one (which is another issue).

Thank you for the support in this case.

[dirk]

Hi Daniel, thank you for your positive feedback.

[f_und_e]

Hello,

I have the very same problem. I already configured a DIO module but now I want to add a ConCAN module. It is possible to add it in pictory, after saving the config and resetting the driver it shows up.

Code: Select all

piTest -d

also shows the module - but if I restart the Revpi, it disappears.

When i stop Codesys with

Code: Select all

sudo systemctl stop codesyscontrol.service

and do the configuration, it is working as it should - but as soon as I activate codesys again or restart the RevPi, the module will be deleted.

How did you manage to fix this behaviour?

edit:

/var/log/apache2/error.log shows this error:


[Thu Jan 28 10:23:14.835517 2021] [core:notice] [pid 1799] AH00094: Command line: '/usr/sbin/apache2'
* Failed to apply overlay '0_revpi-con-can' (kernel)

[f_und_e]

Okay, I solved the issue. You are not allowed to configure it with Pictory, when using the new library version. If you add the device "to the right" via Codesys, it seems to work.
But does it behave like a master this way? The "offical" guide is completely different.

All the best