#11

Great! I ordered 3 PCBs from OSHPark last night, and they were added to a manufacturing panel within ten minutes. Performing surgery on my Teletype would be a bit too anxiety inducing, so I appreciate this alternative.

I’ll report back after I build it. I currently have 2x Ansible connected. I had previously experienced a lot of JF crashes in remote mode, so I had disconnected that. I’m finishing the builds on 2x TXo and 2x TXi, so I’m about to have a lot of modules connected to one TT.

Are there any specific tests I should run and report after the build?

1 Like
#12

any 0603 2.2k will do

http://www.digikey.com/product-detail/en/yageo/RC0603JR-072K2L/311-2.2KGRCT-ND/729676

1 Like
#13

thanks tehn!! your support on this is very much appreciated.

#14

If TT can’t support an ecosystem of attached modules it kind of defeats the purpose of offering an ecosystem. My plan was to attach a Just Friends, one Txo and one Txi so that sounds like it would work, but adding an Ansible or two would push it over.

1 Like
#15

have ordered via oshpark for the board. Am planning to share the power with teletype using this diy mini flying bus. Probably not much strain on the power and able to save a spot on the power busboard for other module.

mb.jpg2725×2592 2.36 MB

2 Likes
#16

well, in short, it can. there’s no reason to overreact to an edge case. without modding your TT or getting this cheap-as-nothing busboard, you can do everything that is promised with these modules.

what the TT mod or bus board enables:

  • prevents crash on user-error addressing of non-existent modules
  • allow read/write speeds to rates never imagined when this feature was added

i think it’s important to remember that this is an open source endeavor. we’re collectively figuring out a way to wedge in more functionality than was intended-- which to me is far more interesting that having a locked protocol and a very private company never talking about their plans. the fact that @bpcmusic made expanders in the first place is simply wonderful-- so let’s embrace the ride we’re all on.

21 Likes
Teletype Firmware i2c Debugging
#17

I apologize for what I realize, in retrospect, was an overly-harsh tone. As a product person myself, primarily in the corporate world but now in the non-profit world, I’ve suffered through many ecosystem debates, and among them none were as painful as those brought about by success.

So what you say is not just true but good: working through a problem as a community in an open way is an excellent way to address issues. Ensuring that conversation includes some clear guidelines about edge cases is important, as those are the places explorers go first, followed by everyone else if they are successful.

Cheers.

7 Likes
#18

Hi sakul, I’m in Germany and would be more than happy if I can buy a complete board from you. Please let me know if this would be possible.

#19

@tehn I try again, hoping not to be too annoying with my requests:

Is the bus board supposed to be the more efficient solution for the I2c stability bugs compared to the teletype resistor mod?

Thanks!

#20

@Leverkusen The result on stability is identical between the two solutions. The difference is in whether you want the bus board, and whether you’re comfortable modifying your teletype.

2 Likes
#21

I would also be interested in the board and necessary parts if you are ordering

#22

Great, thanks for the confirmation! On the picture above it does not look as if modifying the teletype would be more elaborate than building the bus board.
I will contemplate about it a bit since I already have the old bus board. On the other hand the board is cheap enough to enjoy the extra i2c connectors…

#23

ok, i’ve had an even better idea for a potentially more elegant solution.

TT is (wonderfully) only one board. the i2c “bus board” could be a thin mezzanine, that connects to both the power jack (with a 5x2 female connector) and the i2c jack (with a 3x2 female connector).

there would then be a load of 3x2 male connectors on the back for i2c, and a male power connector (so there won’t need to be redundant cabling.) the extra regulator and resistors can be hidden on the board. all in all it should be an elegant (and cheap) solution.

of course, i’ve already ordered some of yesterday’s version and that will also be totally fine. so i’ll only make time to draw up this new version if there are other people interested.

12 Likes
#24

Definitely interested. Hoping this ecosystem expands wonderfully and I want a to welcome all my potential new friends.

1 Like
#25

Oh, I just ordered the original new bus board PCB - I did not really understand the idea of the new one, technically it does not make any difference, does it?

#26

cough

:stuck_out_tongue:

3 Likes
#27

Also interested in the mezzanine solution, as in addition to solving the “pull-up situation” & providing more i2c connectors it also seems to be a more mechanically sturdy solution than the small bus board PCB.

#28

I dont have any trilogy module so i’ll only have 1 txO connected to my TT. Will this still be a problem for me?

#29

@sam haha, whoa that is embarrassing. i need to improve my reading comprehension skills.

@Leverkusen it will do the exact same thing. this is simply ergonomics.

1 Like
#30

In terms of the ergonomics, I found trying to get 3 modules connected to TT and the previous I2C board tricky enough with my current set of I2C cables.I’m wondering if the bus board would be better than a mezzanine solution? Of course, I could also just make myself some longer cables.

1 Like