Forum Replies Created
-
AuthorPosts
-
SeanParticipantYup, explains a lot.
I’ll not wipe and reinstall tomorrow and will just let it run.
Thanks for your work and dedication. Now..
Get some sleep. 🙂
SeanParticipantDumped the browser cache, opened SSH to OSPi and repeated the update steps (3 files changed) including restart of the app, browsed to OSPi from my Mac’s Safari…
The configuration was not erased and the location still says Colorado, USA. Also, GPS coordinates do not display on the map or anywhere else.
I am done for the night. I would like to completely remove OSPi from the Pi and reinstall from scratch in the morning. Can you point me at the best method of doing this?
SeanParticipantThe Web UI from my Mac failed the same way at first.
In Safari on OS X 10.10.5 the location in the System section said Colorado, USA instead of Loveland, Colorado or the station name.
Clicked the location field and was presented with a map that had only one pin (in red) this was the location of my house. No other pins displayed. moving or resizing had no effect.
At this point I clicked the Submit button in the detail bubble that was attached to the one red pin then, without clicking the Submit button on the main options screen, clicked the location field once again.
YAY! The map now displayed the blue weather station icons. I repeated this three times (each without clicking Submit in the main options screen and got the same result each time.
Then, I went back and did it a fourth time but this time selected the closest station to my home and clicked its Submit button, then clicked the submit button on the Options screen, saving the settings.The location still says Colorado, USA, not the station ID as It used to. But now, when I click the location field (still from my Mac) it shows all the weather station pins with the nearest one selected.
How do I verify that the correct station is configured? Will it ever display the weather station ID in the location field again?
Edit:
Was testing and typing when your reply above came in and didn’t see it. Do you still want me to test the demo site?
SeanParticipantThe web UI on an iPad has the same symptoms as the IOS app. Trying my Mac now.
SeanParticipantI am using the IOS app on an old iPad with current OS.
Moving or resizing the map does not cause stations to appear. I have also tried deleting the WU key, saving, re-entering, saving. No change. I will try the web UI next.
Re the warning of the configuration wipe:
I was also using the IOS app. I saw the notification icon in the upper right, clicked it, saw the notice of an update with a link to help. Clicked the link and a window popped up that had the content from this link in it (I think)
https://opensprinkler.freshdesk.com/support/solutions/articles/5000631599-installing-and-updating-the-unified-firmwareNowhere in the text did I see the warning. Still don’t. I understand that I may only be seeing what I expect to see, so don’t think that I will be insulted if you point out what is in front of my nose.
SeanParticipantI do have an API key set. But the location map does not show any stations. I will try zooming out to see if any are shown within a 10 mile radius. There should be at leSt twenty.
Regarding the note in the update notice, I did not see it.
SeanParticipantFound the default password and imported an old program so we are back up.
One thing I noticed is that the location now says Loveland, Co. It used to say KCOLOVEL23 which is the local weather underground station. When I tape the change location bar, I get a map with no weather underground stations on it. How do I get the local station endeared?
SeanParticipantLooks like the update blew away my configuration. Frustrating.
I am now looking for the default password so I can recover to the last back up.
SeanParticipantWell, that was easy. Thanks Samer!
SeanParticipantYes. The transmitter works from the RFToy using the codes that I recorded with it.
I input these codes as names into stations. I have tried both low number stations and high number stations.
I connect the the transmitter’s data to GPIO18, set RF Data to 18 in Defines, save, recompile and reboot . Fail.
Repeat the above except move the data connection to GPIO15, setting rf data in defines to 15. Fail, with an added buzz from the relay.
Updated the firmware from 2.1.3 to 2.1.4, retested. Fail.
Move the transmitter back to the RFToy and it still works.
SeanParticipantRay thanks for your help. But…
I’m done
I moved the transmitter data to GPIO15 and recompiled/rebooted. Nothing but relay noise. The transmitter is not being fed a signal that it can use.
I tried a get pull and rebuild/reboot. Same. Nada.
The only conclusion I can come to is that OSPi 1.4 with Raspberry Pi2 using either 2.1.3 or 2.1.4 does not drive the RF transmitted from your store.
SeanParticipantI’ll try GPIO15. Then de-soulder the relay if it works.
In the meantime, can you post all the GPIO that are unused?
SeanParticipantTwo things:
1) Are there GPIO pins you are not using other than 18? If it is not in the section that you pointed me to in the defines.h file can i assume that I can try the transmitter data there?
2) There seems to have bee several changes to the P1 pinout for the new Raspberry Pi 2. There is a discussion HERE and a detailed explanation HERE. This is over my head, so I hope you can make sense of it. Could these be related to my issue?
SeanParticipantreconnected the transmitter to the RFToy and verified that it works.
So, it looks like there is an issue with my OSPi.
Hardware:
OSPi controller version 1.4
Two extension modules
Raspberry Pi 2 model B
Two Netgear Powerline 500 ethernet adaptersSoftware:
Noobs version 1.4.0
OSPi firmware version 2.1.3
SeanParticipantIn the 2.1.3 version of firmware, there is a setting called “Activate Relay” that (I think) will do this. You can find it in each station’s definition window.
SeanParticipantNo joy.
changed the rf data pin definition back to 18 and recompiled. The rftoy picks up no signal.
I wonder if I fried the transmitter when I connected it to the OSPI?
The next thing I’ll try is removing the extension wires from the transmitter, cleaning off the pins and plugging it back into the rftoy to see if it still turns on the rf outlets.
SeanParticipantOK, I changed the pin definition back to 15. There is noise from the relay.
The names are 16 digit hex. Here are the names:
“51153351153C00C0″,”5115C35115CC00C0″,”51170351170C00C0″,”511D03511D0C00C0″,”51350351350C00C0”
The unit has an extension module that was not connected during this test.
The RF stations are numbers 41 through 45.
The next thing I am going to try is defining one of the first 8 zones as a transmitter.
SeanParticipantConnections are good.
4.92 VDC to GND at the transmitter, not polarity reversed.
No signal detected by the RFToy.
Have not tried the speaker trick.
The time stamp of the opensprinkler file agrees with when I compiled it.
Still no workie
I wonder if I fried the transmitter. I’ll try it in the RFtoy tomorrow.
Other than that one change in defines.h, was there anything else in the 2.1.3 code that deeded changing?
SeanParticipantNo signal. So, I will dig out my kit and find out where I went wrong.
Thanks again.
SeanParticipantBrilliant idea!
I’ll try it tonight.
SeanParticipantWell I made the change to defines.h (see attached) and recompiled. I connected the transmitter properly (I think).
I captured and tested the transmitter codes. They work if transmitted by the RFToy.
I configured the station names to match the transmitter codes (see attached).
Still, it does not work.
My first assumption is that I crossed wires connecting eh transmitter. I will check that. while I do, Can you teak me if I have the right firmware? Is there something else I should check?
App Version: 1.4.1
Hardware version OSPi 1.4
Firmware Version 2.1.3.Attachments:
SeanParticipantNever mind.
I confused myself. I assumed that GPIO18 would be on pin 18 of the GPIO connector.
I just looked at the Raspberry Pi v2 pinout and learned that GPIO18 is actually on pin 12, not pin 18.
Last question, Will I need to modify and recompile each time a new version of firmware comes out?
SeanParticipantI’ll try that, thanks.
Befor I do, could you clarify something?
I did a quick continuity check based on your illustration and found that my GPIO pin 18 does not seem to match the illustration you provided. I could easily have counted the pins wrong though.
On the reverse side of the board, is the pin I have circled in red in Pic1.png actually GPIO pin 18?
If so…
On my board, that pin has continuity to the contact that I have circled in blue in Pic2.png.
Did I get this wrong?
SeanParticipantAssuming that A3 is the same on the microcontorller-based OpenSprinkler and the OSPi board, I am going to connect the RF transmitter to my OSPi per the attached image and hope that it doesn’t fry something when I apply power.
Attachments:
SeanParticipantMy OSPi is still in pieces on the kitchen table waiting for an answer to my original question.
If anyone here has successfully connected an RF transmitter to an OSPi Plus, could you speak up and tell me how the connection is made?
-
AuthorPosts