![ev3 box robot bricksmith ev3 box robot bricksmith](https://c1.staticflickr.com/1/259/18549013948_95377206a8_b.jpg)
This should be 1/N where N is the LDU length of the segment unit, i.e. ldr 0 Author: Willy Tschager 0 Unofficial Model 0 SYNTH BEGIN DEFINE TECHNIC_CHAIN_TREAD _38 BAND FIXED 0.03571 8 0 // Technic Chain Tread 38 1 0 0 0 0 0 1 0 0 0 -1 -1 0 0 57518.dat 0 // Technic Chain Tread 38 1 0 0 0 -32 0 -1 0 0 0 1 -1 0 0 57518.dat 0 SYNTH END ldr 0 TECHNIC_CHAIN_TREAD _38 SYNTHESIS DEFINITION 0 Name: TECHNIC_CHAIN_TREAD _38. For the large treads this is defined as: 0 FILE TECHNIC_CHAIN_TREAD _38. The band definition includes a scaling value which is used for working out how many elements will be needed between constraints, i.e. Two parts are defined: one for going between, and the other for wrapping around, the constraints – i.e. The loop of treads is defined in the lsynth.mpd file as a band of fixed size elements. The sizes as per the LSynth file can be seen in the image below: Sprocket Radii as defined by lsynth.mpd.
![ev3 box robot bricksmith ev3 box robot bricksmith](https://c1.staticflickr.com/9/8762/16935321528_ab811cd11a_b.jpg)
It is in fact the small sprocket that is wrong, it ought to be 32 LDU. This is incorrect, since the large sprocket is 1.6x that of the small, not 2x. This states that the small sprocket has a radius of 25 LDU, and the large 50. The two sprocket types I’m interested are listed as: 0 // Technic Sprocket Wheel 25.4 1 25 0 0 0 1 0 0 0 1 0 0 0 1 57520.dat 0 // Technic Sprocket Wheel 40.4 1 50 0 0 0 1 0 0 0 1 0 0 0 1 57519.dat Each constraint is defined by its type, radius, orientation etc. The lsynth.mpd file is used to describe the parameters around the various elements, in this case Bands, and Band Constraints. I’ll attempt to describe what I’m seeing. I’ve worked through how the lsynth.mpd file works, including reading the source code. Author jerry Posted on NovemNovemCategories LEGO Tags Bricksmith, Treads Leave a comment on Bricksmith and Treads – Part 3 Further Investigations into LSynth and TreadsĪfter posting my “tutorial” articles on the LEGO MINDSTORMS EV3 Facebook group I started to look in to how LSynth does its magic, and now have a greater understanding of what the issue with treads is.
![ev3 box robot bricksmith ev3 box robot bricksmith](https://9to5toys.com/wp-content/uploads/sites/5/2020/07/lego-mindstorms-ev3-robot-kit.jpg)
This does look a lot of effort to do manually, but I’m used to it now and find it quick enough to do, and the results look good. This results in the treads 2-5 only having one orientation rotation, and one position translation, thus reducing the errors. This is probably due to the first tread being rotated about its origin only. One thing to note is that treads 2-5 have undergone two rotations each, but don’t appear to suffer any level of cumulative error. Once that first tread is in place and aligned, it is now a simple case of copying, pasting, and rotating as shown in part 2: Second tread in place. This is different to the 50 used by LSynth as discussed in my previous post about my investigations in to LSynth: Sprocket Radii as defined by lsynth.mpd: 50 & 25. a radius of 48 from the centre of the sprocket. First tread rotated 18˚.Ī point of interest is that the tread was rotated around a Y coordinate value of -48, i.e. The technique is almost identical to that discussed in Part 2, but the first tread needs to be rotated by 18˚ after its initial placement: Initial placement. These are much better in terms of placing the first tread as it will sit properly in the notch as it’s on an integer grid, unlike the 90˚ rotated version which is very slightly off that grid. In Part 2 I referred to sprockets with the notch a the top: Notch at the top. In this article I will finish discussing placing treads manually using Bricksmith.