I agree on the risk with the USB ports, you wouldn't typically design
something like this. But I appreciate the out of the box thinking that got
me past that. The current limiting etc can easily be done in the end
device, and that's what I choose to do. In reality, only one person is
likely ever going to use this thing and we are already plugging USB ports
into DB9s so.. Brian did at least consider the M100 user group and
instructed everyone to use plastic DB9s so I think that is sufficient.

Jim - congrats on the new gig. Hope you find some time to play soon. I used
both your code and Brian W's to get my PDDuino going. Found the re-org of
the code very helpful in figuring things out and appreciated all the
documentation. I was chasing a few bugs that it looks like you guys both
sorted out, or moved, in the latest master branch. Biggest thing I saw was
the PDDuino would wander off looking for label information and not respond
to drive commands. Like when trying to load TS-DOS from the UR2 it would
fail unless you could force the PDDuino to get a disk label, IE: swap to
TS-DOS rom, list a directory, then it would happily go on to the load step.
It is somewhat working now so I took a break from it, although my M0 still
doesn't work and I'm not 100% sure why but I think it's the guy from SdFats
fault..

Brian




On Mon, Jul 12, 2021 at 4:04 AM Scott McDonnell <mcdonnell.j...@comcast.net>
wrote:

> “That IS a bit risky. Ideally there should be some sort of current limit
> to avoid drawing more than 50 or 60 ma. But I don't know how to do that in
> a small practical way.”
>
>
>
> Wouldn’t a 82 (or 100 for 50ma) ohm resistor in series do the trick?
>
>
>
> Scott M.
>
>
>
> *From: *Brian White <b.kenyo...@gmail.com>
> *Sent: *Sunday, July 11, 2021 2:33 PM
> *To: *m...@bitchin100.com
> *Subject: *Re: [M100] A decent replacement for M100 "Feet"
>
>
>
>
>
>
>
> On Sun, Jul 11, 2021, 8:14 AM Brian Brindle <bbrin...@gmail.com> wrote:
>
> > I didn't think anyone else was actually trying them out.
>
>
>
> BKW - I just assumed the MountT was wildly popular based on how simple and
> awesome it was. I'm genuinely jealous that I didn't think of it.. I'll be
> honest, there is something in my training/experience that was like DO NOT
> HOOK THINGS UP WITHOUT BUFFERING/PROTECTION/ETC!
>
>
>
> You are not wrong of course. But little diy toys like this have to be
> compromises to make them doable.
>
>
>
>
>
> Then you go and pop a USB jack on the BC port and the world didn't end and
> it's worked great.
>
>
>
>
>
> That IS a bit risky. Ideally there should be some sort of current limit to
> avoid drawing more than 50 or 60 ma. But I don't know how to do that in a
> small practical way.
>
>
>
> At least I made sure the BOM has a plastic plug and stressed in the docs
> why this is important even though that plug is uncommon and expensive while
> normal metal shell plugs are dirt cheap.
>
>
>
> (the metal shell of normal de9f shorts the power and ground pins, you
> should never use a metal shell de9f in the bcr port)
>
>
>
>
>
>
>
>
>
>
>
> I'm a daily carrier of my Model-T, I write a lot but 90% of what I do with
> it is useless tinkering to make it do stuff similar to what my phone and
> readily available laptop can do. In fact, in most instances my laptop is
> hooked up and running to debug the thing that isn't working right on the
> M100. That being said, the PDDuino provided weeks of endless debugging
> entertainment.
>
>
>
> Yes that does still need a lot of debugging sorry ;)
>
>
>
> Jim Brain did some work on it and the idea didn't work out, but there is a
> lot he did that are good ideas that I'd been meaning to cherry pick.
> Actually I already did some of that.
>
>
>
> It's still not quite all the way there yet. It still doesn't work with
> other clients like WP-2. I think it's still limited to TS-DOS.
>
>
>
> My problem last time I was working on it was I think enabling debugging is
> screwing it up. Things work without debugging, and break with debugging,
> well great now what? haha
>
>
>
>
>
> I checked out your latest code for it recently with the new main loop and
> it works very well now and is my "daily-driver" for storage.
>
>
>
> I very much respect all of you guys who can not only do this stuff but
> document it where others can play along. I seem to fail miserably at that.
> I do have a current project in the works that I hope to change that with..
> We will see.
>
>
>
> After 20+ years of using M100s I stumbled on an M102 cheap and snatched it
> up. I worked at Radio Shack back in the 90s as a teen and remember lusting
> after the discontinued M102 but hadn't touched one since then. I much
> prefer the size/weight and keyboard to my M100. I also like the system bus
> being accessible like it is so built a little jig for my project. I
> followed your example and added a USB port to it to power my PDDuino, once
> I get a real board made for it I'll get the right length USB cord and it
> will look as awesome as the M100 does with the MountT, but here it is:
>
>
>
> http://niedobry.com/mod100/images/bus_jig.jpg
>
>
>
> Brian
>
>
>
>
>
> Nice.
>
>
>
> Yeah The upside down ports on 102 are annoying. IOlivetti is the same. For
> those I just decided to rely on right-angle usb cables rather than multiple
> versions of the pcb. Half the point was to remove all the ways to get
> things wrong like with the wrong serial wiring etc. Though, at least for
> the Feather boards, since they have asymetrical pins, you could safely have
> two sets of holes on the same board. For teensy boards, you can already
> plug them in wrong now, but at least with only a single set of holes, you
> can have a single silkscreen showing the single correct way.
>
>
>
> For that bus board, if you use a vertical usb port, it can be moved below
> or above the system bus so that it doesn't block the printer port, and you
> can include a pass through pin header so the system bus is still usable for
> DVI. Though the port would stick out then. Maybe a horizontal port could
> still be used just in some other position.
>
>
>
> Well thank you for the kind words. I think everything I've done so far has
> actually been pretty low hanging fruit. I could not have designed REX for
> instance. And I have yet to manage even a hello world in machine language.
> I didn't write either dlplus or pdduino just picked them up and did a
> little work on them, etc.
>
>
>
>
>
>
>
>
>
> On Sat, Jul 10, 2021 at 4:08 AM Brian K. White <b.kenyo...@gmail.com>
> wrote:
>
> On 7/9/21 4:21 PM, Peter Vollan wrote:
> > You'll have to explain what that is past the printer and serial ports.
> https://github.com/bkw777/MounT
> https://github.com/bkw777/BCR_Breakout
> https://github.com/bkw777/PDDuino
>
> I didn't think anyone else was actually trying them out.
>
> --
> bkw
>
>
> > On Fri, 9 Jul 2021 at 13:01, Brian Brindle <bbrin...@gmail.com
> > <mailto:bbrin...@gmail.com>> wrote:
> >
> >     I found this thing called a "Laptop Foot" at the checkout of my
> >     local Barnes and Noble the other day. I am slightly embarrassed to
> >     admit that I paid $12 for it but also I've been very happy with how
> >     it works so...
> >
> >     It's just the one wedge, you pop it under the back of the M100 and
> >     it just sort of tripods. It's very stable, no rocking or anything
> >     and has it at a decent angle for me. I find it easier to keep up
> >     with and quicker to deploy than my plastic feet.
> >
> >     Quick Amazon search for "Laptop Foot" or Universal Laptop/Notebook
> >     stands will reveal 4-packs available from $10-$13 but totally lacks
> >     the instant gratification I received for 4x the price, not to
> >     mention the blank look from my SO as I ran from the checkout to the
> >     Starbucks inside, ripped my rubberized wedge from its box and
> >     plopped my M102 on it happily exclaiming "Hu?! HU?!! Awesome right?!"
> >
> >     She didn't respond, likely because it was too awesome for her to
> >     handle. Anyway, I thought you guys would appreciate it.
> >
> >     Behold - the M100 foot!
> >
> >     http://niedobry.com/mod100/images/ <
> http://niedobry.com/mod100/images/>
> >
> >
> >     Brian
> >
>
>
> --
> bkw
>
>
>

Reply via email to