Roboteq sdc2160 cannot connect to computer

6 years 2 months ago #29529235 by fnick2812
Hi,
Im using SDC2160 with the latest firmware SDC21XX-Firmware-Update-v13-031114.bin. it worked fine but after I loaded my script onto the roboteq. The software Roborun lost contact with the roboteq and could not connect with it any more. In my script is a loop to print out a message, but i forgot to put a delay. so, it turned out that the roboteq is too busy to print the message and ignore the request from the Roborun. when I use Realterm, I can see that roboteq still prints out the message. Do you have any solution to stop the script or erase the memory.
I tried to update firmware via COM by using Roborun. But it did not format the memory completely. My troublesome script still runs after updating.
I think by using realterm i can send a command such as ~BRUN 0 to disable the script right? Can you tell me if the solution is possible and the decimal format of the message ~BRUN 0

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

6 years 2 months ago #29529237 by Griffin Baker
Replied by Griffin Baker on topic Roboteq sdc2160 cannot connect to computer
To stop a script and clear it all out, go to the scripting tab and type in "terminate" minus the quotation marks.

Then turn on controller. As soon as the pc tries to connect to the controller, "click on download to device". This may take a few attempts as it is about the timing.

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

6 years 2 months ago #29529239 by fnick2812
luckily, when i load the older firmware into the controller, somehow it erased the script. haha
actually, i made mistakes like this quite a lot of time. before this time, i managed to do as u said because the script, i guess, was long enough so that the software could connect for just a second before the controller was lost. However, this time, the software did not even detect the controller at all. This kind of issue may be required to have ur attention because it easily render the controller malfunction.

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

6 years 2 months ago - 6 years 1 month ago #29529243 by Griffin Baker
Replied by Griffin Baker on topic Roboteq sdc2160 cannot connect to computer
What does the status led on the controller show? Is it a rapid blink, pause and then rapid blink again? If so, then it sounds like the controller is in a state of constant reboot. This can be caused by a faulty script.

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

6 years 1 month ago #29529276 by fnick2812
did u read what i have said?? i said that i already reflashed the controller. Last time, one of my controller had the same problem and it continuously rebooted. I tried different way and no results so i threw it aside and order another controller.

Can u plz go and test to see how it happens? it s not the first time u know. every time, i reported the bug, you guys never excepted it and just said useless things. The time i was stuck with the problem that one channel moved fast, the other moved slow when they had the same setting. i searched alot but never saw any kind of sentence like because of the stupid firmware. only after that 2 months, the new firmware was published then the issue was resolved. and it is f** irritating, wasted my time.

u want to deny what i said. here is another shitting problem i encounter with sdc2160 today:

settimercount(4,5000)
top:
print("timer=", gettimercount(4),"\n")
wait(100)
goto top

the timer 4 does not count down. when i replaced timer4 into timer1, timer1 counts down. do i need to reflash another firmware?

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

6 years 1 month ago #29529306 by Griffin Baker
Replied by Griffin Baker on topic Roboteq sdc2160 cannot connect to computer
We confirm that there are 4 timers in the SDC2160 firmware. However timers must be numbered 0 to 3 and not 1 to 4.

For execution speed reasons, Microbasic does not check arrays boundaries, and so timer(4) touches an invalid RAM location which then causes the controller firmware to crash.

Also, as a rule NEVER set the script autostart until you have validated your script. Recovering from a buggy auto-starting script can be difficult.

If your script for whatever is faulty, you can recover from it by going to the script tab and typing in "terminate" minus the quotes. Click on "download to device" as soon as the controller tries to connect to the utility. This will send the terminate command in the script so that it stops.

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

6 years 1 month ago #29529344 by fnick2812
I see. Thanks

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

Moderators: tonysantoni
Time to create page: 0.105 seconds