|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Team Update #18
|
|
#2
|
||||
|
||||
|
Re: Team Update #18
Can you imagine how this will effect the Finals on Einstein? You know there are going to be minibots that are almost equal speed...
|
|
#3
|
||||
|
||||
|
no!!! thanks FIRST that you make it clear i like updates and seeing this from what you learned in previous week but cant this wait till championship
|
|
#4
|
|||||
|
|||||
|
Re: Team Update #18
Not a fan. Witnessed MANY minibot climbs this weekend at San Diego that most certainly imparted 3-4 N of force yet were not auto triggered. It's going to suck when the field fails to work correctly and teams lose points they should have earned.
|
|
#5
|
|||||
|
|||||
|
Re: Team Update #18
I saw far too many missed triggers (at least they appeared to be) on webcast this past weekend to be comfortable with this update going into our event this week.
|
|
#6
|
|||
|
|||
|
Re: Team Update #18
I agree, Cory. More than once a 1 second minibot with significant momentum failed to trigger. Is it possible that the triggers still need too much contact time to register? BTW, we had a great time partnering with you guys and 3704!
|
|
#7
|
|||||
|
|||||
|
Re: Team Update #18
Quote:
We've since increased the speed a lot, more along the lines of 254, and the impact is pretty violent. |
|
#8
|
|||
|
|||
|
Re: Team Update #18
The triggers are designed with multiple sensors, and the FMS only looks for 1 of those to be triggered for any amount of time. Thus making the minimal amount of force still trip the tower. The towers have been tested and proved to be much more accurate since week 1, so I think this should be a non-issue now at week 3.
|
|
#9
|
|||||
|
|||||
|
Re: Team Update #18
Quote:
Whatever the circuitry I am 100% confident that there were multiple (greater than 10) instances at San Diego where minibots compressed the platform upwards into the sensors without the tower actually triggering. |
|
#10
|
|||
|
|||
|
Re: Team Update #18
Quote:
|
|
#11
|
||||
|
||||
|
Re: Team Update #18
I have submitted the following question to the FIRST Forum Q&A:
"With any electro-mechanical contact closure that is sensed by a programmable control system, there is both a force component required to perform the closure, and a time/dwell component for the control system to register the closure. The Competition Manual provided the force component necessary to activate the minibot trigger contacts, but did not provide the time/dwell required for this contact to register with the FMS. What is the minimum length of time that the specified force (2N-4N) must be applied to the trigger plate in order to be recorded/registered by the FMS?" |
|
#12
|
||||
|
||||
|
Re: Team Update #18
Quote:
|
|
#13
|
|||||
|
|||||
|
Re: Team Update #18
Quote:
It seems pretty clear there are still problems with the field and I don't just say this because the tower failed to trigger with our minibot. It was a very common occurrence. |
|
#14
|
|||
|
|||
|
Re: Team Update #18
Quote:
|
|
#15
|
||||
|
||||
|
Re: Team Update #18
Quote:
Hence my question if you knew that the force was being applied (and applied properly) or if it was just a 'gut feeling'. Sound of the impact does not equate into actual applied force. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|