search

jiahan / atrias

Automatically exported from code.google.com/p/atrias
0 stars 0 forks source link

Report Medulla errors on the GUI #49

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The medullas will report an error variable through the ethercat. It would be 
helpful to have these errors appear on the GUI.

Original issue reported on code.google.com by kit...@gmail.com on 5 Jan 2012 at 11:17

GoogleCodeExporter commented 8 years ago 
I will start with the GUI.

Original comment by cmartin....@gmail.com on 9 Jan 2012 at 11:23

GoogleCodeExporter commented 8 years ago 
Documented how to get glade setup and running.

Original comment by cmartin....@gmail.com on 11 Jan 2012 at 11:17

GoogleCodeExporter commented 8 years ago 
Data to be displayed
3 thermistor values per Medula
2 Voltage values per Medula

Errors to be displayed
EStop pressed
Limit switch triggered
Thermistor over temperature
Motor out of Range
Motor controller disabled
voltage logic out of range
voltage motor out of range

Original comment by cmartin....@gmail.com on 12 Jan 2012 at 12:00

GoogleCodeExporter commented 8 years ago 
Corrections
Motor controller disabled -> Motor controller error

Additions
Absolute encoder communication error

Original comment by cmartin....@gmail.com on 12 Jan 2012 at 12:31

GoogleCodeExporter commented 8 years ago 
I have decided on the bit flags for the errors. These defines will be included 
in ucontroller.h.

#define STATUS_ESTOP            (1<<0)
#define STATUS_LIMITSW          (1<<1)
#define STATUS_OVER_TEMP        (1<<2)
#define STATUS_MOTOR_OUT_OF_RANGE   (1<<3)
#define STATUS_MOTOR_CTRL_DISABLE   (1<<4)
#define STATUS_MOTOR_VOLTAGE_LOW    (1<<5)
#define STATUS_LOGIC_VOLTAGE_LOW    (1<<6)
#define STATUS_ENCODER_ERROR        (1<<7)

Original comment by kit...@gmail.com on 12 Jan 2012 at 8:02

GoogleCodeExporter commented 8 years ago 
GUI layout added

TODO:
Implement error flag decoding logic
Update GUI with data from Medula

Original comment by cmartin....@gmail.com on 14 Jan 2012 at 12:43

GoogleCodeExporter commented 8 years ago 
Temperature and voltage fields should now update.

TODO:
Test the GUI.
Implement error flag decoding logic

Original comment by cmartin....@gmail.com on 17 Jan 2012 at 1:16

GoogleCodeExporter commented 8 years ago 
An unknown bug was fixed so the GUI now runs and successfully reports 
thermistor and voltage values.

The bug would cause the GUI to crash and give a gtk call stack trace. The 
source of the bug is unknown. 

TODO:
Get the error flags to be highlighted.

Original comment by cmartin....@gmail.com on 18 Jan 2012 at 1:32

GoogleCodeExporter commented 8 years ago 
corrected misspelling of Medulla in gui and source

Original comment by cmartin....@gmail.com on 18 Jan 2012 at 11:44

GoogleCodeExporter commented 8 years ago 
Kit,

We talked about adding more Medulla statuses to the GUI. Would you please 
detail here requirements for the new Medullas in the GUI.

Thank you,
Christopher

Original comment by cmartin....@gmail.com on 18 Jan 2012 at 11:49

GoogleCodeExporter commented 8 years ago 
Changed the error display down to one label to free up room for having more 
Medullas.

I need to test the GUI code on the robot.

Original comment by cmartin....@gmail.com on 19 Jan 2012 at 3:59

GoogleCodeExporter commented 8 years ago 
Medulla A and B errors should display now.

Original comment by cmartin....@gmail.com on 21 Jan 2012 at 12:29

GoogleCodeExporter commented 8 years ago 
Once There error display has been tested I will move Medulla related code to a 
separate file.

Original comment by cmartin....@gmail.com on 24 Jan 2012 at 12:12

GoogleCodeExporter commented 8 years ago 
waiting to test changes

Original comment by cmartin....@gmail.com on 1 Feb 2012 at 11:33

GoogleCodeExporter commented 8 years ago 
I still have to figure out why the GUI is not receiving the status values from 
the medullas. I know the kernel module is receiving the error states correctly 
from the medullas, as I used that yesterday during our speed tests. I think the 
wireless_kernel_interface node may not be passing the data from the shared 
memory to the ros message, but I will have to look at the code to verify that. 
Once that is fixed we can run another test.

Original comment by kit...@gmail.com on 1 Feb 2012 at 11:43

GoogleCodeExporter commented 8 years ago

Original comment by kit...@gmail.com on 19 Apr 2012 at 6:07