Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About GeekDadKen

  • Rank
    New Forum User

Contact Methods

  • Website URL

Profile Information

  • Location
    SF Bay Area
  • Occupation

More About Me

  • Interests
    I'm the Owner/Publisher of the GeekDad blog.
  • Favorite Decorating Holiday?
    Christmas/Winter Holidays

LOR Software

  • LOR Software Version
  • License Level

Recent Profile Visitors

255 profile views
  1. So, a follow up on my progress back from this small disaster. I've replaced the USB485 adapter, and that got the network going again to an undamaged board for pass-through, and to an undamaged flood. But discovered that the ethernet cable that had been the link between the flood that had its power cord cut, and the CMB24D that was damaged was also non-functional anymore (go figure!). Replaced that, and I now have one flood doing a little bit of work again out in the front yard. My next question is that k6ccc suggested the comms chip on the board could be replaced, rather than buying a wh
  2. I do now! (Learned how to do that with a servodog over the holidays but hadn’t realized it was an option for the CMB as well). Thanks!
  3. Yup; everything is running off a laptop in the garage that's on 24/7.
  4. Yeah, that's my first step - replace the adapter and see if I can get other devices that weren't connected at the time of "the incident" to connect again. And if the RS-485 chip on the CMB24 can be replaced, that's a much better solution than replacing the board!
  5. Yup, that's pretty much the story. Just feels nuts that the surge from the power cut could jump to the network connection.
  6. Here's the story: Two devices on the network for our general landscape lighting in the off-holiday period: CMD24D and one of the 50W floods. Doing some yard trimming, the power cable to the flood gets cut, with some sparks. Afterward, the CMD24D appears fried; no blinking light on the board, though if I unplug it for a while and plug it back in, it will flash once and go dark. I have done a couple proper resets using the pin, to no avail. Verified that the AC outlet is live. Have tried connecting boards/devices to the USB485 directly, but while the Comms Listener sees the USB485 (I see "
  7. I very much appreciate your working on this! I actually made significant progress when I realized I had purchased digital servos, and probably wanted analog. I picked up some analog, and for the first time actually got them to move inside Sequencer. But they are still somewhat inconsistent. I played it once, and they did what I wanted them to. Stopped the sequence, started it over, and they just clicked slightly, rather than moving through the full range of motion. I'm wondering if this has to do with how you set them up in the utility to deal with the end of coms or power down?
  8. Indeed, I've tried it both ways, and haven't seen any movement. 😕
  9. Totally appreciate that! I'm wondering if there's some network setting or similar thing that I've tweaked wrong, that might affect working via Sequencer rather than the utility.
  10. Yup, I added it to the preview design as a ServoDog, which meant it added the 8 sub-channels to the sequence. I have the servo wired to the first sub-channel, which works in the utility, but not in the sequence. I'm sure this is something simple somewhere, but there's so little info online about sequencing with servos that I'm lost.
  11. Hmm, no. My understanding from the one video I could find on this issue here in the forumes is that when the channel was configured in servo mode, the sequencer treats the channel like any other light, and turning it "on" and "off" on a given beat would move the servo arm back and forth through its range of motion (as defined in the ServoDog Utility). Is that the wrong take? Thanks for your help!
  12. Hope someone can give me a little basic help. I've added a ServoDog to my network for the first time this year, to do some simple motions on some signs (wagging Pluto's tail). I just can't get it to work yet. The device is on my network, and I can get the servo I have attached to its first sub-channel to move in the ServoDog Utility. But when I try to make it work in a sequence, there's nothing. It's in my Preview with the proper Channel ID, and like I've seen on the one video example here in the forums, I'm just ramping the channel up and down, to no effect. What am I missing?
  13. Just want to say thanks for the info! I'd received a replacement Pixie 8, and because it was a new model, I hadn't paid attention to the dip switches. When I would assign an ID, it would only stick for a couple of minutes, and then I'd lose the unit on the network, and it would do weird, random stuff. Turns out it was resetting to ID01 and the following auto-assigned IDs, and picking up programming for other devices in my setup. Fixed the dip switches last night, and everything is working perfectly now.
  • Create New...