We reimaged our CRio using the 2013 imaging software and we are comming up with a problem.
We take code using the new Labview and after we deploy the code the CRIO CPU % goes through the roof.
I don’t know if the imaging software is faulty or whether it is something that we are doing.
Any suggestions?
Not your fault and not a problem.
There’s just a bug in the Driver Station Charts tab display.
It plots the cRIO % against the 12v battery scale rather than against 100%.
Once the cRIO % rises above 15% it disappears off the top of the chart.
Looking at the log through the Log Viewer should show the correct plot.
I would agree with you, however we are also experiencing huge amounts of lag that eventually prevent it from running at all.
Also, nothing is showing up when I open up the log viewer.
When I look at older logs I see the graphs but when the problem first started happening we can no longer view any of the data from the logs.
I think NI said there was a different Log Viewer bug.
P.S.
Last years Log Viewer seems to still work, but I don’t have a good log to test it against.
If it’s laggy the problem could be excess error messages.
How do your Diagnostics tab messages look?
Thanks for the tip.
We are getting a huge overload of errors in the diagnostics. We are currently working on reducing this number and hopefully bringing it down to none.
Last year “none” was the best goal.
This year, however, there are some new messages that will be [strike]near[/strike] impossible to get rid of entirely.
Messages for what’s connected/what’s not connected to the Driver Station have been added, and others that just mention state changes like Disabled/Enabled, so for instance we’ll see messages telling us that we don’t have an optional secondary router.
They’ll mostly be warnings that can disguise real error messages, so read them carefully.
I’ve not yet seen the 2013 display. Are info/warning/error messages displayed in different colors?
No color changes.
Here’s what an initial startup of the Driver Station Diagnostic messages looks like without the robot.
Warning
44002 occurred at Ping Results: link-GOOD, DS radio(.4)-bad, robot radio(.1)-bad, cRIO(.2)-bad, FMS-bad Driver Station
<time>1/16/2013 2:01:15 PM<unique#>5
FRC: Driver Station ping status has changed.
Warning <Code> 44004 occurred at Driver Station
<time>1/16/2013 2:01:13 PM<unique#>4
FRC: The Driver Station has lost communication with the robot.
ERROR <Code> -44009 occurred at Driver Station
<time>1/16/2013 2:01:12 PM<unique#>3
FRC: A joystick was disconnected while the robot was enabled.
Warning <Code> 44001 occurred at No Change to Network Configuration: <noNICConfig><noNICConfig>
FRC: Driver Station network configuration status.
Driver Station
<time>1/16/2013 2:01:12 PM<unique#>2
Warning <Code> 44006 occurred at Driver Station
<time>1/16/2013 2:01:12 PM<unique#>1
FRC: Custom I/O is not enabled or is not connected to the driver station.
If each type of message were sent with a unique prefix tag they could be displayed as different colors on the screen. Perhaps next year?
Perhaps sooner than that.
A newer log file viewer is in the works and is due to be released shortly. It will read both version 0 and version 1 files. The viewer released at kickoff only reads version 0 files and this year’s DS produces version 1 files.
As mentioned, the number of messages is up quite a bit to aid in debugging field and/or robot issues, but the downside is the verbosity. The new one does color code and filter messages, but at this point the DS displays all messages.
Greg McKaskle
Good to hear Greg. I was hoping for some diferetion of bad error and minor error.
hey I’m on the same team as TogetherSword8 has any one else had the problem that we are having. The CRIO CPU is maxed out, yet we are not having any lag anymore. is it just a glitch in the software or is it actually maxing out the CPU.
When I use the old drivers station to drive the robot it still shows the CPU maxed out and we are also having the problem of not being able to see the charts in Log Viewer.
Warning <Code> 44002 occurred at Ping Results: link-bad, DS radio(.4)-bad, robot radio(.1)-GOOD, cRIO(.2)-GOOD, FMS-bad Driver Station
<time>1/17/2013 8:26:08 AM<unique#>24
FRC: Driver Station ping status has changed.
we get this message even if the driverstation is seeing the robot
is that fine or is something going on?
That message is fine.
It’s just information. You’ll get it whenever a new contact is made, e.g., when you finally hear from the robot radio you’ll see this updated message again.
ok
we have been having the problem with the Crio maxing out even if there is no lag
the only time it isn’t maxed out is when we first connect or format it.
thoughts?
If there’s no lag, then I wouldn’t worry too much just yet.
Wait for FIRST/NI to release the updated Log Viewer and Driver Station to see what those displays show about the CPU %.
If you really want to, you can play with this tool:
Tools ->Profile -> Performance and Memory…
I haven’t used the latest version of that tool yet, so I can’t give specific recommendations.