Search the Community

Showing results for tags 'block'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Frontpage, Forum Information and General LEGO Discussion
    • Guest Section - PLEASE READ BEFORE YOU REGISTER!
    • New Member Section - PLEASE READ BEFORE STARTING!
    • Frontpage News
    • Forum Information and Help
    • General LEGO Discussion
  • Themes
    • LEGO Licensed
    • LEGO Star Wars
    • LEGO Historic Themes
    • LEGO Action and Adventure Themes
    • LEGO Pirates
    • LEGO Sci-Fi
    • LEGO Town
    • LEGO Train Tech
    • LEGO Technic, Model Team and Scale Modeling
    • LEGO Mindstorms and Robotics
    • LEGO Action Figures
    • Special LEGO Themes
  • Special Interests
    • The Military Section
    • Minifig Customisation Workshop
    • LEGO Digital Designer and other digital tools
    • Brick Flicks & Comics
    • LEGO Mafia and Role-Play Games
    • LEGO Media and Gaming
  • Eurobricks Community
    • Hello! My name is...
    • LEGO Events and User Groups
    • Buy, Sell, Trade and Finds
    • Community
    • Culture & Multimedia

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


What is favorite LEGO theme? (we need this info to prevent spam)


Which LEGO set did you recently purchase or build?


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Country


Special Tags 1


Special Tags 2


Special Tags 3


Special Tags 4


Special Tags 5


Special Tags 6


Country flag

Found 6 results

  1. Hello! It’s-a me, Oky! And I’m back with another special review! For many years now, Mario, the stereotypical Italian plumber, has not only somehow evaded cancel culture, but also has been delighting the hearts of gamers everywhere with his simple and fun series of video games. One of the most influential entries in the franchise was Super Mario 64 on the Nintendo 64 as it was the first Mario game to make the jump from 2D to 3D as well as one of the first successful open-world 3D platformers ever made. This year marks the 25th anniversary of the game, so after the success of the NES set, LEGO decided to celebrate this occasion by releasing a brick-built version of the iconic yellow ? Block that appears in many Mario games – which is ironic since Super Mario 64 was actually one of the few games where this block didn’t appear in. It may seem like a strange choice for a set, but these ? Blocks are always full of surprises, so perhaps there is more to it than just a big yellow box? Read on to find out! Let’s-a go! Set Number: 71395 Name: Super Mario 64 ? Block Theme: Super Mario Year of Release: 2021 Ages: 18+ Pieces: 2064 Price: $169.99 The Box The box of this set has the same kind of branding as every 18+ set nowadays with a glossy black background and a white strip of greebles made out of various plates and tiles running along the bottom instead of the white background like all the “regular” Super Mario sets. If you have read my previous review you will know that I’m not really a fan of LEGO’s decision to market all adult-oriented sets with such a depressingly dark box art. It usually detracts from the set, although in this case I think it kinda works. The darkness adds to the mystery of the ? Block. There is not much else on the front of the box except for the set name, the Super Mario 64 and LEGO logos, and some numerical info about the set which also adds to the mystery. To uncover the secret of the ? Block, you don’t have to punch it like Mario, just simply turn around the box to its backside. This side of the box reveals that instead of a powerup or coins like in the games, what comes out of the top of the block is a bunch of microscale Super Mario 64 levels! How cool is that! There are several little close-up shots of some of the details, the transforming feature, and a schematic showing the measurements of the set. The main image and the schematic hint at the fact that there is another flap on the front of the box, but don’t show what’s behind it. What could it be? The mystery continues! The top of the box shows a lineup of all the characters included in the set along with some closer looks at Peach’s Castle and Bob-omb Battlefield. There is also a side view of the Princess Peach figure for size comparison. The bottom of the box shows some choking hazard warnings and other legal info on top of the white greebles. It also reiterates the number of pieces in the set – just to let you know exactly how many pieces you can choke on. The left side of the box features another closeup of Peach’s Castle - which is fitting since previous rumors for this set only mentioned the castle. Maybe whoever spread them only saw this side of the box? The right side shows the set name in different languages and a seal certifying that this is indeed an “official Nintendo licensed product”. Contents Inside the box there are 19 numbered bags, one bag with the instructions, and one with large plates. Some of the build stages are split into multiples bags which is not unusual. For some of them it makes sense, like for the bags with the number 2 since they contain a lot of parts, but for the bags with the number 9 it seems wasteful as the bags are less than half full and contain the same kind of parts, so I don’t understand why they didn’t just put them all into one bag. The bag for the large plates also seems wasteful as it is so big that it could have fit a 32x32 baseplate easily (I had to fold the bag twice to fit it into this picture). I thought TLG wanted to get more ecofriendly, not less? Instructions The instructions booklets starts with a few pages of the set’s designers talking about their love for Super Mario 64, the design of the set, and comparisons between the set and screenshots from the game. It’s always great to get such a little look behind the scenes at LEGO and at the talented people who develop these sets. The instructions themselves are nice and easy to read thanks to the new light gray background they’re using for these adult sets. There isn’t a lot of repetition in the build, although step 183 on the following example page asks you to put inverted 2x2 tiles onto a 16x16 plate 64 times. You don’t see such a high number every day in these callouts. Notable Parts There are quite a few parts in new or rare colors and even some new molds in this set! New molds include a downward 2 stud long bracket and a 2x3 plate with a 1x1 gap in dark brown, although each of those debuted in one other set recently. The only mold that I have never seen before is the 2x2 corner plate with the corner rounded off which is used to extend the bottom of the 2x2 curved corner slope. The latter appears for the first time in yellow, as does Queen Watevra Wa’Nabi’s crown and the 2x2 inverted tile. We also get not one, but two new colors of the cattle horn, red and yellow, plus some in tan which is a color it hasn’t been produced in since 2009, so anyone who is trying to assemble a Mola Ram will be pleased. Other new part-color combinations include a support beam in sand green (which is odd since it is hidden inside the build, so there is no reason to cast it in a new color), moldy (dark green) ice cream , 1x1 inverted bracket in lime, 1x1 brick with studs on 2 adjacent sides and telescopes in bright green, 2x2 round tile in green, 1x3 tile in nougat, 2x2 inverted dome in brown, and 4L bars in trans-clear, so if you want your Jedi to have a colorless lightsaber, you’re in luck. There are plenty of other parts in rare colors that have only appeared in a handful of other sets. If I missed anything new, let me know in the comments. I have some good news for all you sticker haters out there: Almost all the decals in this set are printed, and the only one that is a sticker, the barcode/star pattern on the yellow round 2x2 tile, is already pre-applied like in the other Mario sets! There is a large assortment of printed 1x1 tiles, the printing of which is impressively detailed. Figures It’s no secret that many Nintendo fans have been clamoring for proper Super Mario minifigures ever since LEGO acquired the license but so far all the Mario figures have been brick-built ones at a different scale. This set is no different as it comes with a slew of microscale brick-built representations of the characters similar to the ones in the LEGO Cuusoo Minecraft sets. Unlike the Minecraft figures, however, they made the odd stylistic decision not to print eyes on any of the characters (except for Mr. I for obvious reasons). Even the Bowser sliding puzzle in the previous picture doesn’t have eyes. Let’s take a closer look at them, starting with the good guys: Mario, Princess Peach, and Yoshi. The only one out of the three that has any kind of printing is Mario with his iconic mustache. They are all very recognizable despite the lack of detail. I always like it when designers can pull off a minimalistic design like that. It reminds me of the figures from LEGO’s old “IMAGINE” ad campaign. Still, I kind of wish they would have given Peach just a bit of detail as she looks a little plain next to the others, be it her lips or some features of her dress or something. Also, I’m not sure the part used for Mario’s hat was the best choice. It’s a bit large and looks as if someone had pulled Mario’s hat over his eyes. Or maybe Cappy is swallowing him?! Oh wait, wrong game. Yoshi looks good for the most part, although I wish they could have incorporated some white into his color scheme. Next we have the neutral characters: a Lakitu Bro, mama penguin and baby penguin. The penguins are not much different from other brick-built penguins that have appeared in many sets over the years, but you know what they say about things that aint broken. The Lakitu Bro has a simple yet clever design for his cloud that even includes his little camera. Lastly, we have the enemies: Mr. I, Big Bully, King Bob-omb, and a Chain Chomp. King Bob-omb is easily the best-looking character in the set as he is not blocky like a lot of the others and looks very accurate except for his lack of arms and eyes. The use of that new wheel piece for his body is perfect. The only downside to him is that he is stuck to the Bob-omb battlefield ground. I had to disassemble him and loosely stack the pieces here for this picture. Big Bully on the other hand just might be the worst figure as he just looks like a brick with horns. He should have been round like the others and some indication of his green feet would have been nice too, although I’m not sure how they could have achieved that with legal building techniques. Mr. I and Chain Chomp are fine – again, except for the odd lack of eyes on Chain Chomp. Actually, there is one more secret figure included in the set! The designers intended it to be a surprise for you to find during the build, hence why it isn’t in any of the official images of the set, so I will put it in spoiler tags. If you want to see it, click below, otherwise skip to the build section. The Build It’s time to get building! Here we goooo! First, you build the inner structure of the block, then the back panel. I struggled a bit putting on the rubber bands that hold the back panel up as they get stretched to their limit. Hopefully they won’t snap any time soon. There is a gold star like the power stars that Mario collects in the game placed inside the structure above the purple tile. It has no purpose and is no longer visible once the build is finished; it’s just a neat easter egg included by the designers for you to discover during the build which is pretty neat. Next, you build the front panel. As I mentioned before, there is not much repetition in the build since the construction of the front and back are completely different despite them looking the same from the outside. Never judge a block by its cover! After that, you can put the block aside for a while as most of the rest of the build is the top panel with all the microscale vignettes on it. You start building each vignette by building the base, then the scenery, then attach it to the rest of the build. Each vignette is very different, but all of them are constructed very intricately. I like how going from a big, rough support structure to such small, detailed scenes makes the build feel like it is getting more challenging as you go. Once the whole top section is complete, you just drop it into the block from above. The last step is to build the side panels which are identical, so unfortunately you end the build with some repetition, but it’s not too bad. Spare Parts There are tons of little 1x1 bits left over after the build, including extras of a lot of the printed tiles and other new/rare parts! Since there is an extra mustache plate, you can build a second Mario out of the spare parts, one that looks closer to the big LEGO Mario. Alternatively, you could also build his brother Luigi, even if poor Luigi was never in Super Mario 64. The Complete Set Yeahoo! The build is finished! The completed block looks sooo smooooth! Except for on the question marks, no stud is to be seen, and the rounded edges and corner really add to the smooth feel. They even managed to cover up all the transforming functions very well. Usually, you only see such large, tiled surfaces on MOCs and it looks fantastic. It looks so accurate to the ? Block in the games that it’s not much different from any other replica of it. The only difference is those studs on the question marks which give them some nice texture and remind you that this is indeed still a LEGO set. The block looks great from all sides – except for the bottom where it’s just a big hole. It looks dark and ugly and makes the block hard to hold up from the bottom. This is not a huge issue and I understand why they made it this way as you will likely not see the block from this angle very often and it makes easy to access the interior of the block to fix any potential mechanical errors, but I still wish they would have made this part of it a bit more sightly. Once unfolded, the block becomes a great display stand for the four microscale maps. If you thought the block looked too boring before, it definitely becomes more interesting in this form! Let’s take a closer look at each of the micro-builds, starting with the first level and the hub world of the game, Peach’s Castle, which fittingly hovers over all the others. There is lots of nice part usage here such as the cattle horns as flags, the moldy ice cream scoops as trees, and the telescope as the warp pipe through which Mario enters the game. The castle itself looks nice and accurate, although it’s a shame there is no inverted version of those 2x2 wedges they used for the turret roofs that they could have used for the underside of the turrets instead of the cheese slopes. And in case you’re wondering, no, unfortunately Mario does not fit through the castle entrance as it is one plate too short. The backside of the castle is not so interesting as there is only a small tile indicating a backdoor, although to be fair, I don’t think there is much back there in the game either. The only fun detail is Yoshi hiding behind the tower at the top where you can meet him after you beat the game. The next level (if we’re going by the order in which you visit them in the game) is Bob-omb Battlefield. This is probably my favorite of the micro-vignettes as it is sprawling with details and it really feels like they managed to recreate most of the map in this little 14x14 space. The cannons, the bridges, the trees, the tree stumps, the patches of yellow flowers, the floating island with the red coins box; it’s all there. They even managed to include one of the cannon balls that roll around behind the gray bridge using a microphone piece. There are no secret hidden areas or play features in this vignette, although you can aim the cannons vertically. They even included the little nook you can use as a shortcut to teleport to the top of the mountain where you fight King Bob-omb. Next up is Lethal Lava Land which is mistakenly named Lethal Lava Trouble in the description of the set. There is a fair amount of detail here as well even though part of the transforming mechanism takes up a lot of this space. The printed platform tiles and the Bowser sliding puzzle really add to the authenticity. This is also the only level with a physical representation of one of the power stars that Mario collects. Lastly, there is Cool, Cool Mountain. I don’t think it’s all that cool, though, since it looks a bit plain compared to the others. That’s not to say that it’s bad however! The designers managed to represent most of the level fairly faithfully. They included the log cabin at the foot of the mountain, the wooden bridge suspended over the abyss next to the cabin, the top and bottom halves of the snowman that Mario has to unite, and even the ropes of the ski lift. I just wish they would have included some face printing for the snowman, even if it’s just the mouth. On the back of the mountain, you can see the snow slide leading down from the small cabin at the top as well as the penguin and her baby that Mario has to return to her. Play Features The last few 18+ sets that I reviewed didn’t have many play features, so I was pleasantly surprised to find that this set has more than expected! Of course, the main play feature is the transforming function. It is very simple and works as smooth as the block looks. To reveal the vignettes, instead of punching the block from below like Mario, you push down from the top. The vignettes flip up, and once they’re on top, you give Peach’s Castle a little push which will cause it to swing back, pushing down the side vignettes in the process, and that’s it. Pretty easy, although once the vignettes get to the top, it doesn’t stop, so you need to balance it a bit before you push it open. I wish they would have added a stopper so that they don’t turn too far. To fold them back in, you just pull the castle forward again, flip up the sides to hold the castle in place, and push the whole thing back. Both of these motions work so smoothly and flawlessly, it feels very satisfying to do, so you may find yourself transforming the block over and over. Every time it flips, the back panel of the block gets pushed open by the edges of the side vignettes and gets pulled closed again by the rubber bands inside. Brilliant. You can see it all working in the video below. Some of the vignettes have a hidden interior! The entire front section of Peach’s castle can be removed to reveal the entrance hall. It features the paintings that serve as portals to the three other levels in the set which is a nice touch, even though in the game those paintings weren’t actually in the entrance hall, but locked behind doors. In case you didn’t know, the story of Super Mario 64 is that Bowser trapped the inhabitants of the castle in paintings, so Mario has to jump into them, fight enemies like sentient bombs, and collect power stars to power the doors of the castle and free all the little mushroom people. The Mario world is weird, yo. You can also remove a chunk of the back of the Cool, Cool Mountain to reveal the ice slide inside the mountain that Mario slides down to win a race with a penguin so that he can get a power star from him. Again, Mario is weird. Lethal Lava Land has different play features. The volcano and its surrounding low-poly ring are built on top of a turntable, so they can spin like in the game. There is also the log that Mario has to roll to get to one of the power stars which is attached to a rail so that you can push it back and forth. The following animation shows the two features in action. There are a couple more features which were teased on the box, but the designers wanted these to be a surprise, so I will put them in spoilers too in case you want to discover them yourself. But that’s not all! Even though this set is a completely different scale, it works with the electronic LEGO Mario and Luigi figures. You can use one of them to go on a hunt for 10 power stars hidden around the set by scanning the barcode inside Peach’s Castle, then scanning certain parts of the vignettes. There are clues where to find each star at the beginning of the instructions booklet. Some of the hints are fairly obvious while others you need to be familiar with Super Mario 64 to get them. Unfortunately I don’t have either of these figures, so I can’t test it out for you, but I’ll let you figure it out for yourself. I’m not into the “regular” Mario sets, but it’s pretty cool that they make them compatible with other Mario sets like this to expand your play experience. Ratings Design: Great looking, accurate, and very unique design with lots of great detail in the vignettes. Build: Fun build with nice surprises that gets more and more intricate but ends on a bit of repetition. Playability: Transformation works great and all the vignettes have some kind of play feature, except the Bob-omb Battlefield. Figures: Nice minimalistic approach; most are recognizable, although some could have been better and had eyes. Parts: Lots of new/rare parts, everything is printed. Price: $170 for 2064 pieces is a pretty good deal, especially for a licensed set. Overall: Honestly, I am hard-pressed to find any faults in this set. It’s a fun build with lots of good parts and a great looking result that even has several play features. It’s a set unlike any other and makes for a nice piece of nostalgic gaming memorabilia as well as a detailed display piece. Like with the Diagon Alley set, it was a nice surprise to find features in the set that were not advertised. My only gripes with the set such as the figures or the bottom of the block are mostly just nitpicking. It may not be the minifig scale set everyone’s been asking for, but it's an unexpected and innovative set that we didn't even know we wanted which is even better, xo I applaud the designers for that. If you’re a Super Mario fan, you will enjoy this set. If not, you will probably still enjoy the unique design. Thank you for reading and thanks to Lego for sending me this set to review. It will be available on October 1. What do you think of the set? Let me know in the comments and vote in the poll above. To conclude this review, I will leave you with some wise words from Batman: Some days you just can’t get rid of a Bob-omb.
  2. Now that my semester is mostly over, I've been thinking about some of the projects I had to put on hold to focus on my senior design project this year - specifically, the PCB I developed a couple years ago to run two three-color track signals off a centralized microcontroller: The original design called for a three-color signal: red, yellow, and green. My plan was to divide my layout into blocks, with a signal placed on each block. I wanted my signals to respond in the following manner: - If a train is detected in a block, that block's signal must be red (block is occupied). - The signals in the blocks adjacent to occupied blocks must be yellow (block ahead is occupied). - Otherwise, the block signal will be green (block is unoccupied). This would result in the signals 'following' the train around the layout, such that any trains travelling on the same track would be aware of each other, hopefully avoiding collisions. In practice, I won't be running trains on the same track, but it's still a fun effect to have! My resulting truth table then looks like the following. Inputs A and S are the signals from the adjacent blocks and block sensor, respectively, while outputs R, Y, and G are the red, yellow, and green signals, respectively. It doesn't matter which 'side' I get a signal from an adjacent block, as either way I want the signal to turn yellow. In addition, if the block sensor sees a train, I don't care what the adjacent blocks are doing - the signal must turn red. After working through this table, it occurred to me that there were two ways I could build this signal controller... Form 1: NAND Logic This truth table is simple enough that I should be able to build it with basic logic gate ICs - and if I can do that, then I can do it purely with NAND logic gates, saving cost as I only need one type of chip to make this work. However, I still need to work on converting the truth table to a set of Boolean expressions, and from there into pure NAND logic. After doing a bit of research, it looks like I'll need multiple NAND chips, as most chips I find have only four gates inside them. However, I am space and cost limited, as I can only use four NAND chips (16 NAND gates) if I want to be comparable to the cost of the ATTiny85 at 36 cents per chip. Form 2: ATTiny85 Since I only have five inputs/outputs, the ATTiny85 microcontroller is perfect for this application - there are exactly five pins left over after accounting for power, ground, and reset. However, I would need to program each microcontroller, and doing so with a surface-mount device becomes problematic. The cost is also an issue, as each one costs about $1.16-1.25. Buying in relatively small quantities, I think I can get the cost of components for each board to about $5 per board - including connectors and such. The main issue with using NAND gate chips is the amount I'll need, and thus the space they'll take up on a size-limited board. I also will need some transistors to drive the LEDs as the logic chips can't drive that much current directly. The issue with using an ATTiny85 chip for each board is how to program the much smaller surface-mount versions, as well as the relatively large fixed cost of each chip - I can't work on optimizing out some of the cost in the same way I could with the NAND version. I want to use JST connectors for running cables between the boards and sensors and such, as they're directional and I don't have to worry about plugging things in backwards this way. There is another question I have for you all: what's the most useful form factor? My original project had a board that was designed to fit in a 4x4 stud area, but for this I'm leaning more towards a 2x6 or 2x8 board, as I think I can fit that into more spaces.
  3. Not really, but I found out that the motors in my GX EV3 peform better in IR Control mode than how they do in my program, and I believe that it is because the motor power is different. Each block in the EV3 programming software that moves the motors has a digit for how much power each motor should have. I'm wondering what this digit is in IR Control mode, because the motors act much better in this mode than how the do in the program. If anyone here knows the power of the motors when the EV3 brick is in this mode, please reply as soon as possible. It would be very appreciated.
  4. I'm taking the knowledge I learned from a class last semester and applying it to my long-term layout. The devices pictured here form the basis of a block-occupancy detector system that will be placed within my long-term layout to facilitate some autonomous functions, such as signals, automatic level crossings, and remote switching. To start with, let's have a quick look at the FPGA development board I'm using for the controller. This is the Basys 3 Artix-7 FPGA Trainer board, sold by Digilent. The Artix-7 FPGA chip used here has 33,280 logic cells divided into 5200 slices (each slice containing four 6-input LUTs and eight flip-flops). It runs off of a 5V power supply, delivered either through USB or an external power jack. There are four 2x6 'PMOD' connectors (standard spacing, thankfully), one of which also acts as an analog input. There is also a VGA connector and a full-size USB as well. In addition, there are 16 switches and five pushbuttons available, as well as 16 LEDs that can be accessed by the user. It uses the Xilinx Vivado Design Suite for programming. Next, we have the sensor I'm currently using. ...Or at the very least, something very similar to it. It's one of those fairly generic designs that's copied by everybody and sold for very little, so it doesn't really matter which one you get so long as it looks the same. This, however, is not the final sensor I'll be using - this design is extremely directional, in that it's only sensitive enough for my application when the light source is in front of the module. It turns out that the version which has a photoresistor as its light-sensitive element is much better at detecting the ambient light level, and is actually somewhat cheaper. These type of sensors will run happily on anything from 3.3-5V, and have two outputs: an analog output, which will vary its voltage from 0V up to the voltage of the supply, and a digital output, which operates in the reverse of what you'd typically expect - that is, it outputs a high signal (high being the voltage of the supply) when the light level is below the trigger point set by the potentiometer, and outputs a low signal whenever the light level is above the trigger point. There is one power LED and an LED that reflects the opposite state of the digital output. In my first picture, I have attached the VCC pin of the sensor to one of the VCC connections on the Basys 3 - pins 6 and 12 on the PMOD connectors act as 3.3V supplies, with pins 5 and 11 acting as a ground, and pins 1-4 and 7-10 acting as signal lines - and the GND pin on the sensor to one of the ground connections on the Basys 3. The digital output (DO) on the sensor is connected to one of the signal lines on that same PMOD connector, and the analog output (AO) is left unattached (if I connect AO to a ground connection, the sensor acts as if a bright light is in front of it no matter what). Next, we have to write the code that defines the behavior of the controller! FPGAs are interesting because rather than a microcontroller executing commands, the code written actually tells the FPGA to re-wire itself internally to produce hardware-only logic that provides the desired behavior (this is where the name Field-Programmable Gate Array comes from). As such, the code isn't written in C or Java, but in Verilog and other Hardware-Descriptive Languages (HDLs). The code files can be treated as individual 'blocks' of logic, and can easily be combined together to produce much more complex behaviors than we see here. This is the only Verilog module that runs the system currently: module bodsensortest(led,bodsensor); output led; // Goes to some LED on the Basys 3 input bodsensor; // Comes from AO on the sensor board assign led=!bodsensor; // Oddly enough the AO output is an inverse output - it goes LOW when the light level is above the trigger point endmodule Here I'm defining a module called 'bodsensortest', with the output 'led' and the input 'bodsensor'. Then I tell the Basys 3 to set the output 'led' to the opposite state of 'bodsensor'. In addition to building the actual logic, it's advised to write a testbench module that hooks up to your first module and allows you to simulate it before sending the code off to the board: `timescale 1ns/100ps module tb_bodsensortest; reg tbodsensor; wire tled; bodsensortest dut(tled,tbodsensor); initial begin $dumpfile("tb_bodsensortest.vcd"); $dumpvars(0,tb_bodsensortest); tbodsensor=0; #40 // Default should be sensor 'uncovered' tbodsensor=1; #40 // Sensor now 'covered' #20 $finish; // total sim time: 100ns end endmodule Here I define the units of time that I'm simulating in, the module, and inputs (reg) and outputs (wire) for the testbench file. Then I tell the system to create a .vcd (timing diagram) file, and in that file examine ALL variables within the testbench file. Then I toggle the state of tbodsensor off and on to simulate something passing over the sensor, with some delays. Finally, I add in a 20ns delay to round it to a nice number. Lastly, in order to actually make this work on the board, I have to play with a constraints file that tells the board what I/O pins to look at and what variables they correspond to: ## This file is a general .xdc for the Basys3 rev B board ## To use it in a project: ## - uncomment the lines corresponding to used pins ## - rename the used ports (in each line, after get_ports) according to the top level signal names in the project ## LEDs set_property PACKAGE_PIN U16 [get_ports {led}] set_property IOSTANDARD LVCMOS33 [get_ports {led}] ##Pmod Header JA ##Sch name = JA10 set_property PACKAGE_PIN G3 [get_ports {bodsensor}] set_property IOSTANDARD LVCMOS33 [get_ports {bodsensor}] Here I'm telling the Basys 3 that one of the LEDs on the board is the output from the first module, and the input for that module comes from one of the PMOD connections. After this, I plug these files into the Vivado software, and generate a file that's sent to the board. Because FPGAs are volatile, I also told the software to generate a configuration file that's saved in flash memory on the Basys 3 so it can automatically re-configure itself every time I turn it back on, rather than having to reprogram it with a USB. Otherwise, I would only be able to run this program until the Basys 3 was turned off! All of this makes a little LED on the board turn on and off Also, I've actually got the function backwards - I want the module to follow the backwards behavior of the sensor, as I want there to be a signal whenever a train is passing over the sensor (it makes more logical sense to me that way). However, so far I'm quite pleased with what I've accomplished as we didn't really do much with outside inputs during the class - we stuck mainly to the switches and buttons provided!
  5. After watching a documentary about Puma Punku, I decided to rebuild one of the famous H-Blocks with LEGO-bricks. I tried to build it as small as possible (2x4 brick for comparison) without losing too much of the original measurements/aspect ratio...