Strange IDN? returned string

[bwv1043]

I don't know how they designed the firmware but different interface (USB vs ethernet) can behave differently.  I've seen firmware designs that give you entirely different menu structure and access levels depending how you talk to it.

[JÞB]

---

@tian66 wrote:

I can control the load through USB. Do you think the cal mode will lock ethernet communication, but not USB?

Thanks!

---

I can't say one way or another without the users manual.  (Silly Chroma) but its easilly possible-  If the instrument suddenly changed behavior after a Cal lab tech got to it I would very much suspect the cal lab tech did something.  Again, can't tell without a manual....

[billko]

---

@JÞB wrote:

---

@tian66 wrote:

I can control the load through USB. Do you think the cal mode will lock ethernet communication, but not USB?

Thanks!

---

I can't say one way or another without the users manual.  (Silly Chroma) but its easilly possible-  If the instrument suddenly changed behavior after a Cal lab tech got to it I would very much suspect the cal lab tech did something.  Again, can't tell without a manual....

---

I've even seen instances where a manufacturer will "do you a favor" by updating the firmware without telling you when you send it out for a cal.  Then you wonder why your app isn't working any more.

[tian66]

I see. Thanks

[billko]

bad post

[tian66]

Chroma support cannot figure out this problem. What they can do is asking me ship back the ethernet card and check that.

So I think I have to move on by using USB instead of spending time todebug with them.

[truanttester]

We also have all kinds of hell getting these loads to talk correctly.

They are extermely picky.

If you figure this problem out, please post.  We find that we can alternately get one or two loads in the bay to talk, and then it latches us out and we can't get it to respond any further.