Solutions Cubed Technical Support Forum: MOTM3 Stops Responding - Solutions Cubed Technical Support Forum

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

MOTM3 Stops Responding

#1 User is offline   Gabe 

  • Starting Member
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: 18-February 10

Posted 18 February 2010 - 01:47 PM

I am observing some very odd behavior from a MOTM3 unit. Specifically I have it setup in binary protocol mode at 19.2k and I am able to send some commands, but not others. It will send me ACKs when I send a software reset, write the P term register, write the I term register, and write the D term register. However, when I try to get the position, I get no response back. I have also tried using the rev10 test software. It just says "check baud / comm settings" and won't really do anything.

Any ideas?

Thanks,
-Gabe
0

#2 User is offline   Gabe 

  • Starting Member
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: 18-February 10

Posted 18 February 2010 - 02:04 PM

View PostGabe, on Feb 18 2010, 04:47 PM, said:

I am observing some very odd behavior from a MOTM3 unit. Specifically I have it setup in binary protocol mode at 19.2k and I am able to send some commands, but not others. It will send me ACKs when I send a software reset, write the P term register, write the I term register, and write the D term register. However, when I try to get the position, I get no response back. I have also tried using the rev10 test software. It just says "check baud / comm settings" and won't really do anything.

Any ideas?

Thanks,
-Gabe


Well I'm not sure what was wrong with it, but I used the bootloader to install the rev 1 firmware and then rebooted it into "restore factory defaults" mode and now it seems to be working fine.
0

#3 User is offline   Lon 

  • Advanced Member
  • PipPipPipPipPipPip
  • View blog
  • Group: Root Admin
  • Posts: 640
  • Joined: 03-March 04

Posted 19 February 2010 - 01:36 PM

Gabe,

Sorry to hear that you had a problem. But less sorry that you found a way to fix it.

It's hard to conclude what would have caused the issue you had. It could be that some of the firmware was not installed correctly, but that's a wild and unsubstantiated guess (I've never seen an example where the code sort of works). If you purchased product recently the firmware was installed by the IC vendor.

Let me know if anything else happens.

Lon
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users