正在加载视频...

视频加载失败

Getting started with Hardware Design is as easy as 1, 2, 3, 4... 1. Draw the circuit using building blocks. 2. Map the inputs and output to FPGA pins. 3. Verify and Build. 4. Upload to the board! And you can do pretty serious stuff with this. While we...

13,148 次观看 • 5 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Milestone! We (robotic arms for gadgets assembly) finished the first commercial order, which brought the first revenue. Here are some learnings from this: The customer was a smart toy manufacturer. The task was to add a heatsink to Raspberry Pi. We received parts from them and returned the assembled modules back. Currently, it's done by teleoperation. Later it will be done by a remote employee via the Internet. Then it will be automated action by action, reducing the operator's time on this and making the task profitable. ps. If you have an assembly task that we can do for you asynchronically - leave a comment below. Learning 1. It's possible! This task which is usually done by the human arm with 5 fingers can be done with a two-finger gripper with the addition of a couple of simple tooling. The task was not simplified. We peeled off thin films from stickers, unpacked paper boxes, moved PCB boards full of components, etc. And no unsolvable problems have been encountered yet. Challenges: 1) The paper box shifted during the opening Solved with the plastic walls that you can lean against 2) Heat pad, stuck to the gripper instead of heat sync. Can be solved by gripper with a pump, but this time solved with the patience of the operator 3) The film on the pad is very thin. Turned out that sub-millimeter arm precision is enough to peel it off with just a regular gripper. 4) The working area has not enough space. You'll only know this by doing real tasks in bulk. This could be solved by an extra pair of long arms, but in this case, solved with the patience of the operator. I think that in the end, we will have 5-10 types of universal tooling and 5-10 types of grippers to solve almost all the problems in such assembly tasks. Learning 2. It's slow. It took 5 times more time, than doing it with human hands. But the good news is there's a lot of room for improvement. We now have specific “time for task” metrics, which we will decrease with iterations. The main reasons for slowness: 1) To rotate the gripper to a steep angle you are forced to control one robot arm with two hands instead of using both arms. We can fix this by just making more room for rotations. 2) Grabbing PCB board with two arms is hard. A slight difference in rotation can break the board, and it's hard to control these angles visually. To solve this, the best way is to use force feedback so you can feel the pressure applied to the item. 3) Accuracy and steadiness is still can be improved We will try a metal version and double the motors to do this. 4) It is physically difficult for the human hands to move with such precision To solve this, we will add a pad for the hands like in surgical robots Learning 3. It's a good business model The "Factory in the cloud" is a good business model for this stage. You send us parts and we send back assembled modules. Currently, it's more convenient than sending a robot to your place, as we can iterate/fix the robot quickly and utilize it 100% of the time. When we polish the set-up over time - we can send robots to your place. So if we can assemble something for you in the USA with Chinese prices by using modern automation - leave a comment below.

Igor Kulakov

37,266 次观看 • 1 年前

We are glad to announce that we have full STARK compatibility between Stone and Lambdaworks Starknet (Privacy arc) 🥷 Platinum Prover. We’re working on adding the CairoVM constraints, the builtins and layouts. You can generate a proof with Lambda Stark Platinum and verify it with Stone following the instructions here: The 3 main objectives to achieve against the alternatives are: 1. the prover and verifier should be easy to run. one command to prove any cairo code. the prover internally calls the vm first to generate the trace, the user shouldn’t do anything but run one command. one command to verify it locally with the stone verifier. we will also add a command to verify it with the l1 contract in ethereum mainnet or testnets. compatibility and support of all the builtins are being worked on. we will be updating the community in the upcoming weeks. for us it’s very important that anybody can test and play with our code. 2. performance. we are already 10 times faster than the stone prover. we believe we can be almost another order of magnitude faster. 3. code architecture and organization should be top notch. the codebase is pretty small on purpose. we are documenting everything we are doing. we are leveraging all the work done in lambdaworks for multiple other provers. this let us easily iterate, play and change any part of the prover. we can test and propose new ideas thanks to this. from our point or view this is crucial and a big improvement over what exists. we have multiple ideas on how to change the protocol. And here's a demo! Don't trust, verify.

Fede’s intern 🥊

16,711 次观看 • 2 年前