Unmodified hobby servos do not expose the position data without cracking them open and reading the internal pot. Looking at the API, I'm guessing it's simply remembering the last positions you told it to move to and regurgitating them.
I'm working on a project that sort of does what this is claiming to do by providing this feedback by way of current sensing. http://satiety.com/robot
Package=Namespace
Byte Code=ILASM
JIT=JIT
Reflection=Reflection
Sandbox=Cooler Sandbox
GC=GC (no more ref counting)
Serialization=Serialization
Exceptions=Exceptions
Plat-Ind=Corel? (doubt it)
I'm sure this is only the beginning of the similarities, but in my opinion,.NET is a direct rip-off of java.
As far as.NET doing thing better?
Threads that you know how they work.
Remoting is a snap.
Very slick Call context.
I like.NET, I like Java.
.NET will win.
We have done a fair amount of it. In the end, the code we get is always horrid, but thats ok sometimes. When we have 600 reports to bang out, and none are all to complex, its ok if its ugly. If one doesn't work, just redo it. For TRULY grunt work, meaning that the above outcome is acceptable, go for it.
Except for situations where we have had someone who worked for us in the past, running the project at the other site, you just can't get anything better.
Slashdot Mirror
I stand corrected. These servos are unsual and very cool!
Unmodified hobby servos do not expose the position data without cracking them open and reading the internal pot. Looking at the API, I'm guessing it's simply remembering the last positions you told it to move to and regurgitating them.
I'm working on a project that sort of does what this is claiming to do by providing this feedback by way of current sensing.
http://satiety.com/robot
Early request patterns looked like this:
/scripts/root.exe
/c/winnt/system32/cmd.exe
/_vti_bin/..%5c../..%5c../..5c../winnt/system32/cm d.exe
/_vti_bin/..%5c../..%5c../..%5c../Admin.dll
/_mem_bin/..%5c../..%5c../..%5c../winnt/system32/c md.exe
/winnt/system32/cmd.exe
/scripts/..%5c../winnt/system32/cmd.exe
/scripts/..%5c../winnt/system32/cmd.exe
/scripts/..Á../winnt/system32/cmd.exe
(Params/IP Omitted)
Now I'm seeing these in some requests:
At least with two, we'd get to call them "Baby Bill's"
Java=.NET
.NET is a direct rip-off of java.
.NET doing thing better?
.NET, I like Java.
Package=Namespace
Byte Code=ILASM
JIT=JIT
Reflection=Reflection
Sandbox=Cooler Sandbox
GC=GC (no more ref counting)
Serialization=Serialization
Exceptions=Exceptions
Plat-Ind=Corel? (doubt it)
I'm sure this is only the beginning of the similarities, but in my opinion,
As far as
Threads that you know how they work.
Remoting is a snap.
Very slick Call context.
I like
.NET will win.
We have done a fair amount of it. In the end, the code we get is always horrid, but thats ok sometimes. When we have 600 reports to bang out, and none are all to complex, its ok if its ugly. If one doesn't work, just redo it. For TRULY grunt work, meaning that the above outcome is acceptable, go for it. Except for situations where we have had someone who worked for us in the past, running the project at the other site, you just can't get anything better.