Forum Replies Created
-
AuthorPosts
-
in reply to: FlexCase Relay Drive Stop Working #17390
Hi xuanlang,
Damage to the individual output MOSFET is the most common cause we have seen for the behaviour you are describing. One good way to test if the hardware is damaged would be to run the same MCU code on another FlexCase S in a controlled scenario.
In this case I recommend connecting the supply voltage for the high side output to a voltage (~12V) limitted & current (~500mA) limited source, such as a power supply, for testing. One potential software bug could have been activiting both the high and low sides on the half-bridge at the same time, shorting the output due to the software configuration.
If you’ve confirmed your software is working correctly, I would be confident that the issue is hardware damage and we can organize the repair. Let me know what you find and I can assist further.
Best regards,
Rhyse
in reply to: FlexCase Relay Drive Stop Working #17379Hi xuanlang,
Given that implimentation, it seems strange that there were issues. The output should not have suffered an overvoltage condition. There is isolation between the gate and the microcontroller, so the micro should be fine even if the output is damaged.
Generally with the FCS we have seen that the outputs can be damaged, as there is a moderate amount of overvoltage protection (highly inductive loads could trigger damage) and no overcurrent protection built into those circuits. The circuits can unintentionally be damaged, which is why we’ve decided to add more protections into future revisions.
I’ve sent the repair guide to you for your reference.
in reply to: FlexCase Relay Drive Stop Working #17352Hi garrettbailey,
Based on your message, I suspect that you are referring to our FlexCase S and the output was damaged due to overcurrent or overvoltage. The outputs on that product do not yet have protection (This feature will be available on the FCS after mid-March 2024).
If you’re driving relay coils, that should have been within specification, but its possible there was some damage somehow. For the most stability, we recommend driving outputs low side on the FCS.
The good news is that the outputs is repairable with a rework station and we can send you replacement parts. I will send you the repair guide directly.
Hi garretbaily,
The analog input guide is a good place to start (https://www.audesseinc.com/resources/analog-input-guide/).
The input voltages are scaled down to the MCU voltage level though internal circuitry. When it says that the voltage range is 0-36V it means that you can supply the analog input with any voltage in that range and you will be able to read it. Any voltage higher than 36 V will read 36, and you won’t be able to read any negative voltages.
Note that there is some non-linearity past about 30V on the readings.
Please reach out if you have any other questions.
in reply to: Flashed software not working on restart. #17139Hi nikhillemos,
It seems like your issue is resolved and will be considered closed, thank you for updating us. Please reach out if there are more issues.
Rhyse
in reply to: PWM output control CDC shock absorber #17128Hi David,
Thank you for the detailed posting. Based on the data you provided I believe you are triggering the current protection mechanism on the FlexBench, which has a continuous current maximum of 1.1A and trip current of 1.95A.
My recommendation would be to try and distribute the current among two low side drives simultaneously (using the same FTM) if you can. The next safest approach would be to use an external, higher current output driver.
Please let me know if you have any followup questions,
Rhyse
in reply to: Measuring -10V – 10V signals #15893One way to do this is to build a simple resistor circuit to convert the singal from -10-10 to 0-5V.
I have attached a reference image and LTspice model so you can see how it works.
Best,
Rhyse
Attachments:
You must be logged in to view attached files. -
AuthorPosts