Closed SAM26K closed 5 years ago
I do have moisture sensors connected on six of the channels that looked ok maybe sample rate too high but reasonable numbers. The RPi is already embedded into an active garden and not accessible for physically experimenting with.
On Fri, Oct 12, 2018 at 8:27 AM Kyle Gabriel notifications@github.com wrote:
Quick question: when you tested the pyadda module, did you have a channel connected to a known voltage to test if the returned voltage was accurate? If not, could you connect a source (like a AA battery) and rerun the test script?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429364711, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjV9frc1iLlSZBLzb2z0bD2opAZK6ks5ukLTPgaJpZM4XBeMO .
Nearing the end of the grow cycle though and would like to help you develop calibration,
\\\
On Fri, Oct 12, 2018 at 10:10 AM John Baxter jbbart03@gmail.com wrote:
I do have moisture sensors connected on six of the channels that looked ok maybe sample rate too high but reasonable numbers. The RPi is already embedded into an active garden and not accessible for physically experimenting with.
On Fri, Oct 12, 2018 at 8:27 AM Kyle Gabriel notifications@github.com wrote:
Quick question: when you tested the pyadda module, did you have a channel connected to a known voltage to test if the returned voltage was accurate? If not, could you connect a source (like a AA battery) and rerun the test script?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429364711, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjV9frc1iLlSZBLzb2z0bD2opAZK6ks5ukLTPgaJpZM4XBeMO .
I just pushed a fix for the ADS1256 module. Follow these steps to properly test if it works:
Hi Kyle, Still not finding the device. Here is the feedback and upgrade log: Activate: Success: Input controller activated in SQL database Error: Could not activate Input controller with ID 7c56228d-cdb5-464d-bc12-58b0bb01de3d: No module named 'adc_consts'
deactivate: Success: Input controller deactivated in SQL database Error: Input controller with ID 7c56228d-cdb5-464d-bc12-58b0bb01de3d not found
Here is current version info: Mycodo Version: 6.4.1 Python Version: 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516] Database Version: da10608dbc1c Daemon Status: Running Daemon Process ID: 1212 Daemon RAM Usage: 46.236 MB Daemon Virtualenv: Yes Frontend RAM Usage: 53.104 MB Frontend Virtualenv: Yes uptime
01:33:28 up 23 min, 1 user, load average: 0.49, 0.89, 0.79
Kernel Information: uname -a
Linux raspberrypi3_2 4.14.70-v7+ #1144 SMP Tue Sep 18 17:34:46 BST 2018 armv7l GNU/Linux
On Sat, Oct 13, 2018 at 1:33 AM John Baxter jbbart03@gmail.com wrote:
Hi Kyle, Still not finding the device. Here is the feedback and upgrade log: Activate: Success: Input controller activated in SQL database Error: Could not activate Input controller with ID 7c56228d-cdb5-464d-bc12-58b0bb01de3d: No module named 'adc_consts'
deactivate: Success: Input controller deactivated in SQL database Error: Input controller with ID 7c56228d-cdb5-464d-bc12-58b0bb01de3d not found
Dependency Log:
30 Last 30 lines of /var/log/mycodo/mycododependency.log: [2018-10-10 14:37:38] Successfully installed ads1256
[2018-10-10 14:37:39] [2018-10-10 14:37:39] #### Setting permissions
[2018-10-10 14:37:42] #### All Dependencies have been installed.
[2018-10-11 09:49:46] Dependency installation beginning. Installing: ads1256
[2018-10-11 09:49:46] [2018-10-11 09:49:46] #### Installing/updating git:// github.com/fabiovix/py-ads1256.git#egg=ads1256 (pip-git) [2018-10-11 09:49:54] Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple [2018-10-11 09:49:54] Obtaining ads1256 from git+git:// github.com/fabiovix/py-ads1256.git#egg=ads1256 [2018-10-11 09:49:54] Cloning git://github.com/fabiovix/py-ads1256.git to ./env/src/ads1256 [2018-10-11 09:50:00] Installing collected packages: unknown [2018-10-11 09:50:00] Found existing installation: UNKNOWN 0.0.0 [2018-10-11 09:50:00] Not uninstalling unknown at /usr/local/lib/python3.5/dist-packages, outside environment /home/pi/Mycodo/env [2018-10-11 09:50:00] Can't uninstall 'UNKNOWN'. No files were found to uninstall. [2018-10-11 09:50:00] Running setup.py develop for unknown [2018-10-11 09:50:08] Successfully installed unknown
[2018-10-11 09:50:09] Successfully installed ads1256
[2018-10-11 09:50:10] [2018-10-11 09:50:10] #### Setting permissions
[2018-10-11 09:50:13] #### All Dependencies have been installed.
Upgrade Log:
[2018-10-13 00:46:01] Upgrade script executed with the 'force-upgrade-master' argument. Upgrading from github repo master. [2018-10-13 00:46:01] [2018-10-13 00:46:01] #### Upgrade to v6.4.1 initiated 2018-10-13_00-45-56
[2018-10-13 00:46:01] [2018-10-13 00:46:01] #### Beginning Upgrade: Stage 1 of 2 #### [2018-10-13 00:46:04] Stopping the Mycodo daemon...Done. [2018-10-13 00:46:58] Downloading latest Mycodo version to /home/pi/Mycodo-master.tar.gz...Done. [2018-10-13 00:46:58] Creating /tmp/Mycodo-6.4.1...Done. [2018-10-13 00:46:59] Extracting /home/pi/Mycodo-master.tar.gz to /tmp/Mycodo-6.4.1...Done. [2018-10-13 00:46:59] Removing /home/pi/Mycodo-master.tar.gz...Done. [2018-10-13 00:46:59] Copying /tmp/Mycodo-6.4.1/.upgrade status file to /tmp/Mycodo-6.4.1...Done. [2018-10-13 00:46:59] Moving env directory...Done. [2018-10-13 00:46:59] Copying databases from /home/pi/Mycodo/databases/ to /tmp/Mycodo-6.4.1/databases...Done. [2018-10-13 00:46:59] Copying flask_secret_key from /home/pi/Mycodo/databases/ to /tmp/Mycodo-6.4.1/databases...Done. [2018-10-13 00:46:59] Copying statistics ID...Done. [2018-10-13 00:46:59] Copying SSL certificates...Done. [2018-10-13 00:46:59] Copying mycodo/inputs/custom_inputs...Done. [2018-10-13 00:46:59] #### Stage 1 of 2 Complete #### [2018-10-13 00:46:59] [2018-10-13 00:46:59] #### Continuing Upgrade: Stage 2 of 2 #### [2018-10-13 00:46:59] [2018-10-13 00:46:59] Moving old Mycodo from /home/pi/Mycodo to /var/Mycodo-backups/Mycodo-backup-2018-10-13_00-45-56-6.4.1...Done. [2018-10-13 00:46:59] Moving new Mycodo from /tmp/Mycodo-6.4.1 to /home/pi/Mycodo...Done. [2018-10-13 00:47:29] [2018-10-13 00:47:29] #### Upgrading Mycodo database with alembic (if needed) [2018-10-13 00:47:33] [2018-10-13 00:47:33] Running post-upgrade script... [2018-10-13 00:47:33] [2018-10-13 00:47:33] #### Running initialization [2018-10-13 00:47:34] [2018-10-13 00:47:34] #### Creating mycodo user [2018-10-13 00:47:34] The user
mycodo' is already a member of
adm'. [2018-10-13 00:47:34] The usermycodo' is already a member of
dialout'. [2018-10-13 00:47:34] The usermycodo' is already a member of
gpio'. [2018-10-13 00:47:34] The usermycodo' is already a member of
i2c'. [2018-10-13 00:47:35] The usermycodo' is already a member of
video'. [2018-10-13 00:47:35] [2018-10-13 00:47:35] #### Compiling mycodo_wrapper [2018-10-13 00:47:36] [2018-10-13 00:47:36] #### Creating symlinks to Mycodo executables [2018-10-13 00:47:36] [2018-10-13 00:47:36] #### Creating files and directories [2018-10-13 00:47:37] [2018-10-13 00:47:37] #### Setting permissions [2018-10-13 00:47:38] [2018-10-13 00:47:38] #### Removing statistics file [2018-10-13 00:47:38] [2018-10-13 00:47:38] #### Checking if swap size is 100 MB and needs to be changed to 512 MB [2018-10-13 00:47:38] #### Swap not currently set to 100 MB. Not changing. [2018-10-13 00:47:38] [2018-10-13 00:47:38] #### Checking python 3 virtualenv [2018-10-13 00:47:38] #### Virtualenv already exists, skipping creation [2018-10-13 00:47:38] [2018-10-13 00:47:38] [2018-10-13 00:47:38] #### Updating apt repositories [2018-10-13 00:47:39] Hit:1 http://archive.raspberrypi.org/debian stretch InRelease [2018-10-13 00:47:39] Get:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB] [2018-10-13 00:47:41] Get:3 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages [11.7 MB] [2018-10-13 00:49:02] Fetched 11.7 MB in 1min 23s (140 kB/s) [2018-10-13 00:49:10] Reading package lists... [2018-10-13 00:49:11]On Fri, Oct 12, 2018 at 3:52 PM Kyle Gabriel notifications@github.com wrote:
I just pushed a fix for the ADS1256 module. Follow these steps to properly test if it works:
- Deactivate and delete any ADS1256 inputs currently on your Data page.
- Perform an upgrade to the master branch.
- Add a ADS1256 Input on the Data page, configure, and activate.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429483490, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjaba2CRckN6G2-yzvpKdp0bwd0naks5ukR0WgaJpZM4XBeMO .
I think part of the upgrade log was missing in the previous email. Here's the other half:
Edit: Deleted by Kyle Gabriel (too long)
Pasting long logs in this thread makes it difficult for reading. So, if you have a long log you want to share, please log into github.com with a browser and attach the file. Do not try to attach it in an email or paste it in an email. I've gone through and deleted the long log portions here so it's easier for me to navigate this thread.
Still not finding the device. Here is the feedback and upgrade log: Activate: Success: Input controller activated in SQL database Error: Could not activate Input controller with ID 7c56228d-cdb5-464d-bc12-58b0bb01de3d: No module named 'adc_consts'
Did you follow all 3 instructions I gave that would have you deactivate/delete the current input device and add it again? This is required to install the new dependency. The No module named 'adc_consts'
error indicates you didn't perform steps 1 and 2.
Sorry about that Kyle, Would you mind repeating step 1 and 2 instructions?
On Sat, Oct 13, 2018 at 6:45 AM Kyle Gabriel notifications@github.com wrote:
Pasting long logs in this thread makes it difficult for reading. So, if you have a long long you want to share, please log into github.com with a browser and attach the file. Do not try to attach it in an email or paste it in an email. I've gone through and deleted the long log portions here so it's easier for me to navigate this thread.
Still not finding the device. Here is the feedback and upgrade log: Activate: Success: Input controller activated in SQL database Error: Could not activate Input controller with ID 7c56228d-cdb5-464d-bc12-58b0bb01de3d: No module named 'adc_consts'
Did you follow all 3 instructions I gave that would have you deactivate/delete the current input device and add it again? This is required to install the new dependency. The No module named 'adc_consts' error indicates you didn't perform steps 1 and 2.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429543109, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjTAlTuZ_R60WoFtnb6Q32ngks4-zks5uke5zgaJpZM4XBeMO .
I was asking if you've deleted all current ADS1256 Inputs you may have on the Data page. After that, when you re-add the ADS1256 Input, there may be a prompt to install a new dependency. If you have already performed this, before the error you pasted (https://github.com/kizniche/Mycodo/issues/537#issuecomment-429522575), then I need to investigate something else.
I did that. ie deleted existing data inputs before upgrading to the master. It still can't find the device.
On Sat, Oct 13, 2018 at 8:19 AM Kyle Gabriel notifications@github.com wrote:
I was asking if you've deleted all current ADS1256 Inputs you may have on the Data page. After that, when you re-added one, there may be a prompt to install a dependency. If you have already performed this, before the error you pasted (#537 (comment) https://github.com/kizniche/Mycodo/issues/537#issuecomment-429522575), then I need to investigate something else.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429550127, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjWYLbJ0fv2BMhYpz0HQ803TKOxuqks5ukgR5gaJpZM4XBeMO .
adc_consts
is not the device, they are a set of variables, and is a part of the pyadda python library. Looking into why you're unable to access them.
I'm unable to replicate your issue. It's working fine from my end (except the actual measurement because I don't have the device).
I just released v6.4.2. Could you delete your entire existing install (mv ~/Mycodo ~/Mycodo-backup
) and install from the beginning?
These would be the proper steps to installing new:
1. sudo service mycodo stop
2. sudo service mycodoflask stop
3. mv ~/Mycodo ~/Mycodo-backup
Then install according the instructions in the README
6.4.2 has the same problem. Input adds ok but activate generates same error as before, no prompts to add depency, ×
×
On Sat, Oct 13, 2018 at 5:31 PM Kyle Gabriel notifications@github.com wrote:
These would be the proper steps to installing new:
- sudo service mycdoo stop
- sudo service mycodoflask stop
- mv ~/Mycodo ~/Mycodo-backup
Then install according the instructions in the README
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429586522, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVja6h12GsFukPBq9gof83fKo8570aks5ukoX3gaJpZM4XBeMO .
If you're not prompted to install the dependency, that means you have not deleted your current install and installed fresh.
I thought renaming mycodo did that. What else should I do to make sure its uninstalled?
On Sat, Oct 13, 2018 at 6:33 PM Kyle Gabriel notifications@github.com wrote:
If you're not prompted to install the dependency, that means you have not deleted your current install and installed fresh.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429588935, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjZwEbjT9kbP-w7T9C8F8v44-OV_Wks5ukpR_gaJpZM4XBeMO .
I already followed those instructions.
On Sat, Oct 13, 2018 at 6:38 PM Kyle Gabriel notifications@github.com wrote:
See #537 (comment) https://github.com/kizniche/Mycodo/issues/537#issuecomment-429586522
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429589094, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjffmiDO8yp3yO52sikjzQo5pGoBmks5ukpV6gaJpZM4XBeMO .
Are you sure you're using the right library? Do you want me to retest it?
On Sat, Oct 13, 2018 at 6:43 PM John Baxter jbbart03@gmail.com wrote:
I already followed those instructions.
On Sat, Oct 13, 2018 at 6:38 PM Kyle Gabriel notifications@github.com wrote:
See #537 (comment) https://github.com/kizniche/Mycodo/issues/537#issuecomment-429586522
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429589094, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjffmiDO8yp3yO52sikjzQo5pGoBmks5ukpV6gaJpZM4XBeMO .
I already followed those instructions.
pyadda is installed within a python virtual environment. This virtualenv is located within the Mycodo directory. It is impossible for the pyadda module to be loaded from a freshly-installed virtualenv that hasn't had pyadda installed. If you did not have the pyadda module installed in your virtualenv (if Mycodo was reinstalled), then you would receive the error, No module named 'pyadda'
, However, pyadda is being loaded by the input module, indicating you have a stale pyadda available in the virtualenv. The only other explanation is that you installed pyadda in your system install of python (I did not write instructions for doing that). If that's the case, you will need to uninstall that.
Are you sure you're using the right library?
I am quite sure. It is loading just fine for me on my end (except for the measurement because I don't have the physical hardware).
Reinstalling Raspbian and then Mycodo may be an easier method for you to fix your module issue.
Everything works up to but not including activation which is when it accesses the a/d board. Since you don't have the board you wouldn't be able to check that step right? I have example code from waveshare I run in a terminal and it works fine.
On Sat, Oct 13, 2018 at 6:50 PM Kyle Gabriel notifications@github.com wrote:
I already followed those instructions.
pyadda is installed within a python virtual environment. This virtualenv is located within the Mycodo directory. It is impossible for the pyadda module to be loaded from a freshly-installed virtualenv that hasn't had pyadda installed. If you did not have the pyadda module installed in your virtualenv (if Mycodo was reinstalled), then you would receive the error, No module named 'pyadda', However, pyadda is being loaded by the input module, indicating you have a stale pyadda available in the virtualenv. The only other explanation is that you installed pyadda in your system install of python. If that's the case, you will need to uninstall that (I did not write instructions for doing that).
Are you sure you're using the right library?
I am quite sure. It is loading just fine for me on my end (except for the measurement because I don't have the physical hardware).
Reinstalling Raspbian and then Mycodo may be an easier method for you to fix your module issue.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429589544, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjfEM20e0NGn3P0BAT8TN_quYkzsTks5ukph-gaJpZM4XBeMO .
Yes, you've already confirmed the pyadda code works, which is why it's being used in the mycodo module.
I just found an issue in the module, however your error doesn't appear to be a result of this issue, indicating your system is still misconfigured somehow. I've tested the current code on several of my Pis and it's working.
My recommendation is to:
This should fix your current issue and we can continue bug testing.
I found one issue with the current code (which also wouldn't be causing your issue). However, hold off on performing an upgrade to master until I've fixed this (should only be a few minutes).
Okay. I just committed the fix, the code is all ready to test.
Still have same problem. Anything else you want me to try before reinstalling raspian? That will take awhile.
On Sat, Oct 13, 2018 at 7:48 PM Kyle Gabriel notifications@github.com wrote:
Okay. I just committed the fix, the code is all ready to test.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429591865, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjdmg5m2GxKOBb10r1FJ2w0bC0n09ks5ukqXhgaJpZM4XBeMO .
Hi Kyle, Do you have a direct contact email I can use? Thanks
On Sat, Oct 13, 2018 at 8:33 PM Kyle Gabriel notifications@github.com wrote:
See #537 (comment) https://github.com/kizniche/Mycodo/issues/537#issuecomment-429591533
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429593684, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjbRtZhNYdMammSlijPVsXAsy2W8vks5ukrBygaJpZM4XBeMO .
I was thinking about sending you a waveshare pcb so you can test it and fix the driver problems. But need a private email to communicate with. Thanks Again.
On Sun, Oct 14, 2018 at 10:42 AM John Baxter jbbart03@gmail.com wrote:
Hi Kyle, Do you have a direct contact email I can use? Thanks
On Sat, Oct 13, 2018 at 8:33 PM Kyle Gabriel notifications@github.com wrote:
See #537 (comment) https://github.com/kizniche/Mycodo/issues/537#issuecomment-429591533
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429593684, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjbRtZhNYdMammSlijPVsXAsy2W8vks5ukrBygaJpZM4XBeMO .
" However, pyadda is being loaded by the input module, indicating you have a stale pyadda available in the virtualenv. The only other explanation is that you installed pyadda in your system install of python (I did not write instructions for doing that). If that's the case, you will need to uninstall ..
Exactly how do I do the above? Reinstalling raspbian is not a practical option for me as the RPi is embedded into my grow and depend on it working to keep my plants healthy. Don't want to risk breaking what is working for something that is not working so far.
On Sun, Oct 14, 2018 at 12:18 PM John Baxter jbbart03@gmail.com wrote:
I was thinking about sending you a waveshare pcb so you can test it and fix the driver problems. But need a private email to communicate with. Thanks Again.
On Sun, Oct 14, 2018 at 10:42 AM John Baxter jbbart03@gmail.com wrote:
Hi Kyle, Do you have a direct contact email I can use? Thanks
On Sat, Oct 13, 2018 at 8:33 PM Kyle Gabriel notifications@github.com wrote:
See #537 (comment) https://github.com/kizniche/Mycodo/issues/537#issuecomment-429591533
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429593684, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjbRtZhNYdMammSlijPVsXAsy2W8vks5ukrBygaJpZM4XBeMO .
There are a number of things that can be wrong. This is why I recommended reinstalling Raspbian.
We can start by comparing your output to my output. Below is what a working system should return:
pi@delta:~/Mycodo $ ./env/bin/python
Python 3.5.3 (default, Jan 19 2017, 14:11:04)
[GCC 6.3.0 20170124] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyadda
>>> pyadda.__file__
'/home/pi/Mycodo/env/src/pyadda/pyadda.cpython-35m-arm-linux-gnueabihf.so'
>>> import adc_consts
>>> adc_consts.__file__
'/home/pi/Mycodo/env/src/pyadda/adc_consts.py'
Starting from scratch on mycodo again. Is there anything else I should delete outside of Mycodo folder?
On Sun, Oct 14, 2018 at 1:38 PM Kyle Gabriel notifications@github.com wrote:
There are a number of things that can be wrong. This is why I recommended reinstalling Raspbian.
We can start by comparing your output to my output. Below is what a working system should return:
pi@delta:~/Mycodo $ ./env/bin/python Python 3.5.3 (default, Jan 19 2017, 14:11:04) [GCC 6.3.0 20170124] on linux Type "help", "copyright", "credits" or "license" for more information.
import pyadda pyadda.file '/home/pi/Mycodo/env/src/pyadda/pyadda.cpython-35m-arm-linux-gnueabihf.so' import adc_consts adc_consts.file '/home/pi/Mycodo/env/src/pyadda/adc_consts.py'
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429660358, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjTUjKjLZpTbttC4CiIQcurbPT37vks5uk6C5gaJpZM4XBeMO .
I gave two options:
If you don't want to do either of those, then I just can't help you.
No worries. I would be more confident in ur solution if I could send you the actual hardware. Need a private offline contact info though.
On Sun, Oct 14, 2018 at 1:59 PM Kyle Gabriel notifications@github.com wrote:
I gave two options:
- Reflash raspbian
- Perform the commands I outlined above if you want me to help diagnose your issue
If you don't want to do either of those, then I just can't help you.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429662118, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjetl-4AvYiTyKfF8iGotRrbU6Izkks5uk6XHgaJpZM4XBeMO .
Ok will get back to you when I have a chance to start over. Thanks for all the help so far.
On Sun, Oct 14, 2018 at 3:47 PM Kyle Gabriel notifications@github.com wrote:
None of what you just wrote refutes what I've written previously.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-429669970, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjXIS4kqukhy4V7sidWKFLACxw5KZks5uk77ngaJpZM4XBeMO .
Hi Kyle, I did a fresh install of Raspbian and still have the same problem. Selecting activate generates this error: Error: Could not activate Input controller with ID c58312b6-9277-4338-b09c-b2dab36b4b8c: No module named 'pyadda'
It did prompt to install pyadda and BCM2835 and finished successfully. Are there any logs you want to see? Thanks.
On Sun, Oct 14, 2018 at 4:01 PM Kyle Gabriel notifications@github.com wrote:
Closed #537 https://github.com/kizniche/Mycodo/issues/537.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#event-1902829047, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjfarlNM1PLWtFcfLNUA2144cSPsFks5uk8IvgaJpZM4XBeMO .
Can you restart the backend (Config -> Restart Backend) and try activating it again?
Progress! No errors now but voltage measured is zero and says "no data" on the dashboard.
On Mon, Oct 15, 2018 at 3:28 PM Kyle Gabriel notifications@github.com wrote:
Reopened #537 https://github.com/kizniche/Mycodo/issues/537.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#event-1905365824, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjbCR5TRkQRasdv3u9VhKxsvmDjcoks5ulQwSgaJpZM4XBeMO .
Okay. I'll look into it and get a fix for you to upgrade to master and test.
I just pushed a potential fix. Go ahead and upgrade to the master branch, then try activating the controller again. I added debug lines in the code, so please paste the excerpt of the daemon log after you activate the controller.
I just found an issue with the code and pushed another fix.
The current code that's implemented is done very sloppily. If you could grant me SSH access to your Pi (as user pi) connected to your ADC, I could rapidly improve the code. Let me know what you think.
Still says "no data". Daemon log:
2018-10-15 17:08:59,931 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:08:59,937 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:08:59,951 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:08:59,956 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:08:59,975 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:08:59,981 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:08:59,994 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,000 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,014 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,019 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,038 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,044 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,057 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,063 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,104 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,110 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,125 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,126 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,129 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,140 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,154 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,167 - mycodo.ads1256_379bb855 - ERROR - Could not read chip
On Mon, Oct 15, 2018 at 4:19 PM Kyle Gabriel notifications@github.com wrote:
I just pushed a potential fix. Go ahead and upgrade to the master branch, then try activating the controller again. I added debug lines in the code, so please paste the excerpt of the daemon log after you activate the controller.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-430047004, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjaijJF-j-2SS2n-qoh0DhbucKk6vks5ulRf9gaJpZM4XBeMO .
Sure how do I give you permission? I also have vnc if you want to use that.
On Mon, Oct 15, 2018 at 5:11 PM John Baxter jbbart03@gmail.com wrote:
Still says "no data". Daemon log:
2018-10-15 17:08:59,931 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:08:59,937 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:08:59,951 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:08:59,956 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:08:59,975 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:08:59,981 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:08:59,994 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,000 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,014 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,019 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,038 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,044 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,057 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,063 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,104 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,110 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,125 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,126 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,129 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,140 - mycodo.ads1256_379bb855 - ERROR - Could not read chip 2018-10-15 17:09:00,154 - mycodo.ads1256_379bb855 - ERROR - TEST00: None 2018-10-15 17:09:00,167 - mycodo.ads1256_379bb855 - ERROR - Could not read chip
On Mon, Oct 15, 2018 at 4:19 PM Kyle Gabriel notifications@github.com wrote:
I just pushed a potential fix. Go ahead and upgrade to the master branch, then try activating the controller again. I added debug lines in the code, so please paste the excerpt of the daemon log after you activate the controller.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-430047004, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjaijJF-j-2SS2n-qoh0DhbucKk6vks5ulRf9gaJpZM4XBeMO .
Contact me through http://kylegabriel.com/contact and I'll email you instructions, so you don't expose any login information on github.
Having mysterious issues with pyadda, I started looking for how to port one of the other 2 libraries to python3, until I came across this post that solved it.
I forked the PiPyADC repo and applied the python3 code changes, and added a setup.py to allow the pip install from the input module options. So, it looks like measurements are working and the daemon isn't crashing like when using pyadda.
Thanks very much for all the help. It seems to be working but haven't figured out to calibrate it. Do you have instructions for it? It seems that the high and low limits do affect the output reading but don't know how it does that. The input range is 0 to 2.5 but fractional numbers aren't accepted. The cal would be closer to actual input voltage if I could set the max to 2.5 or so. Thanks Again!
On Tue, Oct 16, 2018 at 12:41 AM Kyle Gabriel notifications@github.com wrote:
I forked the PiPyADC repo and applied the python3 code changes, and added a setup.py to allow the pip install from the input module options. So, it looks like measurements are working and the daemon isn't crashing like when using pyadda.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-430134220, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjfX_gXX7vC5wbKA4iOfMXn4awUpIks5ulY2cgaJpZM4XBeMO .
I'm not really familiar with the ADS1256 at all, but these are the calibration functions found in the PiPyADC library:
Notice the Mycodo input module performs cal_self() during initialization:
I'll try to look up some literature later.
I just added the ability to select the calibration function to be executed when the Input module is activated.
Do I need to update to the master branch? Do I need to delete old inputs before upgrading?
On Tue, Oct 16, 2018 at 2:57 PM Kyle Gabriel notifications@github.com wrote:
I just added the ability to select the calibration function to be executed when the Input module is activated.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-430415606, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjSFD619i2Sy2GOXPgze5b2-AKM2Eks5ullZCgaJpZM4XBeMO .
With all 8 inputs on the dashboard, it's flaky.
On Tue, Oct 16, 2018 at 6:49 PM John Baxter jbbart03@gmail.com wrote:
Do I need to update to the master branch? Do I need to delete old inputs before upgrading?
On Tue, Oct 16, 2018 at 2:57 PM Kyle Gabriel notifications@github.com wrote:
I just added the ability to select the calibration function to be executed when the Input module is activated.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/kizniche/Mycodo/issues/537#issuecomment-430415606, or mute the thread https://github.com/notifications/unsubscribe-auth/AVEVjSFD619i2Sy2GOXPgze5b2-AKM2Eks5ullZCgaJpZM4XBeMO .
Mycodo Issue Report:
Problem Description
Please list:
Errors
Steps to Reproduce the issue:
How can this issue be reproduced?
Additional Notes
Is there anything that should be added to make it easier to address this issue?