Wifi attachment commands
-
- Posts: 137
- Joined: Sat Feb 16, 2013 7:44 am
Re: Wifi attachment commands
I have never been a fan of modifying the libraries as it introduces unnecessary hassle when trying to upgrade to the latest and greatest. I think it would be great if a CustomWifiRequest() call could be made. So add a define CUSTOM_WIFI_REQUEST in the ReefAngel_Features.h and if it is there add the call to CustomWifiRequest with the appropriate parameters and return value. Then the IDE would do its magic.
Thoughts?
Thoughts?
Wifi attachment commands
I did this one for myself...the other problem is the defines for where to start and end custom memory...i say its your turn to make a pull request but yes that would be the better way to go.
Re: Wifi attachment commands
There is already a ticket for this.
I just didn't do anything yet.
https://github.com/reefangel/Libraries/issues/75
I wanted to have someone test the wifi key authentication (issue #71) and channel overrides (issue #73) before I add more to the wifi stuff.
I just didn't do anything yet.
https://github.com/reefangel/Libraries/issues/75
I wanted to have someone test the wifi key authentication (issue #71) and channel overrides (issue #73) before I add more to the wifi stuff.
Roberto.
Re: Wifi attachment commands
Roberto,
The issue you posted is a different request... the one I have hacked in for now was to get custom used memory variables dumped out like /mr
The issue you posted is a different request... the one I have hacked in for now was to get custom used memory variables dumped out like /mr
Re: Wifi attachment commands
Roberto, for what you have planned or are thinking about for issue75... would that be able to return data to the web browser or just call functions on the RA?
I would like to have function that returns through http the memory values in my custom memory fields... like /mr
I would like to have function that returns through http the memory values in my custom memory fields... like /mr
Wifi attachment commands
I have an idea...
What if we extended /mr to take two options which /mb /mi already parse.
Default stays the same
/mrx,y would return that memory range.
Technically we could do a memory write as well with
/mrx,y would write y starting at value x
That solves how i was going to figure out how i get my custom variable locations into the global ra_wifi files.
It also enables a mechanism to backup/restore memory locations.
What you guys think?
What if we extended /mr to take two options which /mb /mi already parse.
Default stays the same
/mrx,y would return that memory range.
Technically we could do a memory write as well with
/mrx,y would write y starting at value x
That solves how i was going to figure out how i get my custom variable locations into the global ra_wifi files.
It also enables a mechanism to backup/restore memory locations.
What you guys think?
Wifi attachment commands
It also creates a workaround for my negative number situation since i can just convert it from hex.
Re: Wifi attachment commands
how would you differentiate between a read and a write then?
Wifi attachment commands
Oh i had originally meant to write another slash command for write..whats your thoughts...
Re: Wifi attachment commands
Well, having a weboption3 would keep the consistency for the way the storing of data works. We already parse for weboption3 with the date/time command. The logic would need to be modified to put in some sanity checks for the command to handle 3 options (to ensure all three exist before writing, etc). The drawback is the amount of data you would be sending to the controller. We couldn't send the whole raw hex memory dump up because of how things get parsed. It's parsed 1 char at a time and reading in a long string would not work because the value would have to be stored in memory before it can be written or processed.
Re: Wifi attachment commands
The incoming read buffer is a
Code: Select all
static char m_pushback[32];
Wifi attachment commands
Looks like the set date method can take three args...
So, I'll see about doing this:
/mr - returns standard memory values VarsStart-VarsEnd
/mrx,y - returns location x-y
/mrx,y,z -set memory location x-y with value z
So, I'll see about doing this:
/mr - returns standard memory values VarsStart-VarsEnd
/mrx,y - returns location x-y
/mrx,y,z -set memory location x-y with value z
Wifi attachment commands
Hmmmm well writing can be shelved for now...I'd be more interested in solving the negative number issue in that case.binder wrote:Well, having a weboption3 would keep the consistency for the way the storing of data works. We already parse for weboption3 with the date/time command. The logic would need to be modified to put in some sanity checks for the command to handle 3 options (to ensure all three exist before writing, etc). The drawback is the amount of data you would be sending to the controller. We couldn't send the whole raw hex memory dump up because of how things get parsed. It's parsed 1 char at a time and reading in a long string would not work because the value would have to be stored in memory before it can be written or processed.
But displaying locations x-y is definitely doable for now...
Wifi attachment commands
What I'd we didn't store it and just start writing as we read each character.binder wrote: We couldn't send the whole raw hex memory dump up because of how things get parsed. It's parsed 1 char at a time and reading in a long string would not work because the value would have to be stored in memory before it can be written or processed.
We could write a loop from x-y and then start reading in char z writing and discarding as we go. If we y-x > strlen(z) then we can just write 0 or F and if it's less than, we just drop the rest on the floor.
Don't know if this is feasible...
Re: Wifi attachment commands
I think you will overrun your buffer and loose incoming data by trying to do that loop.
In the other hand, the reading of negative number is easy fixed. The writing of negative numbers can be interpreted as a very large byte or integer.
In reality, there is no such thing as negative number for the controller. The controller only understands 0s or 1s... , so technically for the controller -1 is the same as 65535.
I just confirmed that you can send "GET /mi,65535" and it will return -1.
This is the workaround for storing negative numbers for now.
I'll look into a more permanent solution later.
In the other hand, the reading of negative number is easy fixed. The writing of negative numbers can be interpreted as a very large byte or integer.
In reality, there is no such thing as negative number for the controller. The controller only understands 0s or 1s... , so technically for the controller -1 is the same as 65535.
I just confirmed that you can send "GET /mi,65535" and it will return -1.
This is the workaround for storing negative numbers for now.
I'll look into a more permanent solution later.
Roberto.
Wifi attachment commands
That doesn't help if i want to store a value like negative 73... The controller stores it just fine with write_int function. I don't quite follow the 0/1 analogy. Or the statement that the controller doesn't understand negative numbers...they are just another int, whats to understand?
With the writing of a range shelved, what about writing byte or int as a hex value?
With the writing of a range shelved, what about writing byte or int as a hex value?
Re: Wifi attachment commands
Ok, anyway, based on what you said regarding 65535, the way to enter negative numbers is to subtract the number for UINT_MAX which in this case would be 65536. So in your case, writing 65535 gets -1. For me to get -73 back into the variable, I had to write 65463. I can handle that situation in the html I am working on. All I need to do is if it's a negative number, then add 65536 to it
Anyway, so now the only thing left is to fix the display for reading and implement reading custom memory ranges.
Anyway, so now the only thing left is to fix the display for reading and implement reading custom memory ranges.
Re: Wifi attachment commands
Yeah, correct
You got the idea.... For now, this should get you going with storing neg values until a permanent fix is found.
I'll try to patch later today.
You got the idea.... For now, this should get you going with storing neg values until a permanent fix is found.
I'll try to patch later today.
Roberto.
Re: Wifi attachment commands
If you're bored and want to understand more about what Roberto was talking about, try this: http://en.wikipedia.org/wiki/Two%27s_complement
Signed ints are stored using "twos complement notation" inside the arduino. You'll see a little table on the right hand side toward the top of the page, illustrating storage of positive and negative numbers (although in 8-bit format rather than 16 like your situation).
Signed ints are stored using "twos complement notation" inside the arduino. You'll see a little table on the right hand side toward the top of the page, illustrating storage of positive and negative numbers (although in 8-bit format rather than 16 like your situation).
Current setup:
60g 24" custom cube (fish and softies right now)
AI Sol Blue, Ecotech MP-10wES
Coralife skimmer
100% customer controller, transitioning to ReefAngel
60g 24" custom cube (fish and softies right now)
AI Sol Blue, Ecotech MP-10wES
Coralife skimmer
100% customer controller, transitioning to ReefAngel
Re: Wifi attachment commands
great reference. i don't have my old books that discuss that stuff anymore so i couldn't refer to them to post a response.
Wifi attachment commands
I understand two's compliment and how large numbers are stored in binary representations. I guess the issue for me is that we are storing int's and bytes which are made up of multiple bits. We aren't flipping bits one by one we are doing write() and write_int() one byte at a time. I guess the bigger problem is that from the web we are writing one character at a time and assuming its a digit and dropping non-digits. So the negative is being treated as garbage and being dropped on the floor.
In the case of a /mb request or /mi request we should not drop it on the floor but instead set the signed bit accordingly...
I've got a working front-end storing the value appropriately, but it would simplify a lot if we just did it correctly on the back end.
In the case of a /mb request or /mi request we should not drop it on the floor but instead set the signed bit accordingly...
I've got a working front-end storing the value appropriately, but it would simplify a lot if we just did it correctly on the back end.
Re: Wifi attachment commands
I would argue that, in the long run, end-user apps shouldn't be worrying about bytes and ints at all.
Hopefully in a week or so I'll have something to show for how I envision this working.
I must admit I still haven't figured out where the params in the request are actually parsed from ascii to byte values... (where is "weboption" set?)
Hopefully in a week or so I'll have something to show for how I envision this working.
I must admit I still haven't figured out where the params in the request are actually parsed from ascii to byte values... (where is "weboption" set?)
Current setup:
60g 24" custom cube (fish and softies right now)
AI Sol Blue, Ecotech MP-10wES
Coralife skimmer
100% customer controller, transitioning to ReefAngel
60g 24" custom cube (fish and softies right now)
AI Sol Blue, Ecotech MP-10wES
Coralife skimmer
100% customer controller, transitioning to ReefAngel
Re: Wifi attachment commands
This should be good. I look forward to seeing this.enigma32 wrote:I would argue that, in the long run, end-user apps shouldn't be worrying about bytes and ints at all.
Hopefully in a week or so I'll have something to show for how I envision this working.
weboption is set in the ELSE clause inside the pushbuffer function.I must admit I still haven't figured out where the params in the request are actually parsed from ascii to byte values... (where is "weboption" set?)
Re: Wifi attachment commands
Ok, I patched the neg number reading and writing.
Grab the dev branch to test it.
Grab the dev branch to test it.
Roberto.
Re: Wifi attachment commands
Sweet, I'll try it out tomorrow if I can get some time. I've already pulled it and it's ready to go.
What did you end up doing for the write?
What did you end up doing for the write?
Wifi attachment commands
I have successfully patched /mr to take two variables to read a custom range in memory. If for some reason the start number is higher than the end number, it returns ERR.
Syntax: /mrX,Y
X = start
Y = end
Pull request pending.
Syntax: /mrX,Y
X = start
Y = end
Pull request pending.
Re: Wifi attachment commands
This code should be added to the html output so that the new /wifi page can fit the display on the phone. It scales great if you double click the page, but this would set it to be default.
Code: Select all
<meta name="viewport" content="width=device-width; initial-scale=1.0; maximum-scale=1.0; minimum-scale=1.0; user-scalable=0;" />