I'd like to use TinyMiniMicro terminals, battery powered in my van 10-15v(12v AGM), power wheelchair 22-30v(24v gel), and mobile robots 34-54v(48v LTO) instead of the slow Raspberry Pis there now. DC-DC power supplies are easy to get and should replace the OEM AC-DC power bricks.
Which of the common TinyMiniMicro terminals will operate normally in this configuration without OEM brick?
Is there any universal SMbus solution to make TinyMiniMicros work with generic DC-DC supplies?
Maybe something that can splice into the stripped OEM cable, sniff the SMBus communications between OEM brick and computer, then configure itself to recreate the appropriate OEM brick responses when the OEM brick is replaced by a generic DC-DC?
// rant follows
In the past I've had monitors, laptops, wireless AP, and medical equipment fail to operate correctly using clean and correct voltage DC-DC supplies because the missing OEM power supplies employed SMBus communication which was now missing. Usually they power up and display a warning that a a non OEM power supply was detected. The crisp, flicker free, frustrating warning proves the power supplied would be sufficient to operate the device, it just wont. Plugging a Dell power brick into an HP laptop with the exact same connector and voltage results in the warning, and bootable OS, but refuses to charge the onboard battery. This is not among the touted benefits of SMBus, but I would bet it is a primary reason OEMs chose to use mutually incompatible messages. Ensuring loyalty to OEM replacement parts when generic could suffice.
I've had success using pico psu, industrial motherboards with a DC input range, and got lucky connecting 12v rated access points to 13.8v(12v nominal) batteries. I've also destroyed access points by connecting them to batteries. DC input voltage should be stated as an acceptable range and printed on the device that uses the power, not only the brick that gets lost.
I destroyed my minutes old Kickstarter Up Board Realsense robotics development kit because the mainboard and the nvme board used identical barrel jacks but different voltages. Wait months patiently, open box, tiny puff of smoke, done. Yes, it was my fault. But was it really?
This is not a problem we should still be having. There should be ubiquitous modular DC input. Not a universal voltage, but clear expectations for what will make a device operate. USB-C connector is not right for every device. But PD-PPS is the right direction.
Which of the common TinyMiniMicro terminals will operate normally in this configuration without OEM brick?
Is there any universal SMbus solution to make TinyMiniMicros work with generic DC-DC supplies?
Maybe something that can splice into the stripped OEM cable, sniff the SMBus communications between OEM brick and computer, then configure itself to recreate the appropriate OEM brick responses when the OEM brick is replaced by a generic DC-DC?
// rant follows
In the past I've had monitors, laptops, wireless AP, and medical equipment fail to operate correctly using clean and correct voltage DC-DC supplies because the missing OEM power supplies employed SMBus communication which was now missing. Usually they power up and display a warning that a a non OEM power supply was detected. The crisp, flicker free, frustrating warning proves the power supplied would be sufficient to operate the device, it just wont. Plugging a Dell power brick into an HP laptop with the exact same connector and voltage results in the warning, and bootable OS, but refuses to charge the onboard battery. This is not among the touted benefits of SMBus, but I would bet it is a primary reason OEMs chose to use mutually incompatible messages. Ensuring loyalty to OEM replacement parts when generic could suffice.
I've had success using pico psu, industrial motherboards with a DC input range, and got lucky connecting 12v rated access points to 13.8v(12v nominal) batteries. I've also destroyed access points by connecting them to batteries. DC input voltage should be stated as an acceptable range and printed on the device that uses the power, not only the brick that gets lost.
I destroyed my minutes old Kickstarter Up Board Realsense robotics development kit because the mainboard and the nvme board used identical barrel jacks but different voltages. Wait months patiently, open box, tiny puff of smoke, done. Yes, it was my fault. But was it really?
This is not a problem we should still be having. There should be ubiquitous modular DC input. Not a universal voltage, but clear expectations for what will make a device operate. USB-C connector is not right for every device. But PD-PPS is the right direction.