Thread: Robot Simulation Compatible With Solidworks
View Single Post
  #5   Spotlight this post!  
Unread 05-12-2016, 00:11
gblake's Avatar
gblake gblake is offline
6th Gear Developer; Mentor
AKA: Blake Ross
no team (6th Gear)
Team Role: Mentor
  
Join Date: May 2006
Rookie Year: 2006
Location: Virginia
Posts: 1,933
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
Re: Robot Simulation Compatible With Solidworks
Quote:
Originally Posted by Lireal View Post
The two that I know about are FRCSim and Autodesk Synthesis. Both should work well with Solidworks, and provide an opportunity for you to test your code as well, but FRCSim needs to be run on Ubuntu.
Quote:
Originally Posted by The CADDy View Post
...

In the off season I have been trying to get a better understanding of how they were able to accomplish this. From what I understand you have to have some sort of CAD model imported into the program and then program the model in some way. I am far from getting a grasp on the whole concept that is why I came here for answers.

So the question i should ask is: Is there anyway to take a CAD model of a FRC robot and control that in a "game" format? and if so what would be the best program to use?

My end goal here is to have a drivable robot on the computer. Something similar to what Microsoft Robotics Developer Studio does.
Based on your reply, I'll second what Lireal wrote, and add a little to it.

Because you don't seem to want to just drive a virtual robot for fun, or for show & tell, I'm guessing that you do want to learn something from the simulation. Here is a list of possible topics to explore. If I'm wrong about your goal, there is absolutely nothing wrong with enjoying a little eye-candy. However, keep in mind that even if all you want is that eye-candy, it can have different levels of sophistication/fidelity.

Some of these topics require a sophisticated simulation. Some don't. Some require one type of simulation, others require a different type. Some simulations need to run in "real" time. In others, matching real world time isn't important. The two tools Lireal named are good for some parts of this list, not so much for others.
  • Do any of our moving parts collide unexpectedly?
  • Will our robot tip over when we drive it hard?
  • Given a known battery & motor(s) condition, how fast will we be able to accelerate/brake?
  • Given a known battery & motor(s) condition, what will our top speed be?
  • Given a known battery & motor(s) condition, what will our manipulators be able to do?
  • Assuming perfect game pieces, how likely is capturing one with our manipulator/intake?
  • Assuming perfect game pieces, how likely is putting one into a goal with our manipulator/shooter?
  • Given a known battery, motor(s), wheel tread, and field surface condition, how much force can we exert in a pushing contest?
  • Given a known battery, motor(s), wheel tread, and field surface condition, will we be able to get past an obstacle?
  • What sort of measurements should we expect to receive from sensors we use?
  • What commands should we issue in autonomous to accomplish a task?
  • Will our software (software changes) work when we try them in the real robot?
  • Which maneuvers/operations should we try to bundle into single commands/macros, and which should the operator have to carry out without help?
  • What visual or tactile feedback will the drive team and human player need during matches to be most effective?
  • What physical control devices should our Driver Station expose to the drivers?
  • How should we divide responsibilities among the members of the drive team and what type of collaboration should they practice (among themselves, and with other teams).
  • Given a "typical" robot that roughly approximates one you might build, how many places can it visit and/or how many tasks can it accomplish during a match?
  • Is zone defense likely to fare better or worse than man-to-man defense in the 2017 game?
  • Should scoring methods focus on quality or quantity?
  • What should scouts record during a match (for alliance selection, or for driver advice), and how many scouts does it take to collect that information accurately?
  • etc.

Those are some of the topics a team with enough "bandwidth" can explore using simulators. One way to use a list like this is to ask whether each/any simulator you consider using will help with each/any topic in the list.

Blake
PS: Simulators can include humans rolling around a big room in chairs, paper dolls on a drawing, supercomputers lighting up a video wall/room/cockpit, or spreadsheets computing electrical motor or "pneumatics" performance (mechanical, thermal, etc effects).
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
Last edited by gblake : 05-12-2016 at 13:32.
Reply With Quote