This post is to document a problem I ran into as well as the solution I found. I'm running a setup with these devices:
Code: Select all
(wepi) pi@RevPi6892:~ $ piTest -d
Found 3 devices:
Address: 0 module type: 95 (0x5f) RevPi Core V1.2
Module is present
input offset: 0 length: 6
output offset: 6 length: 5
Address: 32 module type: 103 (0x67) RevPi AIO V1.2
Module is present
input offset: 11 length: 20
output offset: 31 length: 4
Address: 33 module type: 96 (0x60) RevPi DIO V1.3
Module is present
input offset: 100 length: 70
output offset: 170 length: 18
First, I found that the web GUI did not work well with Chrome running on Windows7. The Config and Services tabs were not displaying correctly (some rows were missing, and the wrong CPU speed was displayed). Switching to Firefox seemed to fix that problem. I found the online tutorial to be out of date with the version I'm seeing, which led to a little confusion, then trial-and-error. While using PiCtory, I was able to create a configuration and save it, but I could not make the configuration active even after hitting Tools > Reset Driver. Executing `piTest -d` showed that the modules were NOT CONFIGURED! Also, clicking File > Save as Start.Config did not get my project to load on reboot. When I returned to PiCtory after rebooting, I saw the default configuration (1 module, RevPi Core).
I found a solution by copying my project file from /var/www/pictory/projects to my development machine, renamed the file as _config.rsc, then copied it back. After a reboot, the RevPi started up with my configuration. I could see this in PiCtory as well as with `piTest -d`.
Hope this helps somebody.