With regards to getting KPLEX to start, I was able to fix it by creating a symbolic link in /etc.
From the command line:
sudo ln -s /home/pi/.kplex.conf /etc/kplex.conf
Kplex is apparently not finding /home/pi/.kplex.conf. Having a symbolic link to the configuration file available in /etc/ solves the problem, while still allowing the OpenPlotter KPLEX app to create a config file.
It's a work-around. I suggest that in the next version of the program, the KPLEXCONF environment variable be set, which should allow the kplex.conf file to be accessible from whatever location is designated by the environment variable.
From the command line:
sudo ln -s /home/pi/.kplex.conf /etc/kplex.conf
Kplex is apparently not finding /home/pi/.kplex.conf. Having a symbolic link to the configuration file available in /etc/ solves the problem, while still allowing the OpenPlotter KPLEX app to create a config file.
It's a work-around. I suggest that in the next version of the program, the KPLEXCONF environment variable be set, which should allow the kplex.conf file to be accessible from whatever location is designated by the environment variable.