mvalkama Posted October 23, 2014 Report Share Posted October 23, 2014 We are using MC52i for sending alert SMSs and they been working nearly without hitch for few years, but something in latest installation is causing odd problems. I can initialize the modem as PLC side via Visilogic just fine (using MC55i/BGS2T strings, those are the only ones that work), but the Com initialize never succeeds. I also tried TC35 strings for Com init which also fail but work in other locations for this model (IIRC MC52i is successor for TC35). Next I tried to change COM port, just in case there was something wrong with that, but no luck with that either. Then I started paying extra attention to SI82 for modem status and that showed value of 19, which should be possible only for SI83. Not sure what "checks: slots timeout" even means... They happened to have old TC35 on site that I tried as replacement and it fell in place without problems so cable seems fine. Got a replacement MC52i a week later but that fails similarly. v570 has latest firmware in it and Visilogic used is 9.7.9b2. The latest firmware for modem was released in 2010 so I expect that we have same version on all them (all installed during past three years). Kinda running out of ideas of what to try next with this one, any suggestions are welcomed. I have one BGS2T for testing that I might try as replacement next as the TC35 temporarily installed is needed elsewhere soon, but would be nice to understand what is causing this trouble. Quote Link to comment Share on other sites More sharing options...
AlexUT Posted October 26, 2014 Report Share Posted October 26, 2014 Hi, You can restore defaults in Com Init FB and repeat test. MC52i is not in supported modems list, so you can test "Other" type. Does problem happens with a specific Cellular Provider or with all prowiders? Is SIM card charged and have budget? You can test if modem send/receive SMS from "Modem Services"->"SMS Options". *This does not include Modem Init commands, PLC send during COM Init. You can make COM port traffic capture during COM Port initialization by PLC. You can do this by use of COM port "sniffer". To obtain it, please contact your distributor. Sniffer part numbet is MJ10-22-CS16. *You can find explanation in document(VisiLogic docummentation should be installed): "C:\Program Files (x86)\Common Files\Unitronics\Documentation\Manuals & Specs\Miscellaneous\Communications Sniffer.pdf", or look for this document at Support site. If you cannot obtain COM port sniffer - you can copy all commenda from COM Init FB to Notepad, and execute one by one from Terminal Program, Like Hercules, where you can save Modem requests/replays. From this capture you can find Modem replies with error. If you cannot localize problem - send test results to support@unitronics.com. BR. Quote Link to comment Share on other sites More sharing options...
mvalkama Posted October 30, 2014 Author Report Share Posted October 30, 2014 You can restore defaults in Com Init FB and repeat test. MC52i is not in supported modems list, so you can test "Other" type. Does problem happens with a specific Cellular Provider or with all prowiders? Is SIM card charged and have budget? Tried all these, no luck. Defaults, different com port, other type, tried another SIM from different provider, the SIM we started with works fine on the older modem. You can test if modem send/receive SMS from "Modem Services"->"SMS Options". *This does not include Modem Init commands, PLC send during COM Init. Ah, this is something I hadn't thought about. You can make COM port traffic capture during COM Port initialization by PLC. You can do this by use of COM port "sniffer". To obtain it, please contact your distributor. Sniffer part numbet is MJ10-22-CS16. ... If you cannot obtain COM port sniffer - you can copy all commenda from COM Init FB to Notepad, and execute one by one from Terminal Program, Like Hercules, where you can save Modem requests/replays. From this capture you can find Modem replies with error. Thought about sniffer cable but don't have one on hand. I tried to use info screen serial monitor to see what goes on between devices, but never got there fast enough to see anything besides an error reply after some waiting (adding delay to code didn't occur to me until I got home). The location is bit far so can't easily test things, but I'll try to get someone bring the modem to me so I can try manual initialization. If you cannot localize problem - send test results to support@unitronics.com. Think I'll do this to eliminate any simple error I just can't see. Then will try to replace modem with BGS2T. Thanks for your suggestions! --mika Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.