Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Control System (http://www.chiefdelphi.com/forums/forumdisplay.php?f=177)
-   -   2015 Beta Testing - The Components are Here. (http://www.chiefdelphi.com/forums/showthread.php?t=130303)

Joe Ross 10-10-2014 21:40

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by SteveGarward (Post 1403798)
Everyone needs to be careful on this one. According to the answer to my question here on the FIRST forums, once you add (separate) power to PWM signals from the MXP, you have an ACTIVE DEVICE.

I think it would be more accurate to say say "once you add an active power supply to PWM signals from the MXP ..."

This does not keep you from supplying 3.3v or 5v from the MXP header or battery voltage from the PDP to the DIO pins, It only keeps you from adding a power supply to add a different voltage.

Quote:

Originally Posted by SteveGarward (Post 1403803)
My concern now is for boards that have 'prototyping' area on it - while the board may be passive, does adding components/circuits make it active? Burden of proof at inspection to show it's just sensors etc., or that PWM pins are not controlling anything? Not sure how that will play out yet.

No matter what board you use, if you claim that it is passive, you'll have to prove it at inspection. Not sure how having a prototyping area changes that. An active circuit added to a prototyping area of an otherwise passive board makes it active.

controls weenie 10-10-2014 23:47

Re: 2015 Beta Testing - The Components are Here.
 
I wanted to share with you the reason I am asking about the PWM voltages. A few of the kids and I are designing a "PWM Extender" which will attach to the robot and inline with the PWM cable. The "PWM Extender" will be 2.5" x 1.5" PCB with a row of 8 LEDS to indicate the servo (or motor) command. This will allow our team to monitor (or debug) the robot health from in the stands. The "PWM Extender" is parasitic in that it will steal from the 6V supply (middle conductor) to power a ATMEGA88 uController to drive the LEDs as a function of the signal command. There is a 5V voltage regulator.

Our team would like to place as many indicators on the robot so the driver and operator do not have to look down at the laptop. We have noticed that no one ever looks down during the competition.

Yes, it is active but only for the LEDs. We would be glad to share the design, gerber files, uController code, etc with anyone who wants it. But, I have a feeling that most will reject it.

Your thoughts?

SteveGarward 11-10-2014 19:55

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by Joe Ross (Post 1403819)
Not sure how having a prototyping area changes that. An active circuit added to a prototyping area of an otherwise passive board makes it active.

From the reply on the FIRST forums, I read that to mean that once any components at all (power or otherwise) are added to the board, and the board is no longer simply a breakout, it is an active board.

Joe Ross 11-10-2014 20:32

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by controls weenie (Post 1403832)
I wanted to share with you the reason I am asking about the PWM voltages. A few of the kids and I are designing a "PWM Extender" which will attach to the robot and inline with the PWM cable. The "PWM Extender" will be 2.5" x 1.5" PCB with a row of 8 LEDS to indicate the servo (or motor) command. This will allow our team to monitor (or debug) the robot health from in the stands. The "PWM Extender" is parasitic in that it will steal from the 6V supply (middle conductor) to power a ATMEGA88 uController to drive the LEDs as a function of the signal command. There is a 5V voltage regulator.

This is definetly active. In addition this would be illegal in any previous year, as a motor controller is not allowed to connect to a custom circuit. It would be legal for you to make a seperate board and have the roboRIO communicate the values it's sending to the motor controllers to the seperate board over another communication method (I2C, SPI, CAN, serial, ethernet, etc).

Given how hard it is to see items on the robot during a match, a better option might be to have either the roboRIO log the data you want to it's internal flash or send the data to the dashboard. Both the LabVIEW dashboard and the SFX dashboard support logging by default.

Joe Ross 11-10-2014 20:33

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by SteveGarward (Post 1403908)
From the reply on the FIRST forums, I read that to mean that once any components at all (power or otherwise) are added to the board, and the board is no longer simply a breakout, it is an active board.

Are you interpreting the 4 examples of items that are ok for a passive device as the only 4 items allowed? The definition allows many more things.

Quote:

PASSIVE DEVICE or CIRCUIT: Any device or circuit whose capability is limited to the conduction and/or static regulation of the electrical energy applied to it (e.g. wire, splices, connectors, printed wiring board, etc.).

controls weenie 12-10-2014 09:34

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by Joe Ross (Post 1403911)
This is definetly active. In addition this would be illegal in any previous year, as a motor controller is not allowed to connect to a custom circuit. It would be legal for you to make a seperate board and have the roboRIO communicate the values it's sending to the motor controllers to the seperate board over another communication method (I2C, SPI, CAN, serial, ethernet, etc).

Given how hard it is to see items on the robot during a match, a better option might be to have either the roboRIO log the data you want to it's internal flash or send the data to the dashboard. Both the LabVIEW dashboard and the SFX dashboard support logging by default.

Joe, I like your first suggestion to use a serial message to another device (maybe a PCDuino) to display our commands on the robot. We can set a message buffer equal to the motor (and servo) commands then send it to the PCDuino maybe somewhere high for best 'line of sight'. This would also help us debug in the pit.

We do want to try placing the commands on the robot this year with indicators such as colored LEDs. In previous years, we have spent many hours reconfiguring the dashboard but we NEVER look down at it during competition. Even the coach is too busy to look down. This way the entire pit crew in the stands can follow the driver and operator commands to educate them on component failures. This might expedite getting the robot ready for the next match.

controls weenie 14-10-2014 21:16

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by Joe Ross (Post 1403911)
This is definetly active. In addition this would be illegal in any previous year, as a motor controller is not allowed to connect to a custom circuit. It would be legal for you to make a seperate board and have the roboRIO communicate the values it's sending to the motor controllers to the seperate board over another communication method (I2C, SPI, CAN, serial, ethernet, etc).

Given how hard it is to see items on the robot during a match, a better option might be to have either the roboRIO log the data you want to it's internal flash or send the data to the dashboard. Both the LabVIEW dashboard and the SFX dashboard support logging by default.

Has anyone seen the specs on the roborio accelerometer? I searched but could not find any information.

Joe Ross 14-10-2014 21:34

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by controls weenie (Post 1404316)
Has anyone seen the specs on the roborio accelerometer? I searched but could not find any information.

It's a 3 axis, selectable +/- 2g, 4g, or 8g. MMA8452Q

Joe Ross 15-10-2014 20:47

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by SteveGarward (Post 1403908)
From the reply on the FIRST forums, I read that to mean that once any components at all (power or otherwise) are added to the board, and the board is no longer simply a breakout, it is an active board.

With today's clarification that plugging in an active component to a passive MXP makes the MXP active, I agree with you. But it sounds like they're trying to figure out a workaround.

SteveGarward 15-10-2014 21:24

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by Joe Ross (Post 1404452)
With today's clarification that plugging in an active component to a passive MXP makes the MXP active, I agree with you. But it sounds like they're trying to figure out a workaround.

I certainly hope they do - for everyone. That clarification makes the current preliminary rules much more broad that I had anticipated or understood them to be.

controls weenie 15-10-2014 21:40

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by SteveGarward (Post 1404457)
I certainly hope they do - for everyone. That clarification makes the current preliminary rules much more broad that I had anticipated or understood them to be.

I have been reading many of these post and I have not understood the benefit of the mxp pcb. All I can see is that it is an exercise in relocating the connector from deep inside the 2x17 male connector. I have several expansion ideas but my thoughts are to connect directly to the 2x17 male connector. I am not seeing the benefit of the expansion board. Moreover, there are no active or passive issues. What am I missing?

RufflesRidge 15-10-2014 22:18

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by controls weenie (Post 1404465)
What am I missing?

That wiring the signal and ground of a 3 pin connector to the signal and ground mixed into the 34 pin connector is a pain. A huge pain if you want to use more than the number of ground pins available.

SteveGarward 15-10-2014 22:27

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by controls weenie (Post 1404465)
I have been reading many of these post and I have not understood the benefit of the mxp pcb. All I can see is that it is an exercise in relocating the connector from deep inside the 2x17 male connector.

Yes and no. It allows you to have easy access to the pins in the MXP, and lay them out in a manner that is easy to use - such as providing ground pins and in a 3-pin arrangement so you can plug in a regular PWM cable. To relocate the connector we just need a cable. You then still have the issue of what you connect to it and how.

Quote:

Originally Posted by controls weenie (Post 1404465)
I have several expansion ideas but my thoughts are to connect directly to the 2x17 male connector.

You could use a connector with a cable and solder the wires directly to things, for sure. It's just often more inconvenient to do so, depending on what exactly you're trying to do.

Quote:

Originally Posted by controls weenie (Post 1404465)
I am not seeing the benefit of the expansion board. Moreover, there are no active or passive issues.

The benefit is 'ease of handling'. Given the current preliminary rules/rulings/statements (especially today's response on the forums), I'm not sure where just plugging something straight in (say, an encoder) through wire on a cable/connector would sit on the active/passive fence. But, they are working on it.

GeeTwo 19-01-2015 16:42

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by Ether (Post 1403309)

Using a simple model of the battery as a fixed internal resistance of 0.011 ohms in series with a constant 12.7v voltage source, it's straightforward to compare the energy wasted across the internal resistance for the same ampere-hours at different currents.

But it's even worse than that. A close look at the battery discharge curves suggests that the internal resistance is not constant, but rather increases substantially with current.

This is not at all surprising. Most resistors increase in resistance as the temperature goes up, like when they have a lot of current running through them. In addition to the reduction in the battery's reduced capability as reflected on the discharge curves, you are also losing more energy to heat in the wiring and the motors at high draw.

jhersh 20-05-2015 17:30

Re: 2015 Beta Testing - The Components are Here.
 
Quote:

Originally Posted by Joe Ross (Post 1403002)
Sample rate is 40hz, resolution is 1/8 amp. Latency seems to be less then then the sample rate, we compared it to an analog current sensor we used last year and didn't see any unexpected latency. I haven't seen any specs on max current, but it measured 60+ amps per channel on our drivetrain.


I've attached data we collected from the PDP during a match at the SCRRF Fall Classic. Note that each channel has a small steady state error, which will be calibrated out in a later firmware update.

Hi Joe,

Do you think you have the DS log for this match that you could attach or send to me?

Thanks,
-Joe


All times are GMT -5. The time now is 05:03.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi