Gen 1 Snapshot Herobot help thread

Starting a thread to use for Gen 1 Snapshot herobot discussion.

Note: the gen 2 build uses parts from the Gen 2 competition kit, the education bundle does not have all the parts.

Gen 1 Build Instruction Link

4 Likes

I made a Google Doc for anyone to put errors they find in the Snapshot instructions or suggestions for making it clearer.

Not that I’m expecting a lot of errors, but more to keep them locatable.

I’ll start this off with an engineering quote:

“If it’s not broken, it doesn’t have enough mechanisms yet”

I built the herobot and am pretty underwhelmed with it (this is a complaint post, so take it with a grain of salt).

I do appreciate all the work that went into this, but I just think that this isn’t the best that could have been done with all that work.

IMO this goes at the bottom of the list of the best herobots. I didn’t think it could get any worse than Fling.

First off, here’s my contribution to the instruction fixes:

Step 44: In the parts list at the top of the page the label says a 2x8, however the correct piece (and the piece in the picture and model) is a 1x8.

Step 60-61: The 1x8 (put on in step 58) in step 59 changes into a 1x12 in step 60.

Steps 57-58 are just kind of awful to do with one person, as the rubber bands have a good deal of tension.

So on to the actual robot itself.

First up: it is just overall flimsy, inconsistent, and break a lot

Here’s my biggest problem with the robot: it just doesn’t work. Sure it picks up the disks, given ample time and sometimes a little help, but that’s not it. It doesn’t get it in the goal well or consistently. When the disks get to the shooter, they take a few seconds of crunching around and then shoot a distance that would it be criminal to say was accurate. Sometimes it’ll fall right in front of the robot, sometimes it’ll make it into [the equivalent of] the 4-point zone. But it can’t actually get it into the 4-point zone, or at least I never got it to. This is because you have to sit a good distance back from the bar when you shoot otherwise the disk hits the bar. When the disk launches, it isn’t flat against the ground. It comes in at an angle, which means you have to sit back a good deal form the bar and even then it’ll sometimes still hit it. Honestly a pushbot could probably score more points. From my testing, it’ll get about 50%-50% in the 2 and 3-point zones.

It severely lacks in pins, lead to breakages

Overall, the build lacks in pins. Usually herobot builds and such have an excessive amount of pins, but this one is severely lacking. For example, step 58 shows that the motor assembly (and the motor itself) are only being held on by two pins on each side. I never attach a motor with less than 3, and with good reason. I have had many issues with that part in particular falling apart (a.k.a. imploding). There are many other parts of the robot that also lack in the pin department. When doing the build, I would suggest using more pins, especially at the high-force points.

The rubber bands break a lot

I played around with it for about 10 minutes and broke the rubber bands stretching from front to back twice. It is a pain to replace them. The rubber bands also like to derail a lot and wander into the joints where the roller and the structure meet.

It gets stuck on the disks

There are no guards anywhere to help with this. If you aren’t lined up perfectly or you hit a disk with the non-intake side of the robot, it’s stuck. And sometimes you can’t get it unstuck without help.

The zone-toucher barely reaches over the fence and is super hard to line up.

There’s not much to say on this one. Post below if you want specific information. Oh, one thing though, if you run it backwards, it breaks really easy. The shaft like to come out of the mini standoff connector a lot too, and it could use some shaft collars on the inside 45 degree piece. [end of one thing]. I’ll end by saying that there is definitely easier ways to touch the 2-point zone.

The wires of the drive motors get in the way of the shooter.

This is partially a user error, but it should be emphasized the importance of this. Put the wires behind the 2-hole 2-pin connector with one blue pin for best results.

The black rubber belt on the intake roller should be replaced with rubber bands.

The robot doesn’t work without this one. Maybe my belts are old, but when I tried it, it just flat out didn’t spin the intake, even with nothing in it. I replaced it with a doubled up rubber band, and it worked much better. Be careful though of the rubber band falling in between the pulley and the structure: very bad things happen when that happens.

I’ll probably add more to the mist as I remember more things, but this is what I can remember right now. Feel free to ask for clarification or elaboration (or video) on anything I said here.

This is just my two cents, and I’d like to know where other people who build this stand. Is it a good build? Top of the line? Good or bad for elementary nd middle schoolers? A good use of time?

TL;DR: I think the herobot isn’t that great and has a lot of problems (read bullet points for details).

8 Likes

If you think this robot is supposed to be great, you are missing the point of why these predesigned trainers are offered to novice teams. Their purpose is not to be a great robot, their purpose is to help a beginning team learn how to build with the Vex robotic system, and learn some mechanism basics, acting as a starting point for a team to use the engineering design process to build a great robot of their own.

Sorry for my thoughtless wording here. What I meant to say was that herobots are supposed to have a certain amount of robustness to them, not that they are supposed to be competitive and score lots of point with little to no room for improvement like a robot that a top level team will bring to worlds.

They are supposed to work decently, while still being limited in perhaps one of two major point scoring ways. This helps students get the satisfaction of building the robot while still having the opportunity and inspiration to improve.

Many of the kids who build this will have never built a robot before. IMO this herobot is employs some iffy mechanisms that should not be used on a custom robot because they are overly complex and don’t really work.

One of my favorite herobots was the Next Level one, because it could do most scoring actions somewhat well, couldn’t get the tantalizing yellow bonus hubs, and was simple and actually employed mechanisms that would be used on a competitive robot.

5 Likes

Yes, I agree completely. These pre-designed trainers should have excellent build quality since they are intended to serve as the example of how to build.

I’m glad to see these trainer builds remain “slow”, with simple direct drive motors on the drivetrain (the introduction of a couple idler gears was a nice feature) but I think, however, it is unfortunate that mechanisms are being introduced, for example the radial release mechanism of Fling, that are beyond the mechanical ability of the novice student. I think these builds should have much more basic mechanisms that are easy to understand, easy to repair, and typically show a basic concept such as gearing for torque or speed. If they can’t score a lot of points, well, that’s the point, they aren’t intended to.

8 Likes

Taking it a little off topic from iq, but I am honestly not impressed with the vrc hero bot either. The past ones have had at least decent build quality, even if the compound gearing on moby’s arms was a little sketchy. But I honestly feel like a lot of corners were cut on the design, and things that no competitive team would do were done, such as cantilevered wheels and different sized wheels leading to an angled base. These are honestly terrible build quality, and I’m not even going to mention the huge uncut shafts that stick out all over the place and pose a large possible damage risk.

1 Like

The original clawbot trainers, both IQ and V5, are where we start all our new teams, and what we build at our basic summer STEM camp. These trainers for the most part have given all the instruction our teams have needed. I am somewhat ambivalent about the need for game-specific trainers. Some of our teams have built them, especially in IQ. But we try to get our teams into the regular design process as quickly as possible after building a clawbot trainer.

OK, built a Gen 1 Snapshot this morning, don’t have any disks to try it with yet but here are my build notes:

On page 27 of the instructions – it would be nice to have the length of the required belt so you don’t have to scroll all the way back up to the parts list at the top of the PDF.

On page 28, the parts list shows a 1x8 beam but the label next to it says “2x8”.

Stretching the two rubber bands across the mechanism in step 57 is very hard – you almost need 3 hands to hold things in place while stretching the bands to stop the tension from tearing things apart. Once you add the beam in step 58 things stabilize.

…and speaking of step 58, it shows adding a 1x8 beam, but by step 60 that beam has magically transformed to a 1x12.


Seems to work fine on mine, FWIW.

2 Likes

This post was flagged by the community and is temporarily hidden.

Once again, VEXIQ Engineering has set the new VEX IQ roboteers (and new mentors / coaches) up to fail. After spending 3+ hours building Snapshot , the default driver control program doesn’t drive the robot.

I complained last year about this to support and @Bob_Mimlitch_III. I got told it would be fixed and that it wouldn’t happen this year, but here we are.

The drive base motors should be in ports 1 and 6. Viewing from the top, left hand motor in 1. Right hand motor in 6 (or port 12 if you have shorter cords).

The other two motors get plugged into ports 4 and 10 (front buttons on the controller. ) Your roboteer can pick the best way.

I’m all for programming, but with an awesome drive program available, it makes a quick success for the roboteer.

There is no comments in the instructions about needing to write code, how to find the code, etc.

Oddly, the wiring for the Gen 2 snapshot is correct.

9 Likes
8 Likes

Happy to see that I’m not the only one with a yellow dispenser that does not want to cooperate.

5 Likes

A new revision of the Gen 1 Snapshot instructions has just been released.

Changes include some of the feedback provided in this thread, as well as the wiring.

Please continue to provide feedback if you come across anything!

8 Likes

I’m going to take you up on this.

It appears that on steps 95-97 two of the the standoffs in the launching mechanism disappear and move over to the right, going through the wheel (edit: this issue first appears in the second picture of step 94).

image

2 Likes

Need to say that the rev level is 5. I used the link at the beginning of the thread and it takes to Rev 3.

Wiring is not how I would do it, but it will work. Or how the V2 VIQ bot is wired either.

Thanks for the update!

2 Likes

Editing the OP doesn’t seem to be an option for me any longer, maybe it is on a timer. This leads us to our next suggestion, a static link to the ‘current’ rev.

This link should always redirect to the latest revision:

https://link.vex.com/docs/2022-2023/viqc-slapshot/Snapshot-Gen1-BI

6 Likes

It does and thats how I found it. But missed the link to the Rev5 version local to this.

Thanks for the heads up on this.

Another revision (Rev 6) was just pushed live that fixes this issue. It can be found here.

8 Likes