redcokehome/nr-sdk

Automatically exported from code.google.com/p/nr-sdk

nr-sdk's Issues

Digital inputs operating together

I'm having some strange issues with one of the digital inputs – when I hit 
one of the limit switches, both ports 2 and 3 flash on and when I hit the 
other, only that one shows changes. I'm getting the same behavior in a program 
that I wrote.

Original issue reported on code.google.com by [email protected] on 19 Mar 2011 at 8:20

nr-console crashes on exit with Mac

On exit, nr-console crashes with a message:
"com.neuronrobotics.nrconsole.NRConsole quit unexpectedly while using the 
libNRJavaSerial.jnklib plug-in."

This happens on disconnecting the active serial connection.

Original issue reported on code.google.com by [email protected] on 1 Mar 2011 at 6:56

[deleted issue]

[deleted issue]

Connection error on using 3.7.6 on mac

Plugged in the DyIO into a mac.
Started NRConsole
Got this error in a dialog box:
"Failed to connect to device! The RPC sent in undefined with CRITICAL method."

Original issue reported on code.google.com by [email protected] on 5 Jun 2011 at 2:21

Nice to see some indication of port choices in nr-console

It would be nice if there was some indication, maybe a popup or something else 
that showed what the choices where for the type of port without having to click 
on each one then pull down the combo box.

Original issue reported on code.google.com by [email protected] on 18 Mar 2011 at 7:17

Connection between the DyIO and the laptop

There is no "connection" between the DyIO and the laptop. This means that when 
a program starts up, the counters are at the previous values, motors are at a 
random value, etc.

And when a program ends (or crashes) there is nothing that stops the motors so 
they keep running.

It would be nice if there was some state between the program and the DyIO so 
that all this starting/stopping housekeeping could be done.

It's really annoying to have a program crash with the motors running and 
there's no way of stopping them without starting the nr-console and stopping 
each one manually. Also, that woud be very bad if it were, say, an arm motor 
that crashed running, and it broke the robot because you couldn't stop the 
motor.

Original issue reported on code.google.com by [email protected] on 19 Mar 2011 at 8:17

Could be a hardware problem, but...

Just flashed one of my DyIO modules (#39) with rev 16.

Fired up NR Console and set port 12 to analog input in anticipation of plugging 
in a pot to test it.

Before anything at all was plugged in, I noticed that the display on NR Console 
was changing. The reported voltage on the analog channel was drifting slowly 
down from a value of around 5V towards (but not all the way to) 0V.

In the process of entering this note the DyIO has now quit entirely - gone to a 
solid red status LED. Unplugging and replugging it in doesn't help. Restarting 
NR Console doesn't help. Can't even reflash it now.  At best it gets part way 
through the upload and then quits.

Original issue reported on code.google.com by [email protected] on 28 Nov 2011 at 10:42

nr-console not remembering async or live settings

The nr-console doesn't seem to always remember the state of the async setting 
and never remembers the state of the "live" setting.

Is it supposed to?

This may be due to the nr-console crashing on disconnect.

Original issue reported on code.google.com by [email protected] on 19 Mar 2011 at 8:21

Need a way to stop motors

The servo motors on our robots don't stop when they have a 127 value - there is 
no way of programmatically stopping them. We need a way to stop sending PWM 
signals so they'll really stop.

This is especially true when a program exits. More on that in a future issue.

Original issue reported on code.google.com by [email protected] on 19 Mar 2011 at 8:14

Change %voltage on analog ports to voltage

The nr-console shows %voltage on analog inputs rather than voltage. The API 
uses voltage. I'd like to see them be the same - that is make the console show 
voltage so a person could find calibration values for light sensors or whatever 
by using the console, then enter the values into a program.

Original issue reported on code.google.com by [email protected] on 21 Mar 2011 at 2:58

Floating analog inputs have non-obvious behavior...

Not sure whether this is new behavior with rev 16 of the firmware or not. 
Probably not...

Analog input channels with nothing connected to them exhibit non-obvious 
behavior. The answer may well be - don't do that (i.e., let analog inputs float 
and then pay attention to them...), but the effect should at least be 
documented.

Shorting the input of one analog channel to ground pulls the inputs of all of 
the unconnected analog channels to zero. Similarly, pulling that input high 
pulls them all up.

Bottom line: All of the floating analog input channels seem to float to the 
same (not necessarily obvious) value. So ideally don't let them float but if 
they are floating realize that the values you are seeing are completely 
meaningless.

Original issue reported on code.google.com by [email protected] on 29 Nov 2011 at 2:28

Programs fail/crash with motors running

If the servo motors were running at the time a program exits, they continue to 
run after the program stops. Since there is no reset button, you have to unplug 
the DyIO to stop the motors.

It would be nice (not high priority) if when the connection was released with 
the DyIO, it stopped generating PWM signals.

Original issue reported on code.google.com by [email protected] on 1 Mar 2011 at 6:59

Delays on digital inputs changing with listeners

I'm seeing long time delays between the time that the digital input changes 
(pressing the limit switch) and I see the change in a java program. The time 
seems to vary by as much as a full second. This is using a 
IDigitalInputListener. 

Am I doing this right, that is should the listener be called asynchronously 
without having to set any time values or any other parameters? I'm assuming 
that if the second parameter of the constructor is "true" then it is always put 
into async mode.

Original issue reported on code.google.com by [email protected] on 19 Mar 2011 at 8:19

Index out of bounds on a serial port connect (mac)

This code:
    static DyIO dyio = null;

    public DefaultRobot(String dyIOPort) {
        System.out.println("Connecting to: " + dyIOPort);
        dyio = new DyIO(new SerialConnection(dyIOPort));
        dyio.connect();
        initialize();
    }


Produced this output (notice the first line of output showed the println):

Connecting to: /dev/tty.usbmodemfd13411
Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0, Size: 
0
    at java.util.ArrayList.RangeCheck(ArrayList.java:547)
    at java.util.ArrayList.get(ArrayList.java:322)
    at com.neuronrobotics.sdk.dyio.DyIO.resync(DyIO.java:248)
    at com.neuronrobotics.sdk.dyio.DyIO.isAvailable(DyIO.java:484)
    at com.neuronrobotics.sdk.common.BowlerAbstractDevice.connect(BowlerAbstractDevice.java:104)
    at com.neuronrobotics.sdk.dyio.DyIO.connect(DyIO.java:575)
    at DefaultRobot.<init>(DefaultRobot.java:12)
    at SampleRobot.<init>(SampleRobot.java:40)
    at SampleRobot.main(SampleRobot.java:26)

Original issue reported on code.google.com by [email protected] on 1 Mar 2011 at 6:48

Counters should have report on trigger

I don't have access to set the priority (this would be a feature request)...

I'd like to see counters/encoders with a trigger - that is, set a count value 
that would cause it to trigger, and it does a callback at that time. Rather 
than have callbacks on value changes which tend to cause too much network 
traffic.

Original issue reported on code.google.com by [email protected] on 1 Mar 2011 at 8:31

DyIO doesn't remember the servo motor default settings

If I set the servo motors in nr-console to eliminate the off-center noise that 
the robot makes, then hit the "set default" button, the settings are not 
remembered (at least) across reboots. Since they don't seem to default to a 
value that corresponds to "OFF" the same way the Vex motors do, the noise is 
pretty annoying on restart.

Original issue reported on code.google.com by [email protected] on 1 Mar 2011 at 7:02

[deleted issue]

[deleted issue]

Problems with rev 13 of NR Console on Windows 7

Just installed rev 13 of the firmware on my W7 development machine at home. 
Have successfully installed previous revisions with no problem. This revision 
seemed to install correctly, but when I fire up NR Console and select the DyIO 
port number - nothing happens. Actually, I see the center LED on the DyIO 
flashing for a few seconds, then that stops and it stays a solid blue.  But the 
display never changes - the diagram of the DyIO never shows up. The dropdown 
menu items are also non-functional.

Tried re-flashing the DyIO (to rev 13) using an earlier version of NRC. That 
seemed to work fine but it made no difference when trying to bring up rev 13 of 
NRC.

Original issue reported on code.google.com by [email protected] on 5 Nov 2011 at 9:26