Closed t0mpr1c3 closed 4 months ago
@oskay @andz82
We have made some prototype enclosures, that worked pretty well, but weren't able to go to the next stage with that. @t0mpr1c3 we can chat about that offline.
There's not much issue with changing to a lower-cost USB/micro interface, but take care that it does not accidentally increase the cost instead.
I would be very careful about going to a different I/O expander. The AYAB software has to support every version of the AYAB hardware, and adding yet another chipset to support should only be done if there is a clear and compelling reason.
Fair point about the I/O expander. Happy to chat offline about enclosures.
An attractive suggestion mentioned to me today was to reserve a pin on the microcontroller for a row-counting Hall effect sensor.
Hi Tom,
- Comparators are going to be faster than ADC for evaluating the Hall sensor output.
We have to keep in mind that there obviously are different hall values for different machine types, therefore these comparators would have to be compatible to either levels (https://github.com/AllYarnsAreBeautiful/ayab-firmware/blob/master/settings.h#L49)
- Eventually, it will become desirable to support USB-C. I would not be surprised if Apple are planning to phase out USB-A on their laptops. USB-C is already standard on iPads and phones, which we may want to support some day.
Good point...it may be worth to check. I like the USB-C port as well for it's rigidness. Still, if a host device currently has USB-C, there is still the possibility to use a USB-C to Micro-USB cable for now. USB-C <-> USB-C cables are still pretty rare in the wild (at least in my bubble of colleagues, family and friends).
- A chip with more IO pins would not require I2C expanders.
Guess that's probably a decision of costs...bigger chip might cost more than I2C expanders.
USB C support is trivial; that's just a cable type, and it's straightforward enough to switch to a USB C cable. The real concern is that future devices may, at some point, not support USB 2.0. Thus far, newer versions of USB (including properly built USB 3 cables) do generally support USB 2.0 for backwards compatibility.
We have to keep in mind that there obviously are different hall values for different machine types, therefore these comparators would have to be compatible to either levels (https://github.com/AllYarnsAreBeautiful/ayab-firmware/blob/master/settings.h#L49)
Yes, a disadvantage is that you would need one comparator (and hence one pin) per level. The data acquisition would be basically instantaneous, whereas reading the ADC takes about 0.1ms. Although I suspect UART communication between the Atmega and its USB bridge is the major bottleneck in terms of response time.
USB C support is trivial; that's just a cable type, and it's straightforward enough to switch to a USB C cable. The real concern is that future devices may, at some point, not support USB 2.0. Thus far, newer versions of USB (including properly built USB 3 cables) do generally support USB 2.0 for backwards compatibility.
This is good to hear. I hate micro USB, the cables are flimsy and always breaking. A real downgrade from mini USB.
The micro connectors are designed to last for twice as many cycles as mini: https://en.wikipedia.org/wiki/USB_hardware#Durability
It's not the connection that fails, it's the cable itself.
On Sat, 7 Aug 2021, 15:50 Windell Oskay, @.***> wrote:
The micro connectors are designed to last for twice as many cycles as mini: https://en.wikipedia.org/wiki/USB_hardware#Durability
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/AllYarnsAreBeautiful/ayab-hardware/issues/8#issuecomment-894699827, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM63QRNVC5QCVBFE6P2UBTT3WFB3ANCNFSM4JQ3PKBA .
Sure, but if you have different color LEDs, you add the problem of matching their apparent visual brightness, and it becomes critical to not substitute which LEDs are used. Also take care to not use LED color as an important indicator since some segment of the population is colorblind.
I would like to have a option to use a different motor to make all carriages moterised with some switch on each end for it to go left to right with out doing it manualy and control its speed ect, like end stops with a timing belt or linear rail system with nema motor that grips all carriages like a hand for example..
Also would like some options or opinions for automatic electronic colour changer with solenoids that can be controlled through the shield or added ect.
Counters could be oled too? Or use a arduino tft? With a mount..
Interested in enclosures aswell and a upgrade for all them yellow parts like ayab done with the metal covers ect would be nice, something with rgb colour changing and control thats useful as a light for the bed too..
Can we replace the hall position sensors with arduino ones with ayab shield? They tend to brake alot from transport vibration and are getting hard to find.
Long time no updates, jeez..
There isn't anything complicated about the Hall sensors as far as I can remember. Remanufacturing them would be mostly just trial and error to get the sensitivity right.
On Sun, Feb 19, 2023 at 7:03 PM Rixstaa @.***> wrote:
I would like to have a option to use a different motor to make all carriages electronic with some switch on each end for it to go left to right with out doing it manualy. Would also like to know if theres a different hall position sensors we can use as originals are becoming hard to find, maybe schematic to make some etc or already a arduino one that will work? I was even thinking adding a tft screen would be nice for some check functions.
— Reply to this email directly, view it on GitHub https://github.com/AllYarnsAreBeautiful/ayab-hardware/issues/8#issuecomment-1436138504, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM63QUSE5L2N2CYLYFQYQLWYKYD5ANCNFSM4JQ3PKBA . You are receiving this because you were mentioned.Message ID: @.***>
Eventually I would like to re-design the AYAB interface. Some improvements that I could suggest are straightforward (e.g. longer USB cable). Others incremental (e.g. migrating from Adafruit Mini Metro to something cheaper, 1x MCP28017 instead of 2x PCF8574, common bus resistor networks). In my view the most important area for new development is revamping the enclosure. But I will need to play around a good deal before coming to any conclusions on that.
Does anybody have any thoughts or feelings that they would like to chip in?