Jump to content

codefox421

Eurobricks Citizen
 View Profile  See their activity

  • Posts

    198

  • Joined

  • Last visited

 Content Type 

Everything posted by codefox421

  1. codefox421
    That's much bluer better! RAW files are magic =P Very nice solution for the play functions. Either it's a breeze to use or you're a trained operator; you make the motions look so smooth in your video!
  2. codefox421
    Don't get me wrong, BricksTer hasn't neglected Power Functions compatibility for the sake of 9V compatibility. There are reasons LEGO didn't include 9V compatibility. Whatever those may be, 3rd party projects need not follow suit. I'm familiar with the tin foil method, but I hadn't seen the battery method or the output-as-input method before. Good tips. My biggest issue with the tin foil method is that you can potentially connect the battery backward. I'm not sure if those other two methods have the same issue, but BricksTer ensures proper polarity of 9V input. No more connect and really quickly disconnect if the LED doesn't light up. Instead, BricksTer is plug'n'play 9V compatible. Thank you! Though my long term goal has always been to have a KickStarter of my own. I simply decided to open-source BricksTer from the start. I didn't want it to go the way of UPCORE: promise of open-source in the furture, but nothing to show at the end of the day. This way, if I get hit by a bus tomorrow, all the information is still there! By the way, I don't plan on getting hit by a bus, but who does?
  3. codefox421
    I've tried it. I mostly used it for planning an LGB garden railway, but I played around with the LEGO parts too. I'd say the UI is more intuitive than BlueBrick, but the parts selection is far more limited. With the free demo, there is an upper limit on track sections that can be placed. That gets really annoying really fast. A college friend of mine cracked it once, but I've since misplaced the binary.
  4. codefox421
    As a LEGO train fan, I made backward compatibility with the 9V system a requirement from the start for BricksTer: http://www.eurobricks.com/forum/index.php?showtopic=87340 I guess you could call my project the competition to SBrick, and there are advantages and disadvantages to both projects.
  5. codefox421
    The `comboMode` function, specifically when `maskedByte == upX` or `maskedByte == downX`, is where the speed controller logic happens. You can rewrite these sections to take finer steps with the virtual speed controller. Alternatively, your direct-to-speed sliders already use the finer resolution. Edit: For anyone interested, here's the APK with those sliders: https://www.dropbox....ann-sliders.apk They are buried in the menu at the upper-right of the screen. Kinda messy I know, but a massive overhaul of the app is in the development stages...
  6. codefox421
    The original plan was for BricksTer to be a 1:1 replacement for the IR receiver. Since then, plans have changed and there are now 28 (=7*4) speeds in each direction (edit: that's a total of 56 + brake/float) . However, they are only accessible via the direct-to-speed message mode. There is another message mode which acts like the 1:1 IR replacement. I'm not sure if things will stay like this forever; I've been toying with the idea of adding an oscillator, so the uC can run at a higher clock speed, and I can pass off the PWM generation responsibilities to the built-in comparators. Currently, any communication interrupts the PWM signal, so I've limited messages to 1 byte. This limits the resolution of the speeds, but 28 is decently fine-resolution for what is essentially a toy. I ought to make a video demonstrating the finer-than-7 resolution...
  7. codefox421
    Wow! Thanks to everyone for the kind words! Here you go. Though I've only built one copy. I simply replaced the colored parts between the red/white and brown/tan versions. Emerald Night with BRmk1 by niaconis, on Flickr Oh I believe you! Those curves can be a megablocks! I'm not overly convinced about my doors either. Things get tricky around the ends since that's where everything comes together, so these doors are a sort of compromise I took in order to get the coach out of my head and into the brick. I'll undoubtedly revisit them some day; I've been continually planning and revisiting my EN mods since I bought the set 3 years ago! I've seen your mk1, and it's quite nice. Keep at it! This isn't the first time I've tried to design a mk1. This is revision 6 of trial about 4 or so! (I've lost track over the few years it's been since I first started)
  8. codefox421
    Thank you! Yes! BricksTer is compatible with older phones, as well as NXTs, PCs, and EV3s*. I would love getting your help to design a case! I have a handful of ideas about the direction I'd like to take it, but it's pretty much a clear slate right now. Setting this up might be easier done through voice than text. Do you use Skype or some other VoIP service? PM me please. *Based on specs and not real world tests. I don't own an EV3, so I can't test with one. Anyone have an EV3 and want to help out? Let me know!
  9. codefox421
    I've always really liked the look of the BRmk1 for no reason. In my effort to 7-wide-ify the Emerald Night, I decided to make a MOC of this classic carriage. I designed it in LDD using few references and viewing them infrequently, so it mostly just takes on the more distinguishing aspects of what make me love the BRmk1 rather than being a strict LEGO representation of a real-life thing. Having room to seat two minifigs side-by-side while retaining the curved sides was also something I strove for in the design. I played around a bit with the livery. I think just about everyone knows train window frames in tan are ridiculously expensive, so I first tried a crimson and cream livery (red and white). The white windows were less ridiculously expensive. It looks damn good on it's own, but with the Emerald Night locomotive, not so much. It was missing the rich earthy tones that the tan and brown possessed. So when I found out the 2x2x2/3 curved slope was available in dark brown, it was time for a repaint. Which color scheme do you like better? I chose to go with the more available and less pricey square windows, and I think the effect is okay. Though not the BRmk1, there are other coaches from the UK's railway past that have more boxy looking windows. This one is an open composite type just like my MOC: Finally, thanks go to my gf for taking the pics with her fancy camera. I've attached the LXF should anyone want it. 10194-emerald-night-carriage-tourist-06.lxf
  10. codefox421
    That's 4x4 for those counting in studs. The electronics only take up 3x4, the extra row of studs is to allow room on the PCB for mounting holes. Those would disappear for an enclosed version, and the traditional technic holes in the end could be added with a simple 1x4 technic brick. Now to actually design a case... along with improvements to the app, firmware, etc. It's a lot for one developer and one beta tester (with real jobs on the side)! We definitely appreciate any help we can get! :)
  11. codefox421
    As I remember, LEGO actually modeled their drivers after Ben's L drivers... or at least drew inspiration from them. In terms of size, a 48 tooth gear is a good substitute for the flanged XLs and a backward flanged L works for the unflanged XLs.
  12. codefox421
    Ah, I have seen that hopper in the back before. Liked it then, like them all now. Very attractive MOCs and a great scene overall.
  13. codefox421
    It's good to know I'm not the only one who visits eurobricks at work! XD If you have any questions or suggestions, please post them. Let me know if you are building your own copies. I like to know that others are benefiting from my work =)
  14. codefox421
    Since you seem to have some electronics experience, you could put together some Mindstorms NXT/EV3 compatible Bluetooth receivers in just a couple weeks (mostly waiting for orders to arrive) for about $26 a piece: http://www.eurobrick...showtopic=87340 Granted it wouldn't have a flashy plastic box.
  15. codefox421
    Wow that's quite the LEGO studio! I ought to take some notes for organizing my own collection of parts. Great little digger, by the way. The redesign really payed off; it's quite sleek and functional!
  16. codefox421
    That's amazing! Self-constructing machines are really cool, and there's quite a lot of research going into such devices. Haha, the easter-egg at the end of your video is well played! XD
  17. codefox421
    legoman and I got the kinks worked out, and he will be taking two receivers with him to BrickFair Virginia! While working with legoman, I realized the biggest failing of the BricksTer project has been the lack of documentation for getting started. Today, I'm proud to present BricksTer's first ever detailed, step-by-step Readme and How-To Guide! View it here in the repository. By the way, I calculate the cost of materials per device is about $26 USD.
  18. codefox421
    Wow, your bridge looks great! I was very surprised when the images first loaded. I've always thought of the rigidity of technic bricks, but the flex is much more expressive!
  19. codefox421
    Here I thought this issue would contain your RFID article, but I misread your other post. Silly me. Can't wait until the next issue!
  20. codefox421
    I wholeheartedly second this resource. You may want to take a look at this other page by Philippe too: http://www.philohome...s/motorcomp.htm The difference between the receivers has to do with the maximum amount of current that can continuously flow through each channel. For the V1 receiver, that's 400mA; for the V2, it's 1500mA. For reference, a since PF train motor draws 380mA on average. So if you're running only one motor, the V1 should be perfectly sufficient. If you want to run two motors on the same channel, the extra $10 is probably worth it. Any difference between the two in battery life or maximum speed should be negligible.
  21. codefox421
    Looking good. I've finished soldering my first board this morning. I'll post pictures later. EDIT: I can only test one channel at a time since I only have one spare PF lead. I'm testing the red channel right now (A in the firmware). I'm seeing it function properly when going forward, but the speeds seem to be reversed (i.e. 0-7-6-5-4-3-2-1) when going backward. I'm sure it's a firmware bug; just a matter of tracking it down. I expected to find some bugs as these are the first tests with the new board layout. EDIT: It was a super simple fix once I found it. I had forgotten to uncomment two lines that are necessary for the DRV8833 motor driver chip. Silly me. Working firmware is now checked into the new repository. Btw, I've split the repository into two, one for the android app and one for the hardware/firmware: https://github.com/BTbricks
  22. codefox421
    There is definitely some hardware that supports it, but there isn't support in the Android API yet. Plus, I would think NXT/EV3 compatibility is a necessity for a LEGO-compatible device! Anyway, I'll take another look at the app. Might be as simple as the image being too large, but then I'd think it wouldn't work on my phone either... hm... Being paired doesn't matter. Here's another try at resolving this: https://www.dropbox....-working-07.apk Thanks for working with me to clear this up. =) EDIT: There's a bad bug in that binary. I've fixed it and sent you a new link in a PM. It's probably best to debug outside this thread as there may be lots of back and forth to get to the bottom of this disappearing act.
  23. codefox421
    Nice find. The master version has an incompatible pin-out, though it is literally the same hardware running a different firmware. I received my BT modules yesterday. Just under two weeks, not bad. I must have ordered during a holiday or something last time. I recall it taking near a full month to arrive. I've also been researching a new BT module (with mostly the same pin-out). It offers dual mode BT 2.1/4.0, so there's potential for an iOS app if using that module (HM-12). The current module can only support Android (and NXT, EV3, PC, etc). Silly Apple and their costly1 MFi program Can you give this version a try? (You may need to uninstall the old version first.) https://www.dropbox.com/s/xek4e78etbzdbql/BricksTer-last-working-06.apk I've only changed the momentary controller yet. (I didn't think until I was finished that I should have done the speed controller first!) This may or may not fix it, but it's been something I've been meaning to figure out for a while now. If it doesn't fix it, I have another idea. 1 It costs money to develop with MFi, PCB space to fit their manditory IC, and firmware bloat to implement their special protocol. Bluetooth 4.0 operates outside the MFi program, but is not supported by Android (yet), NXT, EV3(?), etc.
  24. codefox421
    It probably is a screen resolution issue. I'll look into it. From where did you buy your BT modules? If you've received them already, I ought to order mine from there in the future!
  25. codefox421
    Hm... that's not right! On what model of phone are you running the app? Does it do the same thing for the momentary controller? Your HE looks great, nice and zippy like a high speed train should be. Can't wait to see it on 10.8V! My PCBs should get back from the fab tomorrow. I'm looking forward to getting them up and running, so I can make sure the firmware is in tip-top shape. I have some time to wait for the BT modules, but I have a single one that I can use for debugging in the meantime.
×
×
  • Create New...