@magharees, @stan, @Kalitapaws, @pacificmeister, and anyone who has reached out through PMs about getting one of the uSplits, as you probably know, all of the first batch is claimed atm. However, since I just got the PCBs for v1.1 HW I am thinking that I can hand solder up some of those for people who want uSplits before I order more assembled boards. This would give me a good sized group of testers for the v1.1 HW and allow me to verify that the updates didnt introduce any issues.
The changes made in the v1.1 HW are very minor:
Resistors were added in series with the UART RX and TX signals to protect the ESC and other connected devices from damage if the uSplit happens to become powered when the other devices are not. This is an unlikely scenario since the uSplit is powered from the comm port of the ESC, but it is still a possibility.
The ābootā button was replaced with a circuit that automatically puts the uSplit into bootloader mode when a USB cable is connected.
I will get a survey going to collect everyoneās info for the hand soldered v1.1 uSplits if people are interested in that.
The main difference between these and the main batch would be that this is still in the ātestingā phase and that this is assembled by you, by hand?
Hello @Ricco ! Do you already have an idea of when we will have to pay for the first batch ? I filled the survey long time ago but never had any confirmation that it was taken into account
And Matt, can you, please, give us a list of the people and the quantities in the first batch so everyone can be sure all is ok for him/her/it and on a good way. Thank you !
Loving the minor changes shows how mitch thought has gone in to it. Did the 5v and 3.3v rails get protected? This might be a stupid question what would happen if a connection vibrates louse in use would it brick any thing?
Asking because just found out iv got my 2nd dead VESC due to 5v rail death.
If you filled out the survey, you were taken into account. The survey was closed at 49 requested units. I got tracking for the first batch of uSplits two days ago Estimated delivery says today, but it just left Hong Kong, so I doubt that lol Once I receive them, Iāll take a couple days to program, test, and package them. Then, I will talk to everyone who filled out the original survey to get payment and get them sent out
@Darkie02, Thanks for the support What type of protection would you like to see on the 5v and 3v3 rails? I do not believe there is any scenario where a connector vibrating loose would brick anything. The 3v3, GND, RX, and TX signals are the only signals used by the uSplit. The other signals are connected directly to the same pins of the other connectors, acting like a Y-splitter cable. What was the cause of the 5v rail deaths you experienced?
1st one was the ground of the metopro torching part of the Battry pack when I was testing a board so totally my fault.
2nd one unsure as it was a VESC 6+ Tampa told me today the 5v rail died as to why was only powering metro pro and a remote, my conser would be the fact it could be powering 3 other devises and a usplit could be overloaded unknowingly so some type of auto resetting overload protection
Donāt even know the kind of loads some of the UTAR devises pull
The vibrating lose can have VESC apply full brake on canbus and old foxboxes brick if can disconnected in use was unsure if this issue could happen on the UTAR in any way
The uSplit will come wrapped in heat shrink, so the connections will not be exposed. That takes care for the possibility of things touching it and shorting out.
To protect the 5v and 3v3 rails, I could add resetable fuses to them both. I looked yesterday for some options and a well suited fuse costs $0.88. So adding this protection to the uSplit would increase the cost by $1.75. That fuse would trip almost immediately when 1A is drawn, wont trip ever for a draw less than 500mA, and will trip increasingly faster between 500mA and 1A.
The only time the throttle would be affected by UART vibrating loose is if a remote is operating in UART only mode. I do not condone the use of UART only remotes with the uSplit. Even in that case, the ESC should timeout once the cable is disconnected and let the motor free-spin.
The first batch of assembled uSplits arrived today! Iāll be testing them, packaging them up, and contacting those who filled out the survey over the next few days
I just posted FW v0.7 to the uSplit downloads page of my site. This FW fixes a couple known bugs in the uSplit FW. Anyone that has recently purchased the uSplit should follow the instructions here to update your uSplit. If any other issues are found, PM me with details so I can start on those
is the MCU mulitplexing known vesc commands and responses between the uarts? or is it multiplexing or duplicating individual bytes. whatās the strategy to avoid mixing up incoming and outgoing messages?
I donāt want to give too much away as the FW is what makes the uSplit what it is but I will say that it handles the comms on a packet-by-packet basis, not byte-by-byte
All solder joints look good and it functions properly so Iāve given them a go on the rest of the parts 
What type of protection would you like to see on the 5v and 3v3 rails? I do not believe there is any scenario where a connector vibrating loose would brick anything. The 3v3, GND, RX, and TX signals are the only signals used by the uSplit. The other signals are connected directly to the same pins of the other connectors, acting like a Y-splitter cable. What was the cause of the 5v rail deaths you experienced?
Iāll be testing them, packaging them up, and contacting those who filled out the survey over the next few days