I checked into the reports of OMS not seeing the networked MTP2 if
connected with an MTPAV. I don’t have an MTP2 but used an MTP1.
Setup:
MTPAV is the first unit with the MTP1 networked.
Both MTPAV and MTP set to Fast communication speed.
MTPAV set to “This box ID 1–8, Net Port =MTP”. This is the exact text
from the MTPAV led.
The MTP is set to 1-8 on it’s power\/box select switch.<\/p>\n
Results: OMS will not find the networked MTP. But, if you select Add
device and give it one of the ports 9-16. Then the networked MPT works
great.
Both units work as expected in this configuration.<\/p>\n
Probably whats happening is customers give up when OMS does not find the
networked port. Most don’t know you can add a port beyond 8 and the MTP
driver will work.
The MTP will not work if it is set to 9-16 which may also be a factor in
this problem.
To recap: Both units set to fast. The MTP set to 1-8, not 9-16. OMS will
not find the MTP, but by using the Add device trick it will work.
Thanks
ML
———–<\/p>\n
And this from OMS code writer Doug Wyatt:
—–
Little known fact about the MTP OMS driver: It never ever shows networked
interfaces as two icons. It always shows one icon to which you can attach
devices on ports 1-17 (17 being a networked standard interface).<\/p>\n
Compare this to Opcode drivers which show multiple interfaces with multiple
interface icons.<\/p>\n
Doug
————<\/p>\n
Hope this info helps in some trouble shooting and tech support.<\/p>\n
If you have any questions, give me a call<\/p>\n
-mac<\/p>\n
—————————————————-
Mac McCormick<\/p>\n","protected":false},"featured_media":0,"template":"","categories":[],"tags":[34385,34386],"storecat":[],"itemids":[],"manufacturers":[],"acf":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n