Isopod Com1 problem

[cjh]

Got the isopod with the Com cable. The first time I plugged it in, the MAXTERM gave me back everything ok.

ISOMAX V0.5
OK

I did a couple of test like
REDLED OFF
GRNLED OFF
...

After I turned off the computer and came back to use the ISOPOD, once again I cant get an OK for some reason. I think Windows XP does something with the com1. So I uninstalled com1 and reinstalled it. enabled com1 and tried to test again. The ISOMAX V0.5 comes up, but no OK.

I tied the SIN and SOUT and tried to see if it was echoing back, and that worked fine.


I am going to take the ISOPOD to work and test it out on my work machine to see if I can get an OK response.

Any other ideas what the problem could be ?

Coby

[nmitech]

Download the window terminal program, NMITerm here,
http://www.newmicros.com/download/NMITerm.zip

Install and click on the HELP topic for Firmware's Ascii setting instruction.

More IsoPod documents, sample programs, appnotes here,
http://www.newmicros.com/store/product_details/download.html

[cjh]

I have tried both NMITerm and Maxterm, they will not give an OK status.

The SIN must be working becuase the isopod is getting my ALT-T and coming back with ISOMAX V0.5, and since it is sending the string 'ISOMAX V0.5' the SOUT must be working also.

The cable is fine, and the power supply is fine. I am wondering if there is something I have set with windows XP for the com1 port.

The only time I got an OK status was the first time I hooked up the ISOPOD. After I turned it off once, I never have gotten an OK status again.

[nmitech]

Try this,


Unplug the power from the IsoPod. Just the Power line, and leave the serial cable connected.
Restart your XP
Run NMITerm or Maxterm
Now plug in the power to the IsoPod then hit the ENTER key several times. If it reponds with OK then it is ready. If it does not respond to the key stroke, please email to nmiproduction@newmicros.com to obtain the RMA# and instruction to return for repair/replacement. If you have a Quick-Kit please send back the custom made serial cable also to check out.
Also you may want to check this IsoPod with other PC if it is posible, before you send it back. We've tested with XP @2.0Ghz here with out any problem. It works just fine with Maxterm & NMITerm

[cjh]

That did not work, I turned the power off on my computer, unplugged the power cable, loaded Maxterm
and then plugged the power cable back in, and still no OK.

I did the same for NMITerm.

before I send it back, I am going to try to use it on my new machine first.

I am using a cable from newmicros, and last night I tested it with a BasicX 20x4 LCD, and it worked fine. The Return key was working. so Im not sure what is wrong with isopod.

Im going to test it on another machine first.

[rcorreia]

I'm having the exact same problem. Also using version 0.5 of IsoMax.

I've checked all my connections etc, Even tried bypassing the autostart routine with no luck.

Was a resolution found or did the user have to send in his board for a replacement?

RC.

[nmitech]

I don't have a latest status of "cjh" isopod.

cjh, would you keep us posted on the status of your Isopod please.

Thanks!

[nmitech]

NMI production dept. received an IsoPod from cjh in February. The returned IsoPod was tested and found nothing was wrong with cjh's IsoPod. The IsoPod was sent back to cjh and We have not hear anything from cjh since then.

cjh, Please keep us posted with your latest info. Thanks!

[rcorreia]

It's fixed.

Turns out to be what I originally supsected. I had been playing with some code the other night and I believe I lost power during an upload that was supposed to write to the EEPROM.

Unfortunately the document "Autostarting an IsoMax Application" complicated things a bit. The diagram which illustrates which pins to jumper must be refering to IsoPod V1 where I assume J3 was used for something entirely different then J3 on a V2 board.

At any rate I checked out the IsoPod Schematics figured out the correct location of the pins to jumper and everything worked like a charm after that.

Thanks for the help everyone!

Reading through the forums definitely helped me track down the root of the problem.

RC