The LEGO® Fan Weekend (LFW) is organized by The LEGO Group’s Community Engagement and Events Team in cooperation with AFOLs and supported by Skærbæk Kursus- og Fritidscenter.
The purpose of the event is to provide a space for AFOLs from all over the world to meet, network and share their passion. At the same time it is also an exhibition where the participants can share their MOCs with each other and the public audience.
The event is located in Skærbæk Kursus- Fritidscenter in the town of Skærbæk, Southern Jutland, situated on the west coast of Denmark. Approximately 2½ hours drive north of Hamburg, 1½ hours drive south west of Billund and 4 hours drive west of Copenhagen.
In 2014 around 350 AFOLs from more than 20 countries are expected to participate in the event and to show their creations made from LEGO bricks to over 2000 public visitors during Saturday and Sunday.
Lego Technic Ropa euroTiger upgraded with 3 Sbricks, Tested at Lego Fan Weekend 2014 in Skærbæk, Denmark. Controlled with Mini Ipad, using Bluetooth Technology. Enjoy!
Allan Clausen: I mainly demonstrated the Ropa with the 3 Sbricks installed, and I got a lot of attention from the crowd visiting. I actually was so busy, that i hardly didn't have time to shoot som pics from the event. It went amazingly well, and the crashes i had,... moreI mainly demonstrated the Ropa with the 3 Sbricks installed, and I got a lot of attention from the crowd visiting. I actually was so busy, that i hardly didn't have time to shoot som pics from the event. It went amazingly well, and the crashes i had, was only my self to blame. I for instance lifted the Ropa, while it was running, because it almost ate the paper cloth on the table, and thereby i broke some chains in the middle of the machine, and had to make a very big repair, to get it fixed.
September 30, 2014
Lénárd Pásztor: This weekend is LEGO Fan Weekend! Meet Allan Clausen's Ropa euro-Tiger model built with SBrick. Will You be there?
Lénárd Pásztor
(owner)
Hi All!
We created an update for train fans. Our users usually configure multiple trains in one profile. The problem started when not all trains powered on and the profile not started. Now you can stop the discovery and run the profile if you want even if not all device connected. We hope this solves the problem. Any comments are welcome. :)
