[ryann]

Lon,

After getting everything working great, I set aside the MOTM3 to work on other parts of the project. When I returned to it, I had symptoms just like Kirk in this post. To summarize, D6 would never flash, and I couldn't communicate with the board in any way. I re-loaded the latest firmware (version 2), then put the board in run, mode 6 and pulled both limit switches to ground.
Putting the board back in mode 4, I turned it on and D6 flashed 5 times. The situation improved, but I'm still having problems.

• The MOTM rev10 test software will give me all the register values ONLY if I uncheck temperature. If temperature is checked, I get "CHECK BAUD / COMM SETTINGS".
  
• I can no longer communicate in ACSII mode. I've tried two different terminal programs at 19.2 and 9600. I get no echo or feedback. D6 doesn't seem to ever flash while I'm typing. I'm trying simple things like "R01 04".

Any suggestions are appreciated.

[Lon]

Hey Ryan,

Try loading firmware version 1 back into the MOTM3. Version 2 is relatively new, and I'll go back and take another look at it to see if it might be causing an issue.

Lon

[ryann]

I loaded version 1, turned it off, put it in mode 6, grounded the limit switches, turned it on then off after it stopped flashing, then put it in mode 4 and turned it on again.
The behavior is the same.
I can see register values in the test software if I turn off temperature, but nothing in terminal program if I change DIP to ASC.

[Lon]

I'm looking into this.

Loading the firmware with the bootloader did not impact using the binary control software. I could use it without turning off the temperature register. I know that the older MOTM2 could not be used with the revision 3 test software unless the temperature measurement was diasabled. That was because the temperature measurement did not exist on that hardware. So I'm not seeing this issue here. The MOTM3 is on a green PCB and the MOTM2 is on a blue PCB.

I am seeing a problem executing Read commands in ASCII mode. This appears to be related to the bootloader. If that's the case it may take some time to figure out. I can execute a Write command in ASCII mode after using the bootloader.

I'll keep working on this to see what the issue is.

Lon

[Lon]

I think the problem I was having was with buffer overruns. I was alternating between our AN1000 PID tuning software and a hyperterminal window to test the MOTM3 in ASCII mode. Unfortunately, I forgot that AN1000 was implemented using the binary protocol.

I'm able to communicate successfully with the MOTM3 in ASCII and binary after bootloading new firmware (rev1 or rev2). That's using hand typed controls with hyperterminal, or our internal production test software that uses the ASCII mode.

However, I will write an automated routine to test ASCII mode over night with continuous communication attempts.

Some things to try on your end:

1. When switching from program to run modes you need to cycle power.
2. Restore defaults in mode 6 (like you did) after cycling power.
3. ASCII characters should be upper case. R01 00 good, r01 00 bad
4. ASCII commands must be followed by a carriage return and linefeed. In hyperterminal this can be selected under file/properties/settings/ASCII setup (select "send line feeds with line ends" box.
5. Hyperterminal should have "none" selected for handshaking.
6. If you use binary mode to test communication, cycle the power when swtching to ASCII mode in order to clear any incomplete communication stored in the communication buffer.

[Lon]

I did set up an automated test program, and it ran 20,000+ communications in ASCII mode with no failures. If you like you can send your unit to me for testing.

Lon

[ryann]

I did the following:

• Put the MOTM3 in program mode
  
• Turn on power
  
• Load rev2 firmware
  
• Turn Off power
  
• Switch to mode6 (19.2, ASCII)
  
• Jumper NLIM and PLIM to ground.
  
• Turn on power
  
• Saw D6 flash 7 times
  
• Wait 10 seconds
  
• Turn off power
  
• Remove jumper
  
• Switch to Run, mode 4, (19.2, ASCII)
  
• Turn On
  
• Saw D6 flash 5 times
  
• Start HyperACCESS 8.4, 19200-8N1, The boxes for "send line feed with each line" and "echo typed characters locally" are checked.
  
• Connect
  
• It seems to work.

I don't remember if the MOTM used to echo characters back (it doesn't now), but I can even read the temperature register.

-Thanks for the help

[ryann]

Everything seems to be working perfectly. I think powering down anytime a mode is changed may prevent the problem.

Thanks.

[Lon]

I'm glad you were able to communicate with the MOTM3. My automated software ran over the weekend with 2,222,746 good communication packets and no failures.