djm

Eurobricks Citizen
  • Content Count

    267
  • Joined

  • Last visited

2 Followers

About djm

Spam Prevention

  • What is favorite LEGO theme? (we need this info to prevent spam)
    <p> Trains and 60197-1 </p>

Profile Information

  • Gender
    Male
  • Location
    Auckland

Extra

  • Country
    New Zealand

Recent Profile Visitors

1171 profile views
  1. Your mileage may vary. On my Windows 10 machine, I fired up Bricx to see if I could connect to an NXT via Bluetooth. My NXT is named djm01. Using the menu item "Tools/Find Brick" menu item, opened up a dialog window. Within that window, I expanded the "Port" drop-down list. In that list there were two entries with respect to my NXT; one labelled BTH:DJM01 one labelled BTH:DJM01:<then a hex code> I successfully connected to the NXT with Bricx using the entry with the hex code. Although the actual hex code value isn't especially important, it corresponds to the value in the "Association Endpoint address" (visible using Device Manager and looking within the "Details" tab of the properties for the device). So my suggestion would be to take a second look at the list of ports and see if there is another entry which includes a hex code and try that one. Regards, David
  2. djm

    L-draw parts for custom track radi

    For the r104 (and other ME Models curves), there is Ronald Vallenduuk's LDraw file available for download at https://github.com/Duq42/ldraw-parts. The l-gauge,org diwnload doesn't appear to be available on the wayback machine, so fingers crossed that the website comes back up (or someone makes the file available). David
  3. Simply a confirmation that I've tested the EV3 with multiple sensors and it works as desired with version 1.5. Caveat for anyone plugging the NXT touch sensor into the EV3. From what I've seen, the reading for an NXT sensor shows a high raw data value for when not pressed and a low raw data value when pressed. The EV3 sensor shows a low raw data value when not pressed and a high raw data value when pressed. Code accordingly! Regards, David
  4. Thank you. I've tested the Boost hub and can confirm that the ports now are detected and work as expected. Some further diaganosis from me regarding the EV3 behaviour; I have three EV3s (don't ask!) and they are all exhibiting the same behaviour. they are all run firmware version 1.09H If I plug a touch sensor into port 4, it successfully detects the sensor being pressed if I then plug a second touch sensor into port 1, it detects it (shows it in the log) and recognises it being pushed but no longer recognises port 4's sensor being pushed. remove the second sensor from port 1 and plug it into port 2. It detects it (shows it in the log) and recognises it being pushed but no longer recognises port 4's sensor being pushed. remove the second sensor from port 2 and plug it into port 3. It detects it (shows it in the log) and recognises it being pushed but no longer recognises port 4's sensor being pushed. (Dang this should be #4) If I start again, reconnecting to the EV3 and plug the first sensor into port 1, it successfully detects the sensor being pressed. If I then plug a second touch sensor into port 2, it does not detect it (and does not shows the detection in the log). It does not detect the sensor in port 2 being pushed but does detect the sensor in port 1 being pushed. If I unplug the sensor in port 1 it will then detect the sensor in port 2, including when it is pushed but when the sensor is plugged into port 1 again, the port 2 sensor stops being detected. remove the second sensor from port 2 and plug it into port 3. it does not detect it (and does not shows the detection in the log). It does not detect the sensor in port 3 being pushed but does detect the sensor in port 1 being pushed. If I unplug the sensor in port 1 it will then detect the sensor in port 3, including when it is pushed but when the sensor is plugged into port 1 again, the port 3 sensor stops being detected. remove the second sensor from port 3 and plug it into port 4. it does not detect it (and does not shows the detection in the log). It does not detect the sensor in port 4 being pushed but does detect the sensor in port 1 being pushed. If I unplug the sensor in port 1 it will then detect the sensor in port 4, including when it is pushed but when the sensor is plugged into port 1 again, the port 4 sensor stops being detected. So it looks like the EV3 is only picking up input from the lowest numbered port. I don't know whether or not this diagnosis is of any help. Regards, David
  5. It appears that the latest firmware release from LEGO for the Boost Hub (2.0.00.0017) has remapped the port IDs. When I connect BAP to my Boost Hub, Port C in BAP turns the B port motor and port D in BAP is the Boost Hub C port. There is no access using BAP to Boost hub's A and D ports. David
  6. I hope you're not too busy to play with your LEGO! A question regarding the EV3 and using multiple touch sensors. When I have one touch sensor plugged in (port 1), it recognizes the sensor and shows me the "raw" data value. I can see the raw data value changing as I press the sensor down and release it. However, when I plug a second touch sensor into the EV3 (port 2) , although it shows me the raw data value, it does not show any change in the value when the button is pressed or released. The touch sensor is not faulty as if I have the second sensor connected to port 2 and nothing connected to port 1, the change in raw data value is visible when the sensor is pressed/released. So my question is whether BAP supports multiple touch sensors in an EV3 and whether or not anyone else has successfully used this set-up? I'm hoping to use multiple touch sensors of this ilk, for controlling monorails: Regards, David
  7. I've just started looking into using @Cosmik42's Brick Auotmation Project. I had a bit of a stumble as I had renamed my SBrick and hence was encountering the "connected but discarding" issue but renaming it back to SBrick remedied that. I've also successfully connected to my EV3, which fortunately didn't matter that I had renamed it. I next tried connecting to an NXT but I have been unsuccessful in doing that. I was wondering whether anyone has successfully managed to connect to an NXT? If so, would you be willing to post what you had to do to get a successful connection? Regards, David
  8. djm

    [GBC] The Akiyuki Project

    I recall posting about the following errors in the Fork-to-Fork:
  9. For 2, the menu path is "View/Editing Views/Export/POV-ray view export".
  10. Video of GBC at Japan Brickfest 2019
  11. I haven't used them myself, but @BrianGT did post an image showing a comparison between the crown and the headlight. Take a look at this post: Regards, David
  12. djm

    [GBC] The Akiyuki Project

    I can't recall whether there was a conscious reason for making that choice or not. It could just as easily have been me making a mistaken identification of which parts were used in the model. I always considered my reverse-engineering of Akiyuki's GBC modules to be an "interpretation" rather than a replication. Perhaps experiment and see whether there is a difference in behaviour. David
  13. djm

    [GBC] The Akiyuki Project

    Way back on page 29 of this thread. Akiyuki's original model used one mechanism, which was what was originally replicated when we reverse engineered the module. The top of the spiral lift changed in a subsequent Akiyuki iteration. I came up with an approximation of it subsequently, which is what my "delta" to the model recreates. Regards, David
  14. djm

    [GBC] The Akiyuki Project

    Power is supplied via a transformer. Thus for the US, something like this. Therefore the controller can be used in many countries - you just need an appropriate power supply. David
  15. djm

    [GBC] The Akiyuki Project

    Are you sure? I only see one 2x8 on page 5 (step 6). The 2x8 plate on step 4 is a technic 2x8 plate not a 2x8 plate. The second 2x8 plate is in step 9 on page 7. I'm not aware of any other 2x8 dark bluish gray plates in the instructions. David