WP problems

ssmall · January 29, 2016, 03:06:19 PM

I have 6 nodes around the house and all of them use ATC extension to the library. I am able to WP all of my non-battery powered nodes. Up until a few days ago I have used the python script to do this. Once I saw the latest post on increasing the speed of WP, I couldn't resist and tried the latest version of the WP GUI. I failed on my first attempt to use the WP GUI because I didn't update the WirelessHEX libraries. Once I upgraded the libraries, and recompiled the sketches I was bale to get the WP to work. I had to use the slowest option at first because the node had the old version of the WirelessHex library. I upgraded it a second time using the fastest option and that worked as well.

Hope this helps

Felix · January 29, 2016, 03:59:26 PM

Thanks steve for taking the time to upgrade and verifying it works

mzv72m · January 29, 2016, 05:49:13 PM

I got it to work with the example node sketch both with and without ATC.

Now I need to try my sketch for the node and hopefully it works. If it does then it was just a mismatch with the libraries/code.

Everything works!!! Yea!!!!

I must have had something out of sync

Thanks Felix for putting up with someone new to the WP process.

Mobsens · January 30, 2016, 04:30:57 AM

QuoteAgain here is the changeset that added support for the 50% WP speed increase. Ensure you have this lib running in your IDE.

For many it can be difficult to have to compare the sourcecodes to find out if you are using the right version.
Why not adding the time for latest update and version no in the first lines of the sourcecomments.

Felix · January 30, 2016, 08:26:24 AM

I completely agree versioning would make things a little more clear.
I already had this in mind, but I have to figure out what's truly the best way to do it, such that I won't miss changing the versions when I do an update. Sometimes a code change is so minor it does not deserve a version change, perhaps a minor version should increase only. Once i start versioning I cannot stop

, yet another thing to worry about.

Westy87 · January 30, 2016, 11:53:39 AM

Quote from: Westy87 on January 28, 2016, 10:56:19 PM
OK I followed the instructions to upgrade speed to 3 HEX file lines per RF packet :
1. Updated WirelessHEX69 lib (I'm using Codebender, so to be double sure, I put latest WirelessProgramming.zip into "Personal Libraries"
2.Uploaded latest WirelessProgramming_gateway sketch to Moteino GW (making sure that IMPORTANT SETTINGS are matched! )
3. Downloaded Wireless Programming GUI app v1.3

I get successful OTA/WP uploads at 1 line per packet only. 2lpp and 3lpp give me OUT OF SYNC: retrying...errors
Obviously, I've done something incorrectly.
Any ideas?

I finally got 3x speed to work. The issue was I uploaded a zipped version of WirelessProgramming folder to Codebender Personal Libraries. Turns out when I replaced that with WirelessHex69 codebender finds it. I reckon the original problem was Codebender didn't find the library in my Personal Libraries,so it used the outdated builtin library.

By the way Felix, is Lowpower labs no longer supporting the Codebender built-in libraries? I really like Codebender vs the Arduino IDE...

Felix · January 30, 2016, 05:00:54 PM

I like codebender for several reasons but unfortunately I cannot support any 3rd party tools if it means I have to spend the time pushing my changes to them myself every time there is a change. Just doesn't work like that.

syrinxtech · January 31, 2016, 08:55:38 AM

Quote from: Felix on January 30, 2016, 08:26:24 AM
I completely agree versioning would make things a little more clear.
I already had this in mind, but I have to figure out what's truly the best way to do it, such that I won't miss changing the versions when I do an update. Sometimes a code change is so minor it does not deserve a version change, perhaps a minor version should increase only. Once i start versioning I cannot stop , yet another thing to worry about.

Felix,

Speaking only for myself, I think versioning has caused more problems for me than all other dumb mistakes combined. I think it would extremely helpful to have a version ID on every piece of code, script, etc. that comes out. Something like the following:

Major.Minor.Patch = 1.0.1

or

Major.Minor.Patch(sequence) = 1.0.1(a)

Also, it would be extremely helpful to have on the main Github page a chart showing the latest version for each of the various software packages. Alternatively, you could have just the latest version of each package on it's individual Github page.

Yes, I know it's a lot of work and generally a PITA. I do think it would help not only the noobies but also those folks that come from a more regimented coding background where version control is a much more invasive part of the programming process.

Felix · February 01, 2016, 08:47:18 AM

I could not agree more but since I only have 24h in a day, with too many responsibilities to list here, it sounds like I would need another staff/partner to manage all that

I think the overall gain from all this WP related updating/upgrading should be in the positive. Meaning, more WP speed, nicer GUI with more features etc.
Once people sync up their sources and the GUI and it starts to work, the pain will start to go away, i guess it's one of the gotchas that come with my freebie no strings attached software. I hope that's not perceived as a lame "leave me alone" answer. I will consider versioning for sure though. Thank you all for the feedback and understanding.

syrinxtech · February 01, 2016, 08:41:46 PM

Quote from: Felix on February 01, 2016, 08:47:18 AM
I could not agree more but since I only have 24h in a day, with too many responsibilities to list here, it sounds like I would need another staff/partner to manage all that
I think the overall gain from all this WP related updating/upgrading should be in the positive. Meaning, more WP speed, nicer GUI with more features etc.
Once people sync up their sources and the GUI and it starts to work, the pain will start to go away, i guess it's one of the gotchas that come with my freebie no strings attached software. I hope that's not perceived as a lame "leave me alone" answer. I will consider versioning for sure though. Thank you all for the feedback and understanding.

If you figure out how you want it done and provide guidelines, I'll volunteer to help. I often wonder how you get as much done as you do and still try to have a life outside of LowPower. I firmly believe in "put your money where your mouth is".....so I'm offering to help.

Just tell me how and give me the tools and I'll do the versioning.

Felix · February 01, 2016, 10:21:00 PM

Thanks very much for offering. I'm not sure how it could work efficiently though.
I'm afraid it might just add to the confusion if one person submits code changes and another maintains versions. Maybe Github has some tools to do that well but I am not aware. Right now Github is the version control repository. It does a good job keeping history and all that, and we can go back in time for snapshots of repositories.

I am all too used to using diff tools to compare versions of files.
Maybe that's why I don't give versioning too high of a priority.
But of course I am very aware not all people use diff tools.
A great free diff-er is WinMerge for those interested.