crget-discuss Mailing List for crget
Status: Beta
Brought to you by:
bascule
Menu
▾
▴
crget-discuss — General discussion about the crget utility
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(4) |
Nov
(2) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Gerry C. <ger...@ta...> - 2005-07-08 12:59:13
|
I started looking at crget some time ago, downloaded it and had a few problems. The tempo of other research activities had kept me from pursuing it. I've been looking at single-board linux systems to talk to my instruments, but now, with A/D offered on some of those systems, and the ability to write the code either myself or hire graduate labor, I doubt I'll pursue the Campbell stations in my network expamsion. I'm still interested in anything someone comes up with, but I'll likely be following more as an interested observer... gerry Octavi Fors wrote: > Dear list members, > > I've been member of this list for two years and note its extremely low > traffic. To tell the truth, I contributed very few because I have not > been in the need of using Campbell stations under linux. > > However, this will change in near future. So I wonder in which degree of > completeness crget works when retrieving data from Campbell stations. > Why crget stopped in 0.1b version and didn't evolve since 2003? > Is that because other open source projects have been more succesfull? > > Sincerely, > -- Gerry Creager -- ger...@ta... Texas Mesonet -- AATLT, Texas A&M University Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.847.8578 Pager: 979.228.0173 Office: 903A Eller Bldg, TAMU, College Station, TX 77843 |
|
From: Octavi F. <of...@am...> - 2005-07-08 06:44:37
|
Dear list members, I've been member of this list for two years and note its extremely low traffic. To tell the truth, I contributed very few because I have not been in the need of using Campbell stations under linux. However, this will change in near future. So I wonder in which degree of completeness crget works when retrieving data from Campbell stations. Why crget stopped in 0.1b version and didn't evolve since 2003? Is that because other open source projects have been more succesfull? Sincerely, -- Octavi Fors Astronomy Department University of Barcelona SPAIN |
|
From: <caf...@ma...> - 2004-09-20 14:29:44
|
I'm managing two cr10x meteorological stations down here in Brazil, Sao Paulo University, moving to a Linux/Debian based computer thanks to crget. However, I could not find a way to extract chunks of data stored in the datalogger using -l option. Worst, when trying I had two cr10x locked. Even using Campbell/Windows software I'm not accessing the dataloggers anymore. Could someone help me with that? Best regards, Carlos -- ----------------------------------------------------- Dr. Carlos Augusto de Sampaio Franca Depto. de Oceanografia Fisica Instituto Oceanografico da Universidade de Sao Paulo Praca do Oceanografico 191, Butanta Sao Paulo, SP Brasil CEP 05508-900 (55)(11) 3091 6564 (55)(11) 3091 6610 (FAX) ----------------------------------------------------- |
|
From: LEAP e. <en...@no...> - 2004-07-01 19:25:24
|
I'm using crget 0.1b, which is the only available version, as I can
tell. I want to pull data from a CR10X datalogger across the modem link.
>From prior posts, I found people using
crget -d /dev/modem 8675309
I am using two different machines, both running Debian Sarge with Linux
2.4.x. One machine uses the HSF softmodem drivers while the other uses
LTmodem drivers. I do not have a dial-up ISP, although I have verified
that the modems are able to successfully ring other telephones in the
office.
When I connect the telephone line and attempt to fetch data using the
syntax above, the modem connection starts and appears to work, syncing
the time on the datalogger and printing out startup messages:
energy@LEAP:~/crget$ ./crget -d /dev/modem 1379
--12:17:23-- Getting data via modem /dev/modem from logger at 1379
=> 'logger_data-1379-20040701'
Opening port /dev/modem... port opened.
Initializing modem... initializiation error, retrying... done.
Dialing 1379... connected.
Not updating clock: Skew of 20 seconds is within 30 second threshold.
Opening port /dev/modem... port opened.
Initializing modem... initializiation error, retrying... done.
Dialing 1379...
Invariably, the connection breaks with the "initializiation error,
retrying" message as seen above.
Line 214 in logger.c states:
/* XXX Okay, here's how this goes. I was running into a
bug where I would get a command back from the
datalogger that wasn't the original one I issued.
This is a cheap hack to correct this problem.
Basically, we wait for the command we issued to be echoed
back to us. If we get something else in the mean time,
the bug has been encountered, so we just reinitialize, retry,
and hope for the best.
*/
Any suggestions? Are the files in CVS more recent? ( I didn't have any
luck checking them out as anonymous. )
Ryan
--
Ryan J Nicholson
Energy Conservation Coordinator
Lifestyle & Energy Awareness Program
Northland College
1411 Ellis Ave
Ashland, WI 54806-3999
|
|
From: <ben...@id...> - 2004-05-25 08:27:48
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: Tony A. <tar...@at...> - 2003-11-21 20:27:13
|
You might try passing the same dialing strings through a terminal program that crget is passing to the modem, and see if you get the same "ERROR" back from the modem. Tony Arcieri On Wed, 19 Nov 2003, Trond Rafoss wrote: > Dear list, > I have now made some progress in my crget tryout. > > After digging up another modem, now a Dynalink external fax modem > > compiling and executing crget yields the following: > > [root@localhost crget]# make all > gcc -g -Wall -c buffer.c > gcc -g -Wall -c connect.c > gcc -g -Wall -c download.c > gcc -g -Wall -c fd.c > gcc -g -Wall -c format_data.c > gcc -g -Wall -c logger.c > gcc -g -Wall -c main.c > main.c: In function `main': > main.c:204: warning: implicit declaration of function `asprintf' > gcc -g -Wall -c modem.c > gcc -g -Wall -c output.c > gcc -g -Wall -c xmalloc.c > gcc -o crget buffer.o connect.o download.o fd.o format_data.o logger.o main.o modem.o output.o xmalloc.o > [root@localhost crget]# ./crget -d /dev/ttyS0 064949473 > --23:45:52-- Getting data via modem /dev/ttyS0 from logger at 064949473 > => 'logger_data-064949473-20031119' > Opening port /dev/ttyS0... port opened. > Initializing modem... done. > Dialing 064949473... Error while dialing 064949473: ERROR > Dialing 064949473... Error while dialing 064949473: ERROR > Dialing 064949473... Error while dialing 064949473: ERROR > Dialing 064949473... Error while dialing 064949473: ERROR > Dialing 064949473... Error while dialing 064949473: ERROR > Too many dialing attempts, giving up! > > With the USRobotics modem, the process hang already at the modem initialisation step, but with this modem all seems to proceed successfully until the dialing starts. > > Do you have any suggestions on passing the latter problem (see output above) > > Best regards from Trond Rafoss > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Crget-discuss mailing list > Crg...@li... > https://lists.sourceforge.net/lists/listinfo/crget-discuss > |
|
From: Trond R. <tro...@PL...> - 2003-11-19 22:53:47
|
Dear list,
I have now made some progress in my crget tryout.
After digging up another modem, now a Dynalink external fax modem
compiling and executing crget yields the following:
[root@localhost crget]# make all
gcc -g -Wall -c buffer.c
gcc -g -Wall -c connect.c
gcc -g -Wall -c download.c
gcc -g -Wall -c fd.c
gcc -g -Wall -c format_data.c
gcc -g -Wall -c logger.c
gcc -g -Wall -c main.c
main.c: In function `main':
main.c:204: warning: implicit declaration of function `asprintf'
gcc -g -Wall -c modem.c
gcc -g -Wall -c output.c
gcc -g -Wall -c xmalloc.c
gcc -o crget buffer.o connect.o download.o fd.o format_data.o logger.o =
main.o modem.o output.o xmalloc.o
[root@localhost crget]# ./crget -d /dev/ttyS0 064949473
--23:45:52-- Getting data via modem /dev/ttyS0 from logger at 064949473
=3D> 'logger_data-064949473-20031119'
Opening port /dev/ttyS0... port opened.
Initializing modem... done.
Dialing 064949473... Error while dialing 064949473: ERROR
Dialing 064949473... Error while dialing 064949473: ERROR
Dialing 064949473... Error while dialing 064949473: ERROR
Dialing 064949473... Error while dialing 064949473: ERROR
Dialing 064949473... Error while dialing 064949473: ERROR
Too many dialing attempts, giving up!
With the USRobotics modem, the process hang already at the modem =
initialisation step, but with this modem all seems to proceed =
successfully until the dialing starts.
Do you have any suggestions on passing the latter problem (see output =
above)
Best regards from Trond Rafoss
|
|
From: Tony A. <tar...@at...> - 2003-10-08 06:01:14
|
I usually use 'anonymous', although any password should work, I believe. Sourceforge is in the process of upgrading their CVS servers, and at present their backup server (the one used for anonymous access) doesn't appear to be up, so I'm attaching a tarball with the latest CVS sources. Tony Arcieri On Tue, 7 Oct 2003, Gerry Creager N5JXS wrote: > I just tried to get the cvs tree. I guess I'm missing it somewhere, but > I found no reference as to what to use for the anonymous access > password. And it does want one... > > Any suggestions? > > Thanks > Gerry > Texas Mesonet > http://mesonet.tamu.edu (down for a data disk casualty, back soon) > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Crget-discuss mailing list > Crg...@li... > https://lists.sourceforge.net/lists/listinfo/crget-discuss > |
|
From: Gerry C. N. <ger...@ta...> - 2003-10-08 00:08:12
|
I just tried to get the cvs tree. I guess I'm missing it somewhere, but I found no reference as to what to use for the anonymous access password. And it does want one... Any suggestions? Thanks Gerry Texas Mesonet http://mesonet.tamu.edu (down for a data disk casualty, back soon) |
|
From: Tony A. <tar...@at...> - 2003-10-07 21:24:59
|
On Tue, 7 Oct 2003, Trond Rafoss wrote: > I am now trying crget from linux (RedHat 9) over a USRobotics Sportster > 28,800 external modem with the following result: > > [root@localhost crget]# ./crget -d /dev/ttyS0 064949473 > --11:24:18-- Getting data via modem /dev/ttyS0 from logger at 064949473 > => 'logger_data-064949473-20031007' > Opening port /dev/ttyS0... port opened. > Initializing modem... initializiation error, retrying... initializiation > error, retrying... initializiation error, retrying... initializiation > error, retrying... initializiation error, retrying... initializiation > error, retrying... initializiation error, retrying... Couldn't reset modem > [root@localhost crget]# Something in the modem initialization code is failing. You may want to try printing the value of the buffer that's being pulled from the modem in the modem_reset() function in modem.c by adding the following line around lines 218: After buf[x] = '\0'; add: puts(buf); To display the contents of the buffer and see how the modem is responding to ATZ. You can change the modem initialization string on line 195 of modem.c as well. I'll try to make these values easier to tweak in future releases. Tony Arcieri |
|
From: Trond R. <tro...@PL...> - 2003-10-07 09:43:49
|
Dear list,
I am very keen on getting crget up and running against our weather =
station network.
I am now trying crget from linux (RedHat 9) over a USRobotics Sportster =
28,800 external modem with the following result:
[root@localhost crget]# ./crget -d /dev/ttyS0 064949473
--11:24:18-- Getting data via modem /dev/ttyS0 from logger at 064949473
=3D> 'logger_data-064949473-20031007'
Opening port /dev/ttyS0... port opened.
Initializing modem... initializiation error, retrying... initializiation =
error, retrying... initializiation error, retrying... initializiation =
error, retrying... initializiation error, retrying... initializiation =
error, retrying... initializiation error, retrying... Couldn't reset =
modem
[root@localhost crget]#
I have looked through the sources of modem.c and fd.c wheter it could be =
possible to customize the modem initialization string (in order to try a =
model-specific init string). However, I think I have to learn more =
C-programming before being be able to penetrate that issue.
Dear users of crget, can you provide me some info on successful =
combinations of crget setups / modems ? Hopefully I will be able to =
reproduce such setups, or at least dig up some of my errors.
Best regards from Trond Rafoss
The Norwegian Crop Research Institute
|
|
From: Tony A. <tar...@at...> - 2003-08-19 22:19:35
|
As its userbase is quite small, crget seems to have many issues lingering in untested portions of the code. crget is a heavily refactored reversion of the original code I was using, and thus TCP/IP-based access might have been broken during the refactoring process. I'd like to help locate some of these bugs and increase its use, as it appears to have some issues with the protocol implementation that are preventing it from communicating successfully with some of the dataloggers on our network. I'll go through and try to add some helpful debugging information, then update the CVS. Hopefully we can get this particular problem worked out. Tony Arcieri On Tue, 19 Aug 2003, Trond Rafoss wrote: > After compiling the source I issued the command: > > ./crget -Cip 4001 128.39.187.138 > > The result was: > > --11:47:34-- Getting data via TCP/IP connection to 128.39.187.138:4001 > => 'logger_data-128.39.187.138-20030819' > Serial error: Unable to flush buffer while sending command! > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Error: Too many failed attempts to connect to datalogger... giving up! > > > I also tried at connection using the security code (not necessary for just reading data): > ./crget -C -c 1432 -p 4001 128.39.187.138 > > The result was: > --12:07:15-- Getting data via TCP/IP connection to 128.39.187.138:4001 > => 'logger_data-128.39.187.138-20030819' > Serial error: Unable to flush buffer while sending command! > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Warning: Couldn't connect to 128.39.187.138:4001 > Error: Too many failed attempts to connect to datalogger... giving up! > > Do anyone have an idea whether I am doing something wrong, or whether the problem is the function "static ssize_t logger_command" in logger.c (the one giving the error message), which has the note : > /* Send a command to the datalogger > > XXX This whole function really needs to be rewritten. One way to start is to > remove the get prompt function, and have this function get a prompt before > it returns, then set a value in logger saying the datalogger is ready for the > next command. */ > > > Any suggestions are welcome! > > Best regards from Trond Rafoss > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > Crget-discuss mailing list > Crg...@li... > https://lists.sourceforge.net/lists/listinfo/crget-discuss > |
|
From: Trond R. <tro...@PL...> - 2003-08-19 10:17:53
|
Dear crget users.
First of all - thank you Anthony for making this contribution to the =
Open Source World.
Here at the Norwegian Crop Reserach Institute we are running a =
agrometeorological network of approx. 80 Campbell weather stations. We =
are currently switching from modem to IP-based communication. I was very =
happy when I detected crget at sourceforge, and immediately gave it a =
try (on my RedHat 9 laptop).
After compiling the source I issued the command:
./crget -Cip 4001 128.39.187.138
The result was:
--11:47:34-- Getting data via TCP/IP connection to 128.39.187.138:4001
=3D> 'logger_data-128.39.187.138-20030819'
Serial error: Unable to flush buffer while sending command!
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Error: Too many failed attempts to connect to datalogger... giving up!
I also tried at connection using the security code (not necessary for =
just reading data):
./crget -C -c 1432 -p 4001 128.39.187.138
The result was:
--12:07:15-- Getting data via TCP/IP connection to 128.39.187.138:4001
=3D> 'logger_data-128.39.187.138-20030819'
Serial error: Unable to flush buffer while sending command!
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Warning: Couldn't connect to 128.39.187.138:4001
Error: Too many failed attempts to connect to datalogger... giving up!
Do anyone have an idea whether I am doing something wrong, or whether =
the problem is the function "static ssize_t logger_command" in logger.c =
(the one giving the error message), which has the note :
/* Send a command to the datalogger
=
=
=20
XXX This whole function really needs to be rewritten. One way to =
start is to
remove the get prompt function, and have this function get a prompt =
before
it returns, then set a value in logger saying the datalogger is ready =
for the
next command. */
Any suggestions are welcome!
Best regards from Trond Rafoss
|
