Hello!
As much as I wish it is the Led Zeppelin song. Somehow for no particular reason my server refuses to connect to remote stations using GSM network. The configuration of the system was not modified before the error appeared. SIM cards are working, remotes are working, no power problems, no GSM network problems, no problems at all :( and still...
Office Setup:
- WinXP SP3
- logger net 3.4.1
- gprs base modem Audiotel (Siemens MC35)
Remote Station:
- datalogger CR510
- gprs base modem Audiotel (Siemens MC35)
Check out the error log. Any suggestions?
********************************
Loggernet TroubleShooter Network Analysis
3.7.2009 5:36:40
COM1: ComPort
Communication State is normal.
The COM Port connection is COM1.
audiotel: PhoneBase
Communication State is critical. (Ensure your setup and hardware configurations match)
The modem type is <default modem>.
PhoneRemote_9: PhoneRemote
Communication State is critical. (Ensure your setup and hardware configurations match)
The phone number is 041430094.
reber1: CR10X
Communication State is unknown. Communication may not have been attempted since LoggerNet has started.
Scheduled Collection is in secondary retries
Scheduled to collect at 3.7.2009 10:00:00
Collection intervals passed with no data collected: 1
It has been 2d 17h 24m 38s since data has been collected
Recent Communication Errors
Fail PhoneRemote_9: 3.7.2009 0:03:37 | "Connect message not received"
Fail COM1: 3.7.2009 1:06:35 | "write operation timed out","10035","A non-blocking socket operation could not be completed immediately."
Fail COM1: 3.7.2009 2:07:56 | "write operation timed out"
Fail COM1: 3.7.2009 4:04:30 | "write operation timed out","10035","A non-blocking socket operation could not be completed immediately."
Fail PhoneRemote_9: 3.7.2009 5:04:36 | "Connect message not received"
Fail audiotel: 3.7.2009 5:04:36 | "Dialing failed"
Fail audiotel: 3.7.2009 5:05:42 | "Dialing failed"
Fail COM1: 3.7.2009 5:08:51 | "write operation timed out"
Fail PhoneRemote_9: 3.7.2009 5:35:00 | "Connect message not received"
Fail audiotel: 3.7.2009 5:35:00 | "Dialing failed"
Fail PhoneRemote_9: 3.7.2009 5:36:12 | "Connect message not received"
Fail audiotel: 3.7.2009 5:36:12 | "Dialing failed"
*******************************************************
* Last updated by: parovelb on 7/3/2009 @ 2:15 AM *
The msconfig does not show the loggernet process.
The netstat gives: "localhost:6789 ESTABLISHED"
Here are the latest news:
Loggernet TroubleShooter Network Analysis
6.7.2009 12:03:19
COM1: ComPort
Communication State is normal.
The COM Port connection is COM1.
audiotel: PhoneBase
Communication State is critical. (Ensure your setup and hardware configurations match)
The modem type is <default modem>.
PhoneRemote_11: PhoneRemote
Communication State is critical. (Ensure your setup and hardware configurations match)
The phone number is 051438942.
reber8: CR510
Communication State is unknown. Communication may not have been attempted since LoggerNet has started.
Scheduled Collection is in secondary retries
Scheduled to collect at 6.7.2009 13:00:00
Collection intervals passed with no data collected: 2
It has been 5d 23h 45m 31s since data has been collected
Recent Communication Errors
Fail audiotel: 6.7.2009 12:00:05 | "Dialing failed"
Fail audiotel: 6.7.2009 12:01:11 | "Dialing failed"
Fail PhoneRemote_11: 6.7.2009 12:02:02 | "The line is busy"
Fail audiotel: 6.7.2009 12:02:02 | "Dialing failed"
Fail PhoneRemote_11: 6.7.2009 12:02:53 | "The line is busy"
Fail audiotel: 6.7.2009 12:02:53 | "Dialing failed"
Anyone!?
IT looks like Loggernet is having a basic problem talking to the Audiotel modem.
Can you stop Loggernet, navigate to
C:\campbellsci\loggernet\logs
Delete all the files to start a clean sheet.
Start Loggernet and then make a few test connections.
Then go back to that directory and ZIP all the files into one zip and email them to me:
andrew dot sandford at campbellsci.co.uk
Changing the dot and at appropriately.
It is also first worth checking the cables and power to the modem.
For those that are interested:
After studying the logs we could see that Loggernet was dialling OK but the modem never getting a connection after taking varying times to timeout.
Parovelb reported to me he found that moving his base station antenna (the base modem being GSM) he was able to get connection to most remote sites.
He is now investigating why the GSM signal suddenly changed in his office - it could be a network issue or local interference.
It is a pity the GSM/GPRS modems are not clever enough to report they don't have a good signal in the dial response rather than just NO CARRIER!
I agree with Andrew it is a pity the GSM/GPRS modems are not clever enough to report they don't have a good signal in the dial response rather than just NO CARRIER!
I guess it would be nice to have a window open when connecting to monitor in realtime what is going on with the communication.
Another advice I give to all interested. Checking the signal with your mobile phone is not always enough. I do not have any problems talking on the mobile phone with people from the office while the modem is giving me headaches (AUDIOTEL GPRS, dual band, same operator).
I am not sure if this will be helpful or not, but accessing the modem via hyperterminal and issuing the AT+CSQ command will return the returned signal strength indication value, along with channel bit error rate value.
Command AT+CSQ
Response +CSQ: 12,0
General consensus is that a minimum rssi value of twelve is required for reliable service.
Doing this would however mean closing down Loggernet to free up the comm port, but would give you something to check if communications falter again!