Short Circuit Protection Setting

2 years 5 months ago #29535414 by skelmir
In the 2.1 firmware and the 2.1 RoboRun utility the "General / Short Circuit Protection" setting is gone even after resetting the controller. Previously I had that setting at "Medium". What is the default setting now? The problem I have is that I can't seem to get the 2.1 firmware to use closed loop mode. Open loop works fine. The same motor settings also work fine with the 1.8d firmware and the 2.0 firmware. Once I move everything over to the 2.1 firmware (different physical controllers - same motors), the short circuit protection always trips as soon as I try to move the motors. All wiring has been triple checked and in fact if I switch out the controller for one of the older controllers everything works fine.

So I'm curious why this setting was removed and what the new default setting is. Could there be a short internal to the controller that only triggers in closed loop mode?

Please Log in or Create an account to join the conversation.

2 years 5 months ago #29535415 by skelmir
Reading through the release history I see a few "Fixed false positive short faults". For 2.1 11/20/2020. I'm using the SBL2360T controller running 2.1 and I'm fairly sure this is a false positive short. 

Please Log in or Create an account to join the conversation.

2 years 5 months ago #29535416 by skelmir
I successfully downgraded the same controller to 2.01 firmware and everything works fine. So I think that proves that there is still a false positive short.

Please Log in or Create an account to join the conversation.

2 years 1 month ago #29535481 by lio98
I think i might have your same issue. With v2.01 everything worked but now on v2.1 I get the short circuit. Do you mind sharing the procedure to downgrade back to v2.01. I must be looking in the wrong places since i cant find it. Thanks enormously. 

Please Log in or Create an account to join the conversation.

1 year 7 months ago - 1 year 7 months ago #29535659 by BFish
Has there been a solution to downgrading to V2.0? I am having a similar issue.
Thanks.
Edit: I have tried updating the firmware (downloaded from website) in the PC Utility and am not having luck with the USB or the COM options. 
Attachments:

Please Log in or Create an account to join the conversation.

9 months 3 weeks ago #29536206 by hendersonbd
Is this going to be fixed? The problem was reported many months ago.  Also, it has been reported that people are not able to easily revert the firmware back to an older file.  

Please Log in or Create an account to join the conversation.

9 months 2 weeks ago #29536208 by RJL
you can workaround it by setting the detection level in the script by adding:

setconfig(_THLD, 1)

0 is default, 1 is medium, 2 is low
More info can be found on page 92 and 412 of the manual.

r

Please Log in or Create an account to join the conversation.

Moderators: tonysantoni
Time to create page: 0.064 seconds