search

Dan-in-CA / SIP

A highly customizable DIY irrigation/sprinkler controller based on Raspberry Pi
358 stars 156 forks source link

SIP for Orange Pi One #189

Closed Riaan111209 closed 5 years ago

Riaan111209 commented 7 years ago

Hi Dan I see there is somebody on this page that had questions about this in the past. I also have a Orange Pi One. I want to be able to switch 21 channels/relays with it but SIP will not start. I get a message in the terminal that it is not a raspberry pi. Can you please help me set this up. I have jumped through a lot of different irrigation stuff and so far this software looks like it is what I need for my system. Hope to hear from you soon. Kind Regards

Dan-in-CA commented 7 years ago

Welcome Riaan

I don't have much time right now but I am willing to help you get SIP running on your Orange Pi. You will need to make some changes to the SIP Python code. I would suggest that you fork SIP to your GitHub repository. You can make changes there and when things are working, your changes can be merged into the main SIP repo.

It looks like the Orange Pi has the same GPIO pin layout as a RPI B+. That will make things fairly easy.

SIP detects what kind of board it is running on by trying to import a GPIO library either for the Pi or Beagle bone black. I assume you have an importable GPIO library on the Orange Pi. You can try replacing the Pi GPIO library with it in the import instruction on line 6 of gpio_pins.py in the SIP directory for sxample: import your_library_here as GPIO That should at least allow sip to run.

If you plan to use 21 channels you should probably put together a shift register interface as described on the SIP wiki: https://github.com/Dan-in-CA/SIP/wiki/Relay-interface

That' all I have time for right now. I will be back online later today.

Dan

Riaan111209 commented 7 years ago

Hi Dan Thank you very much for the reply and that you will help me to get SIP running on an orange pi. I don't know what time it is where you are. At the moment it is 23:05 here. I hope you can help me to set this up because $ am new to this coding and still have a lot to learn.

Kind Regards Riaan

On 03 Jun 2017 17:44, "Dan" notifications@github.com wrote:

Welcome Riaan

I don't have much time right now but I am willing to help you get SIP running on your Orange Pi. You will need to make some changes to the SIP Python code. I would suggest that you fork SIP to your GitHub repository. You can make changes there and when things are working, your changes can be merged into the main SIP repo.

It looks like the Orange Pi has the same GPIO pin layout as a RPI B+. That will make things fairly easy.

SIP detects what kind of board it is running on by trying to import a GPIO library either for the Pi or Beagle bone black. I assume you have an importable GPIO library on the Orange Pi. You can try adding it to the import instruction on line 6 of gpio_pins.py in the SIP directory for sxample: import RPi.GPIO or your_library_here as GPIO That should at least allow sip to run.

If you plan to use 21 channels you should probably put together a shift register interface as described on the SIP wiki: https://github.com/Dan-in-CA/SIP/wiki/Relay-interface

That' all I have time for right now. I will be back online later today.

Dan

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-305982842, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIniLiXzdfEueyq0PsYIAwB-wF7UZks5sAX9GgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

OK. I will work on modifying the Python code for SIP to try and get it to work with the Orange Pi. You will need to install a Python GPIO library on your Orange Pi. Follow the instructions for "installing Python and Libraries" at: https://diyprojects.io/orange-pi-onelite-tutorial-use-gpio-python-pinouts/#.WTNH09y1sdU

Sip should be installed into a directory named "pi". Does your Orange Pi have a pi directory? I don't have an Orange Pi so I will probably ask a few questions like that.

According to the time stamp on your previous post it looks like your local time is about 12 hours and 45 minutes ahead of the time here in California. You must be on the other side of the world.

Dan

Riaan111209 commented 7 years ago

Good morning Dan I tried to attach 2 pictures but then my message got rejected on your side because of the size.

Inside the code of gpio_pins.py Line 7 says platform 'pi' Should I change this to 'root' as that is where the SIP folder is? Kind Regards

On 04 Jun 2017 08:18, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Good morning Dan I attached 2 pictures in this mail so that you can see what it looks like on my side. Thank you very much for being willing to help me with this.

Kind Regards Riaan

On 04 Jun 2017 01:54, "Dan" notifications@github.com wrote:

OK. I will work on modifying the Python code for SIP to try and get it to work with the Orange Pi. You will need to install a Python GPIO library on your Orange Pi. Follow the instructions for "installing Python and Libraries" at: https://diyprojects.io/orange-pi-onelite-tutorial-use-gpio-p ython-pinouts/#.WTNH09y1sdU

Sip should be installed into a directory named "pi". Does your Orange Pi have a pi directory? I don't have an Orange Pi so I will probably ask a few questions like that.

According to the time stamp on your previous post it looks like your local time is about 12 hours and 45 minutes ahead of the time here in California. You must be on the other side of the world.

Dan

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306008471, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIoA2sRi4N9GUwJt1m33giFqoWMaxks5sAfI5gaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

Riaan, It would be best to make a directory /home/pi and place SIP there. There is a script that is used to start SIP automatically after a reboot that looks for that location.

I will make some code changes in a branch of the SIP repository so you will need to clone a fresh version when that is ready.

Dan

Riaan111209 commented 7 years ago

Hi Dan Thank you for the reply. If I open the file manager then I am inside root. Do you want me to make a new folder inside root with the name 'pi' and the put the SIP folder inside it or does it look for "home" as well.

Kind Regards Riaan

On 04 Jun 2017 17:18, "Dan" notifications@github.com wrote:

Riaan, It would be best to make a directory /home/pi and place SIP there. There is a script that is used to start SIP automatically after a reboot that looks for that location.

I will make some code changes in a branch of the SIP repository so you will need to clone a fresh version when that is ready.

Dan

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306046497, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIvGL-hZwJHQ-k0bBIBrM5KY_If7qks5sAsrSgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

The script looks for /home/pi so you should make a home directory with a pi sub directory and place SIP there.

Riaan111209 commented 7 years ago

Thank you. I thought that might be the case. I will do that and then see if it will run.

Kind Regards Riaan

On 04 Jun 2017 18:17, "Dan" notifications@github.com wrote:

The script looks for /home/pi so you should make a home directory with a pi sub directory and place SIP there.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306049976, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIuvGWFNMzFmSq4Ey9ywIq5PxC6Zpks5sAth-gaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

I don't think it will run yet. I am working on the code modification but it may take a while.

Did you install the orangepi_PC_gpio_pyH3 Python library? That will need to be ready on your system before SIP can be used.

Riaan111209 commented 7 years ago

I tried to install the python library fot gpio as you suggested but it does not work. I am downloading a different operating system to see if I can get it done.

On 04 Jun 2017 18:31, "Dan" notifications@github.com wrote:

I don't think it will run yet. I am working on the code modification but it may take a while.

Did you install the orangepi_PC_gpio_pyH3 Python library? That will need to be ready on your system before SIP can be used.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306050837, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIuiDSgBPkTLyow9wuu1i1dK7pPLBks5sAtvmgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

I pushed a new branch named "orange" to the SIP repository. When you are ready to test SIP use git checkout orange form the command line in the SIP directory. That should switch to the new branch.

The orange branch has a modified version of gpio_pins.py that should work with the orange pi as long as the Python GPIO library is installed. I don't have a way to actually test this but it runs on my Raspberry Pi test rig so I don't see any major problems.

Riaan111209 commented 7 years ago

Thank you very much Dan. I appreciate your help and support. I will give you another reply when I have the new OS loaded.

Kind Regards Riaan.

On 04 Jun 2017 19:23, "Dan" notifications@github.com wrote:

I pushed a new branch named "orange" to the SIP repository. When you are ready to test SIP use git sheckout orange form the command line in the SIP directory. That should switch to the new branch.

The orange branch has a modified version of gpio_pins.py that should work with the orange pi as long as the Python GPIO library is installed. I don't have a way to actually test this but it runs on my Raspberry Pi test rig so I don't see any major problems.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306053984, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIpzXQmkxfMho7Aq5DEI_F7TqgSjQks5sAugUgaJpZM4NvE98 .

Riaan111209 commented 7 years ago

Good morning Dan The link for the duxing gpio library is not working. It gives me a 403 url error.

When I run the python dev install it said that the newest version is already installed.

I will try and put SIP on and let you know from there.

Kind Regards Riaan

On 04 Jun 2017 19:26, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Thank you very much Dan. I appreciate your help and support. I will give you another reply when I have the new OS loaded.

Kind Regards Riaan.

On 04 Jun 2017 19:23, "Dan" notifications@github.com wrote:

I pushed a new branch named "orange" to the SIP repository. When you are ready to test SIP use git sheckout orange form the command line in the SIP directory. That should switch to the new branch.

The orange branch has a modified version of gpio_pins.py that should work with the orange pi as long as the Python GPIO library is installed. I don't have a way to actually test this but it runs on my Raspberry Pi test rig so I don't see any major problems.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306053984, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIpzXQmkxfMho7Aq5DEI_F7TqgSjQks5sAugUgaJpZM4NvE98 .

Riaan111209 commented 7 years ago

At the moment The SIP folder is in the following directory way /root/home/pi/SIP I had to create the home and the pi folder because it installs the SIP folder directly into root

The sip.py will not run.

On 05 Jun 2017 05:27, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Good morning Dan The link for the duxing gpio library is not working. It gives me a 403 url error.

When I run the python dev install it said that the newest version is already installed.

I will try and put SIP on and let you know from there.

Kind Regards Riaan

On 04 Jun 2017 19:26, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Thank you very much Dan. I appreciate your help and support. I will give you another reply when I have the new OS loaded.

Kind Regards Riaan.

On 04 Jun 2017 19:23, "Dan" notifications@github.com wrote:

I pushed a new branch named "orange" to the SIP repository. When you are ready to test SIP use git sheckout orange form the command line in the SIP directory. That should switch to the new branch.

The orange branch has a modified version of gpio_pins.py that should work with the orange pi as long as the Python GPIO library is installed. I don't have a way to actually test this but it runs on my Raspberry Pi test rig so I don't see any major problems.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306053984, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIpzXQmkxfMho7Aq5DEI_F7TqgSjQks5sAugUgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

How are you trying to start SIP? Using the command line from in the SIP directory it should be: sudo python sip.py Do you see any error message?

Riaan111209 commented 7 years ago

Hi Dan I use the LX terminal Following: cd /home/pi/SIP Then sudo python sip.py

Then there is a few errors and the last line tell me that this will only run on a raspberry pi.

My OS is rasbian for orange pi one

On 05 Jun 2017 05:51, "Dan" notifications@github.com wrote:

How are you trying to start SIP? Using the command line from in the SIP directory it should be: sudo python sip.py Do you see any error message?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306097306, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIg5NseS-UPlZdiZ0XJfoEiNvpjm5ks5sA3s2gaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

That is strange. SIP does not print a message that it will only run on a Raspberry Pi. In fact SIP does also run on Beagle Bone and I have even run it on Windows. The only time I have seen that message is if I try to load the RPi.GPIO library on a non-Raspberry Pi system.

Try running the command "git branch" in the SIP directory. You should get a reply of "orange", If it returns "master" use the command "sudo git checkout orange" That should change to the code modified for Orange Pi. If you are on the orange branch and still get the message that it will only run on a Raspberry Pi I will make some further changes to the code to eliminate any reference to RPi.GPIO.

Also, it would be helpful to know what other error messages you get when you try to tun SIP. That would help figure out what is happening.

Riaan111209 commented 7 years ago

Hi Dan Thank you. I will try that in about 30minutes. If it give me all the errors then I will type everything in a message. It would be easier to send a picture but the servers reject my email if a picture is attached. Will let you know. Thanks

Kind Regards Riaan

On 05 Jun 2017 17:44, "Dan" notifications@github.com wrote:

That is strange. SIP does not print a message that it will only run on a Raspberry Pi. In fact SIP does also run on Beagle Bone and I have even run it on Windows. The only time I have seen that message is if I try to load the RPi.GPIO library on a non-Raspberry Pi system.

Try running the command "git branch" in the SIP directory. You should get a reply of "orange", If it returns "master" use the command "sudo git checkout orange" That should change to the code modified for Orange Pi. If you are on the orange branch and still get the message that it will only run on a Raspberry Pi I will make some further changes to the code to eliminate any reference to RPi.GPIO.

Also, it would be helpful to know what other error messages you get when you try to tun SIP. That would help figure out what is happening.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306215683, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIhZgpdRixaePklljpNjM4WrIzKceks5sBBxygaJpZM4NvE98 .

Riaan111209 commented 7 years ago

Okey Dan It replied * master I did as you said and then I got the message:

Branch orange set up to track remote branch orangefrom origin. Switched to a new branch 'orange'

I then run the following: root@orangepi:~/home/pi/SIP# sudo python sip.py

This is the terminal display after that command: BAPI: revision(-1) Trackback (most recent call last):

I hope this give you a better idea as to what is going on here at my side.

Kind Regards

On 05 Jun 2017 18:23, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Hi Dan Thank you. I will try that in about 30minutes. If it give me all the errors then I will type everything in a message. It would be easier to send a picture but the servers reject my email if a picture is attached. Will let you know. Thanks

Kind Regards Riaan

On 05 Jun 2017 17:44, "Dan" notifications@github.com wrote:

That is strange. SIP does not print a message that it will only run on a Raspberry Pi. In fact SIP does also run on Beagle Bone and I have even run it on Windows. The only time I have seen that message is if I try to load the RPi.GPIO library on a non-Raspberry Pi system.

Try running the command "git branch" in the SIP directory. You should get a reply of "orange", If it returns "master" use the command "sudo git checkout orange" That should change to the code modified for Orange Pi. If you are on the orange branch and still get the message that it will only run on a Raspberry Pi I will make some further changes to the code to eliminate any reference to RPi.GPIO.

Also, it would be helpful to know what other error messages you get when you try to tun SIP. That would help figure out what is happening.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306215683, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIhZgpdRixaePklljpNjM4WrIzKceks5sBBxygaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

Yes, That tells me a lot.

First, you need to actually cd into the /home/pi/SIP directory before you try to start SIP. That is what I meant by "from the SIP directory". SIP uses relative paths to load it's Python modules and if you try to start sip.py from a different directory they will not load. That is what is causing the first few errors.

You mentioned that your OS is rasbian for orange pi one. That gives me a clue abut the error that comes right after "Import RPi.GPIO as GPIO". It looks like whoever modified Rsapbian (the official OS for Raspberry Pi) for use on the Orange Pi forgot to remove the Python RPi.GPIO library. It should not exist on a non-Raspberry Pi system. SIP will try to load that library and if it is not found SIP will try to to load a different library or it will print a message that no GPIO library was fund and continue to run. In this case SIP finds the RPi.GPIO library and tries to run it causing an error that SIP is not prepared to handle.

Try looking in /usr/lib/python2.7/dist-packages and see if there is a folder named RPi. If it is there delete it. That should get rid of the error and allow SIP to run.

Riaan111209 commented 7 years ago

Thank you for the reply. This is the following I did.

root@orangepi:~# cd /usr/lib/python2.7/dist-packages Then I put 'dir' to get the following:

dbus pifacecommon-r.0.0.egg-info _dbus_bindings.so pifacedigitalio _dbus_glib_bindings.so. pifacedigitalio-3.0.4-info debconf.py pygame debconf.pyc pygame-1.9.1release.egg-info gi pyserial-2.5.egg-info picamera python-support.pth picamera-1.6.egg-info README pifacecommon serial

root@orangepi:/usr/lib/python2.7/dist-packages#

On 05 Jun 2017 21:36, "Dan" notifications@github.com wrote:

Yes, That tells me a lot.

First, you need to actually cd into the /home/pi/SIP directory before you try to start SIP. That is what I meant by "from the SIP directory". SIP uses relative paths to load it's Python modules and if you try to start sip.py from a different directory they will not load. That is what is causing the first few errors.

You mentioned that your OS is rasbian for orange pi one. That gives me a clue abut the error that comes right after "Import RPi.GPIO as GPIO". It looks like whoever modified Rsapbian (the official OS for Raspberry Pi) for use on the Orange Pi forgot to remove the Python RPi.GPIO library. It should not exist on a non-Raspberry Pi system. SIP will try to load that library and if it is not found SIP will try to to load a different library or it will print a message that no GPIO library was fund and continue to run. In this case SIP finds the RPi.GPIO library and tries to run it causing an error that SIP is not prepared to handle.

Try looking in /usr/lib/python2.7/dist-packages and see if there is a folder named RPi. If it is there delete it. That should get rid of the error and allow SIP to run.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306281180, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIhQrohGIpDM1E1KRcwKI7WyKhq77ks5sBFihgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

OK. Looks like RPi is not in that directory but it must be somewhere.

Try: find / -name RPi

Riaan111209 commented 7 years ago

Good morning Dan If I type sudo find / RPI then it run the search and end with the following line: find: 'RPI': No such file or directory

On 05 Jun 2017 22:23, "Dan" notifications@github.com wrote:

OK. Looks like RPi is not in that directory but it must be somewhere.

Try: find / -name RPi

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306294427, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIoWxEP8YR7Op56W3jNKNOcyqpIBEks5sBGPJgaJpZM4NvE98 .

Riaan111209 commented 7 years ago

Hi Dan For which orange pi OS did you test your system? I might be a good idea for me to load the same operating system and start again.

Kind Regards

On 06 Jun 2017 05:58, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Good morning Dan If I type sudo find / RPI then it run the search and end with the following line: find: 'RPI': No such file or directory

On 05 Jun 2017 22:23, "Dan" notifications@github.com wrote:

OK. Looks like RPi is not in that directory but it must be somewhere.

Try: find / -name RPi

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306294427, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIoWxEP8YR7Op56W3jNKNOcyqpIBEks5sBGPJgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

When I try "find / RPi" it returns "RPI': No such file or directory" but when I try "find / -name RPi" with the -name switch it finds it.

I am running the latest Raspi for Raspberry Pi so it might not work on an Orange Pi.

I will try to eliminate the import of RPi.GPIO in the orange branch. That should eliminate the error. I will let you know when the update is ready.

Riaan111209 commented 7 years ago

Hi Dan Thank you. It will be very nice if I can run the SIP on the orange pi one. Very kind of you to go through all the effort.

Kind Regards Riaan

On 06 Jun 2017 17:10, "Dan" notifications@github.com wrote:

When I try "find / RPi" it returns "RPI': No such file or directory" but when I try "find / -name RPi" with the -name switch it finds it.

I am running the latest Raspi for Raspberry Pi so it might not work on an Orange Pi.

I will try to eliminate the import of RPi.GPIO in the orange branch. That should eliminate the error. I will let you know when the update is ready.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306517050, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIrZPMRhZHnsj4St0Rh_yoRWOg2Vyks5sBWvZgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

I pushed an update to GitHub with the references to RPi.GPIO removed. You can get the update by cd to /home/pi/SIP and use the command sudo git pull That should eliminate the error and allow SIP to run.

Once SIP is running use a web browser on your network to go to the URL of your Oange Pi. When you see the SIP login screen use the password "opendoor".

Riaan111209 commented 7 years ago

Hi Dan I am reloading a new memorycard for the orange pi. Which operating system do you think should work best with your system on the orange pi and all the updates and changes that you made?

On 06 Jun 2017 18:16, "Dan" notifications@github.com wrote:

I pushed an update to GitHub with the references to RPi.GPIO removed. You can get the update by cd to /home/pi/SIP and use the command sudo git pull That should eliminate the error and allow SIP to run.

Once SIP is running use a web browser on your network to go to the URL of your Oange Pi. When you see the SIP login screen use the password "opendoor".

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306538103, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIsgfS_gre_DZ7xmLUG8_8Kipllymks5sBXtMgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

Because I don't have an Orange Pi, I can't say which OS euld be best.

Riaan111209 commented 7 years ago

Okey thank you. I will put debian back and start again.

On 06 Jun 2017 22:04, "Dan" notifications@github.com wrote:

Because I don't have an Orange Pi, I can't say which OS euld be best.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306601008, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIvVx3okJq1CRXsWtCs3xi2oIdXSFks5sBbDPgaJpZM4NvE98 .

Riaan111209 commented 7 years ago

Good morning Dan Will I be able to use a arad irt 100 flow meter with SIP to monitor the amount of water flow?

On 06 Jun 2017 22:15, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Okey thank you. I will put debian back and start again.

On 06 Jun 2017 22:04, "Dan" notifications@github.com wrote:

Because I don't have an Orange Pi, I can't say which OS euld be best.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306601008, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIvVx3okJq1CRXsWtCs3xi2oIdXSFks5sBbDPgaJpZM4NvE98 .

Riaan111209 commented 7 years ago

Hi Dan. I think I need to try this with a raspberry pi first. Reason for this is that I need to install the system on the farm at the end of the month so I am running out of time. When I am back from the farm, I will then try again with the orange pi one at my house in town. I am building a relay board with the shift registers today to be able to switch all the relays for the valves. How does the SIP program with the raspberry pi 3 work with the shift registers?

Kind Regards Riaan

On 08 Jun 2017 07:03, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Good morning Dan Will I be able to use a arad irt 100 flow meter with SIP to monitor the amount of water flow?

On 06 Jun 2017 22:15, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Okey thank you. I will put debian back and start again.

On 06 Jun 2017 22:04, "Dan" notifications@github.com wrote:

Because I don't have an Orange Pi, I can't say which OS euld be best.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-306601008, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIvVx3okJq1CRXsWtCs3xi2oIdXSFks5sBbDPgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

regarding the flow meter see issue 143 https://github.com/Dan-in-CA/SIP/issues/143 another contributor is developing a flow meter plugin for SIP.

If you follow the plan on the SIP wiki for the shift register set up it will work with SIP's native code and no plugin is required.

Riaan111209 commented 7 years ago

Hi Dan Thank you for the reply. I hope I can get this working well. My goal is still to make this work on the orange pi. Time is just catching me and I am not an expert like you so for me this take a lot of time.

On 08 Jun 2017 18:51, "Dan" notifications@github.com wrote:

regarding the flow meter see issue 143

143 https://github.com/Dan-in-CA/SIP/issues/143

another contributor is developing a flow meter plugin for SIP.

If you follow the plan on the SIP wiki for the shift register set up it will work with SIP's native code and no plugin is required.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-307162582, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIpPz8yRFfisn4sHQ-8rAoRYIf5Ltks5sCCaMgaJpZM4NvE98 .

Riaan111209 commented 7 years ago

Hi Dan I am starting to feel stupid because I can not even get SIP to work on a raspberry pi 3. I installed the SIP and I can open it by running the command Sudo python sip.py

I built the shift register board as per the fritzing drawing on your github but the relay only switch on channel 1. In the Terminal I can see the change from 0 to 1 on all the chanels if I switch them on. But that is not what is happening with the relays.

Kind Regards

On 08 Jun 2017 18:51, "Dan" notifications@github.com wrote:

regarding the flow meter see issue 143

143 https://github.com/Dan-in-CA/SIP/issues/143

another contributor is developing a flow meter plugin for SIP.

If you follow the plan on the SIP wiki for the shift register set up it will work with SIP's native code and no plugin is required.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-307162582, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIpPz8yRFfisn4sHQ-8rAoRYIf5Ltks5sCCaMgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

Not sure why that would be. Check the wiring very carefully. What kind of relays are you using?

Riaan111209 commented 7 years ago

I have a 16ch relay module low level trigger.

On 09 Jun 2017 17:45, "Dan" notifications@github.com wrote:

Not sure why that would be. Check the wiring very carefully. What kind of relays are you using?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-307425214, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIg6ntB53qPTG4DQntn8xr7KFPx5rks5sCWiugaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

The low level trigger is a problem with this set up. I have been working on a solution. There is a setting under "Station Handling" on the SIP Options page named "Active-Low Relay" That check box should be checked.

The relays will all turn on when the system is starting up but should work properly once it is booted up.

Dan-in-CA commented 7 years ago

I found a fix for the problem of the low level trigger relays switching on during power up. You need to add a 10K Ohm resistor between the wire from pin 11 and the 5v line from the Pi.

If you check the "acrive-low relay box on the SIP options page as described above, and and add the resistor to the shift register circuit your relay board should work without a problem.

Riaan111209 commented 7 years ago

Hi Dan Thank you for the info. In your github about the auto restart where you explain how to copy the sip.service, i get an error and it will not copy. I also saw that for some reason my OS have 2 main directories. The one is "pi" and the other one is "/". The SIP is installed on "pi" and the systemd is on "/".

How can this work?

Once again thank you for all the help and support.

Kind Regards Riaan

On 10 Jun 2017 18:06, "Dan" notifications@github.com wrote:

I found a fix for the problem of the low level trigger relays switching on during power up. You need to add a 10K Ohm resistor between the wire from pin 11 and the 5v line from the Pi.

If you check the "acrive-low relay box on the SIP options page as described above, and and add the resistor to the shift register circuit your relay board should work without a problem.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-307574242, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIjN0xMz8Kyl0LAv9g8smakaI9Wb6ks5sCr8HgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

The "pi" directory is the home directory for the user "pi'. When you log in as pi you will be placed in that dir. the "/" directory is the root directory. If you make changes to the / directory you must be "root" or use "sudo" when running a command.

What version of the OS are you running? You can get the version with: lsb_release -a or cat /etc/*-release

Dan

Riaan111209 commented 7 years ago

I typed lsb_release -a Then I got this No lsb modules are available. Distributor ID: Raspbian Discription: Raspbian GNU/Linux 8.0 (jessie) Release: 8.0 Codename: jessie

When i type cat /etc/-release Then i get this PRETTY_NAME="Raspbian GNU/Linux 8.0 NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian*

On 10 Jun 2017 21:08, "Dan" notifications@github.com wrote:

The "pi" directory is the home directory for the user "pi'. When you log in as pi you will be placed in that dir. the "/" directory is the root directory. If you make changes to the / directory you must be "root" or use "sudo" when running a command.

What version of the OS are you running? You can get the version with: lsb_release -a or cat /etc/*-release

Dan

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-307584482, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIoywSb9FUKMA_iDaCEa15-HDhjmpks5sCum7gaJpZM4NvE98 .

Riaan111209 commented 7 years ago

Hi Dan I manage to select the low level trigger as you said. I got the relays to switch but they are not reacting to the command. If i switch station one the it will switch 2 relays on. If I select station 2 then it will switch another 2 on. If I switch station 1 off then it will switch 3 relays off. This is a bit strange but at leasts I am moving a bit forward with this project. I also loaded a new OS this afternoon "pixel with raspbian" this seem to be more stable. I am using 74HC595N shift registers.

On 11 Jun 2017 09:05, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

I typed lsb_release -a Then I got this No lsb modules are available. Distributor ID: Raspbian Discription: Raspbian GNU/Linux 8.0 (jessie) Release: 8.0 Codename: jessie

When i type cat /etc/-release Then i get this PRETTY_NAME="Raspbian GNU/Linux 8.0 NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian*

On 10 Jun 2017 21:08, "Dan" notifications@github.com wrote:

The "pi" directory is the home directory for the user "pi'. When you log in as pi you will be placed in that dir. the "/" directory is the root directory. If you make changes to the / directory you must be "root" or use "sudo" when running a command.

What version of the OS are you running? You can get the version with: lsb_release -a or cat /etc/*-release

Dan

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-307584482, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIoywSb9FUKMA_iDaCEa15-HDhjmpks5sCum7gaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

Sounds like you are making progress. I have not seen the situation where more than one station is switched on unless you have a master station selected on the Options page or the system is set for concurrent mode.

Did you also add the 10k Ohm resistor to the shift register circuit? The diagram for the shift registers has been updated today to include the resistor.

Riaan111209 commented 7 years ago

Hi Dan. I still need to put the resisters on my circuit. Will do that this morning and try again. Then I still need to do the rc.local to make it start automatic when the power is cycled.

On 12 Jun 2017 00:58, "Dan" notifications@github.com wrote:

Sounds like you are making progress. I have not seen the situation where more than one station is switched on unless you have a master station selected on the Options page or the system is set for concurrent mode.

Did you also add the 10k Ohm resistor to the shift register circuit? The diagram for the shift registers has been updated today to include the resistor.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-307662666, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIhJ5ulBKvh4YvW_pXEjtkDKEungHks5sDHEBgaJpZM4NvE98 .

Riaan111209 commented 7 years ago

Hi Dan If I put the 10kohm resister as per your drawing the nothing will switch on or off. I have another question: Will it be possible to connect a arduino mega to the pi3 to let the mega do the switching of the pins/relays?

On 12 Jun 2017 05:22, "Riaan Engelbrecht" riaan.eng@gmail.com wrote:

Hi Dan. I still need to put the resisters on my circuit. Will do that this morning and try again. Then I still need to do the rc.local to make it start automatic when the power is cycled.

On 12 Jun 2017 00:58, "Dan" notifications@github.com wrote:

Sounds like you are making progress. I have not seen the situation where more than one station is switched on unless you have a master station selected on the Options page or the system is set for concurrent mode.

Did you also add the 10k Ohm resistor to the shift register circuit? The diagram for the shift registers has been updated today to include the resistor.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-307662666, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIhJ5ulBKvh4YvW_pXEjtkDKEungHks5sDHEBgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

Did you also check the "Active-low relay" box under "station handling' on the SIP Options page. Other users have it working with low level trigger relay boards.

It may be possible to use an Arduino to control the relays but you will need to write some arduino code.

Riaan111209 commented 7 years ago

Hi Dan. Yes the box is checked for low voltage relay board. I will try again this afternoon again. I will build the shift register on a breadboard and try again.

On 13 Jun 2017 16:36, "Dan" notifications@github.com wrote:

Did you also check the "Active-low relay" box under "station handling' on the SIP Options page. Other users have it working with low level trigger relay boards.

It may be possible to use an Arduino to control the relays but you will need to write some arduino code.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-308137278, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIsqXDljsD5aD2VxMYMfxNic_mNKWks5sDp6CgaJpZM4NvE98 .

Dan-in-CA commented 7 years ago

It is always good to start with a breadboard. Once you have everything working you can move the circuit to a more permanent support or you can leave it on the breadboard.

Riaan111209 commented 7 years ago

Will not be able to leave it on the breadboard. Not reliable enough as the farm is 2000km from me. Will let you know what happen.

On 14 Jun 2017 16:43, "Dan" notifications@github.com wrote:

It is always good to start with a breadboard. Once you have everything working you can move the circuit to a more permanent support or you can leave it on the breadboard.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dan-in-CA/SIP/issues/189#issuecomment-308453690, or mute the thread https://github.com/notifications/unsubscribe-auth/ARRkIprcHxvqJnDIOMGoAaDIRSn_Qv_eks5sD_GjgaJpZM4NvE98 .