Jump to content

Philo

Eurobricks Counts
  • Posts

    1,015
  • Joined

  • Last visited

Everything posted by Philo

  1. Texture mapping is supported by all modern LDraw tools (granted, "only" planar/cylindrical/spherical projection), see https://www.ldraw.org/documentation/ldraw-org-file-format-standards/language-extension-for-texture-mapping.html
  2. LDraw.org released the 2nd parts update of this year, with 572 new parts! A preview of all the new pars can be seen here. The update can be downloaded here. And more information about the parts update can be found here. Enjoy!
  3. A "Powered Up" update of my website... The Powered Up connector Mechanical characteristics, pinout and signal description. The Powered Up serial link protocol An overview of the dialog between Powered Up hubs and "intelligent" devices. Power consumption of LEGO Bluetooth elements
  4. Update on this: I confirm this is an issue with my phone (Moto G5+), it works perfectly with my Asus tablet. Only drawback, it's more bulky
  5. @imurvai, Excellent! So I guess your app will soon be able to use any motor configuration - too bad it doesn't work well on my phone (lag)... Going to publish soon my findings about Powered Up serial protocol. But unless LEGO releases more information, we are still a long way from beeing able to create custom sensors!
  6. Yes, these motors do contain an absolute encoder. The problem is that (unlike Spike Prime motors) there is no external 0 position mark. The app may be able to use that encoder after testing the 4 possible orientations of axle into motor hub. FYI, encoders data is returned on ID2 line in 10 bytes frames. First byte is D8 Second signed byte contains the motor rotation speed (dunno the units) 4 bytes signed dword containing the relative encoder position 2 bytes signed word containing the absolute encoder angle (-179..180) 1 zero byte (future use?) Last byte is checksum. The 2 bytes for angle are zero for the Boost motor that doesn't contain an absolute encoder. And yes, I'll be publishing more results on my findings soon...
  7. 10885 - My First Fun Puzzle (Duplo) Download MPD (OMR compliant) Known errors: None. Done with LDCad 1.6c Rendered with Studio 2.0 Patterns created with Img4dat and LDPartEditor
  8. http://peeron.com is also a good source for old instructions.
  9. With the parts highlighting, it looks clear enough! now I haven't tried to build it ;) Do you intend to publish a list of additionnal parts needed?
  10. what are you trying to do exactly, add connectivity to the small wheel arch?
  11. @JunkstyleGioI don't know exactly what's wrong, but I faced similar issues. What works for me is - place the Ldraw parts in CustomParts folder - Open part designer and close welcome screen - File -> open custom parts, select the part you want to edit. - add connectivity. - File -> Save. The problem is that Studio botches the LDraw parts, removing primitives, etc. I corrected that by copying again LDraw files in CustomParts folder. This works fine for added connectivity, but I suspect this might not work if your purpose is to add decals.
  12. Nice work ;) The Ldraw part is mostly done, but I'd like to solve a part numbering issue before releasing it...
  13. When I'm done I'll create a package for Studio. In order for parts to work well, I'll also have to create connectivity for Studio in addition to the shapes. If you want to see how it works, I already made such a package for Spike Prime parts: https://drive.google.com/open?id=17YU4BkiRdbmpHFgSegkDYvc21wq5MSJi To use it, unzip it and place its contents in your C:\Users\{your username}\AppData\Local\Stud.io . Spike Prime parts will then be available in Custom Parts palette of Studio. More details on custom parts in Studio forum: http://forum.bricklink.com/viewtopic.php?f=4&t=965&p=2615&hilit=customparts&sid=a0487a9d7213c77248f4ce56001e5072#p2615 Note that I was not able to use custom connectivity mode of Studio PartDesigner, so I had to make do with simple stud or axle connexions (eg. to attach motor hub to motor case). Not perfect, but it works! Again, don't hold your breath while waiting for C+ motors and hub ;)
  14. I am creating new 42099 parts for LDraw (thus Studio), but the road ahead is still long and winding... The new CV joints are already done: https://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/52730.dat https://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/52731.dat
  15. Thanks for the video. Works perfect indeed!
  16. The new l and xl motors are supposed to have an absolute encoder. The problem is that they don't have a 0° mark like Spike motors, which makes practical use tricky ? I tried bc2 with 42099. Overall it works fine, but I suffer from the same lag issue I already got with the boost hub. This makes me think it could be a problem related to my phone (Moto g5+)...
  17. And Ldraw parts maybe? :) Sure! That's the main reason for buying the 42099 ?
  18. I was about to make this.... Thanks for the confirmation it's the way to go!
  19. I think you must add a fourth path point with the same diameter as the second one) in the middle for the bottom band. Also take care of the order of path points (left, middle top, right, middle bottom)
  20. Not sure it's purely a firmware issue: my own tests of pup small motors show that their internal resettable fuses trip sooner than those of their pf counterparts.
  21. @kbalage, completely agree with your analysis ! ?
  22. All I can say is "Wow!!!!". Amazing...
×
×
  • Create New...