rigserve-devel Mailing List for Rigserve (Page 2)
Status: Alpha
Brought to you by:
aa6e
You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(5) |
Jun
|
Jul
(11) |
Aug
(17) |
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
(3) |
Feb
|
Mar
(8) |
Apr
(3) |
May
(3) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2009 |
Jan
(9) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
From: A. M. B. <aa...@am...> - 2007-09-29 16:26:20
|
Nice to hear Martin's talk at DCC today. In the past I wrote my own stuff to control the RX-320, adopted pcrlib and packaged it for Debian to control my PCR-1000 (even though I use pcrsat most often for that),and more recently wrote stuff to control an Icom ID-1. If you connect an ID-1 to your Linux box via its USB port, the first thing you might notice is that Linux recognizes the ID-1 USB as a serial device and loads the right driver for you. That would be because I have already figured out what was needed and sent a patch along to the kernel USB maintainers. http://d-star.mit.edu/index.php?title=USB_interface_notes I started writing a control application in Python. It actually uses the model of translating human readable command lines and CI-V sentances back and forth. It should fit nicely in the rigserve environment. I'd like to do two things with GUIs - a curses interface like pcrsat because that is so elegant. - a wx gui like GnuRadio since that runs everywhere. I've checked out rigserve's SVN, the curious can visit http://amrad.org/svn and see what I've been up to, and ponder what might be worth merging. 73 de aa4hs, -Maitland |
From: Martin A. <aa...@ew...> - 2007-09-06 05:37:14
|
Subject: SF.net SVN: rigserve: [33] trunk From: aa...@us... Date: Wed, 05 Sep 2007 22:33:32 -0700 To: rig...@li... Revision: 33 http://rigserve.svn.sourceforge.net/rigserve/?rev=33&view=rev Author: aa6e Date: 2007-09-05 22:33:31 -0700 (Wed, 05 Sep 2007) Log Message: ----------- minor changes Modified Paths: -------------- trunk/ic_codes.py trunk/rigclient.py |
From: Martin A. <aa...@ew...> - 2007-09-04 04:44:11
|
Rigserve people, There have been a lot of SVN updates coming out, so be sure you are up to date before working with the Subversion files. When the R75 support stabilizes, I expect to make another release. Experimentally, I have just set up an automatic notification to this list for each new SVN file commit. Let me know if it gets to be too much. (We should be so lucky...) 73 Martin AA6E |
From: Martin A. <aa...@ew...> - 2007-09-02 21:29:34
|
Jim, Typo fixed. Thanks. The S-AM modes for R75 were wrong and have been corrected, I hope. Hex 11 is not the same as hex B. Hi. I'm not sure about the frequency setting problem. It definitely works for the R8500. It looks like some trouble in the command interpreter. Do you have problems with other "puts"? 73 Martin AA6E James Watson wrote: > Hi Martin, > > Sorry it's taken me so long to get round to looking at the software. > > I noticed a slight typo in the readme, "...which is 127.0.0.1. If > "telnet localhost 14562" does not work, you can try "telnet 127.0.0.1 > 14562"..." has the wrong port number. > > I'm having problems setting the frequency; > > Typing the following command; > > get rig1.VFOA.freq > 9420000 > put rig1.VFOA.freq 9425000 > > results in the following error message; > > Traceback (most recent call last): > File "./rigserve.py", line 295, in <module> > reply = str(command(rData)) > File "./rigserve.py", line 250, in command > result = func(args) > File "./rigserve.py", line 157, in do_put > resp = eval (cmd) # execute the command, response passed > up > File "<string>", line 1, in <module> > File "/home/jwatson/rigserve/trunk/icom.py", line 153, in freq > if not in_band(self.bands[v],f): > KeyError: 'VFOA' > > The read freq commands work ok. > > I'm also having problems with the rx_mode command; > > get rig1..rx_mode > ? Unrecognized rx hex mode: 0x112 > > (The receiver was in S-AM mode at the time) > > I'll have a look and see if I can figure out what's happening but may > not be able to do much until the weekend. > > Best regards > > > - jim > > On Tue, 2007-08-28 at 21:05 -0400, Martin AA6E wrote: >> A slew of updates mainly related to Icom support. Added IC-R75 support >> (Thanks, Jim!) with a framework to support many more Icom rigs in the >> future. >> >> 73 Martin AA6E >> |
From: James W. <lei...@gm...> - 2007-09-02 17:53:44
|
Hi Martin, Sorry it's taken me so long to get round to looking at the software. I noticed a slight typo in the readme, "...which is 127.0.0.1. If "telnet localhost 14562" does not work, you can try "telnet 127.0.0.1 14562"..." has the wrong port number. I'm having problems setting the frequency; Typing the following command; get rig1.VFOA.freq 9420000 put rig1.VFOA.freq 9425000 results in the following error message; Traceback (most recent call last): File "./rigserve.py", line 295, in <module> reply = str(command(rData)) File "./rigserve.py", line 250, in command result = func(args) File "./rigserve.py", line 157, in do_put resp = eval (cmd) # execute the command, response passed up File "<string>", line 1, in <module> File "/home/jwatson/rigserve/trunk/icom.py", line 153, in freq if not in_band(self.bands[v],f): KeyError: 'VFOA' The read freq commands work ok. I'm also having problems with the rx_mode command; get rig1..rx_mode ? Unrecognized rx hex mode: 0x112 (The receiver was in S-AM mode at the time) I'll have a look and see if I can figure out what's happening but may not be able to do much until the weekend. Best regards - jim On Tue, 2007-08-28 at 21:05 -0400, Martin AA6E wrote: > A slew of updates mainly related to Icom support. Added IC-R75 support > (Thanks, Jim!) with a framework to support many more Icom rigs in the > future. > > 73 Martin AA6E > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Rigserve-devel mailing list > Rig...@li... > https://lists.sourceforge.net/lists/listinfo/rigserve-devel |
From: Martin A. <aa...@ew...> - 2007-08-29 01:05:28
|
A slew of updates mainly related to Icom support. Added IC-R75 support (Thanks, Jim!) with a framework to support many more Icom rigs in the future. 73 Martin AA6E |
From: Martin A. <aa...@ew...> - 2007-08-28 19:50:50
|
Jim, I will be dumping new stuff into SVN pretty soon (within hours?). I hope you will test and tweak the R75 part of the new code. The idea is that ic_r75 and ic_r8500 are subclasses of Icom, but Icom has most of the horsepower. Will let you know when it's ready. Cheers, Martin James Watson wrote: > Hi Martin, > > I'm not sure if you received my earlier reply but yes I'd like to have a > go with the latest version of the Icom rig drivers. I've learned a > little more about python and am really impressed with it. I've used it > to create a couple of scripts to produce plots from voacap output files. > You can take a look at my website; > > http://homepage.mac.com/jimwatson/voacapl/ > > The project to get voacap running on Linux seems to be taking off. Ive > heard back from a few people now who've managed to get it running on > their machines. > > Please send me any code as it becomes available. > > Best regards > > - jim > > On Tue, 2007-08-21 at 08:46 -0400, Martin AA6E wrote: >> Jim, >> >> I am working on a general Icom class that will be based on the big >> tables from DF4OR. I can provide an advance peek if you or anyone else >> is interested. Still very preliminary. >> >> If only someone would loan me a '7800 and/or an 'R9000 for six months or so! >> >> 73 Martin AA6E >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Rigserve-devel mailing list >> Rig...@li... >> https://lists.sourceforge.net/lists/listinfo/rigserve-devel > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Rigserve-devel mailing list > Rig...@li... > https://lists.sourceforge.net/lists/listinfo/rigserve-devel |
From: James W. <lei...@gm...> - 2007-08-28 18:29:46
|
Hi Martin, I'm not sure if you received my earlier reply but yes I'd like to have a go with the latest version of the Icom rig drivers. I've learned a little more about python and am really impressed with it. I've used it to create a couple of scripts to produce plots from voacap output files. You can take a look at my website; http://homepage.mac.com/jimwatson/voacapl/ The project to get voacap running on Linux seems to be taking off. Ive heard back from a few people now who've managed to get it running on their machines. Please send me any code as it becomes available. Best regards - jim On Tue, 2007-08-21 at 08:46 -0400, Martin AA6E wrote: > Jim, > > I am working on a general Icom class that will be based on the big > tables from DF4OR. I can provide an advance peek if you or anyone else > is interested. Still very preliminary. > > If only someone would loan me a '7800 and/or an 'R9000 for six months or so! > > 73 Martin AA6E > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Rigserve-devel mailing list > Rig...@li... > https://lists.sourceforge.net/lists/listinfo/rigserve-devel |
From: James W. <lei...@gm...> - 2007-08-21 14:33:17
|
Hi Martin, Thanks for the offer - yes please I'd be interested to try out the Icom class. Are you going to post it as a beta on the website. - jim On Tue, 2007-08-21 at 08:46 -0400, Martin AA6E wrote: > Jim, > > I am working on a general Icom class that will be based on the big > tables from DF4OR. I can provide an advance peek if you or anyone else > is interested. Still very preliminary. > > If only someone would loan me a '7800 and/or an 'R9000 for six months or so! > > 73 Martin AA6E > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Rigserve-devel mailing list > Rig...@li... > https://lists.sourceforge.net/lists/listinfo/rigserve-devel |
From: Martin A. <aa...@ew...> - 2007-08-21 12:46:44
|
Jim, I am working on a general Icom class that will be based on the big tables from DF4OR. I can provide an advance peek if you or anyone else is interested. Still very preliminary. If only someone would loan me a '7800 and/or an 'R9000 for six months or so! 73 Martin AA6E |
From: Martin A. <aa...@ew...> - 2007-08-21 12:41:11
|
The spammers are onto this list. I have changed the policy to make it harder for non-members to get through. Hope this helps. 73 Martin AA6E |
From: Andrej M. <And...@hn...> - 2007-08-20 19:00:29
|
http://finance.yahoo.com/q?s=3DEXMT.PK |
From: Damyan K. <Da...@ha...> - 2007-08-20 00:58:39
|
H*E,R,E WE GO AG*AIN! T_H E B'I_G O'N+E BEF.ORE T-H*E S-EPT,EMBER.RALLY! T.H,E MARKE+T IS A+BOUT TO P-O.P_, A,N*D SO IS E X'M.T,! Tic k: E*X M.T 5 -day pot-enti'al: 0*.+4 0 Fir'm: EXC HANG-E MOB.ILE T+E_L+E (Oth.er O,T*C.: EXMT.+PK) A*s.k_: 0*._1*0 (+25.0'0*%) UP TO 2-5,% in 1 day N o-t o+n.l+y d+o,e.s t*h*i-s f,i.r+m h,a v+e gre.at f'undam+entals, b,u't get_ting t+h.i_s oppo,r'tunity at t.h*e r+ight t.i+m.e,, ri,ght befor'e t'h-e rall'y is w+h.a*t make*s t'h.i-s d e'a.l so swee*t! = T-h*i-s a gre at oppo'rtu*nity to at leas t dou_ble up! No.thing g.o o,d c.a-n c+o*m-e of it. Mr Bloo_m c+a+m_e las-t, foldi+ng h_i's pap+er ag ain i,n+t,o h i.s = poc'ket. T.h_i.s in t'u,r'n p*'resupposes an exac t bala'nce of act-ive a_n'd = pass*ive e'l*ements. I w*a_n*t to t r.y i't,, b u't I f*e,a*r . The.re.fore NO s.tring c'om+parison a,lgo'rithm (incl+u_ding t-h_e = doma'in-ma_tch algo,rit.hm) c+a_n be relie'd on to dist_inguis.h a = domai-n t+h_a t belon gs to a p*a_rticular ser'vic-e, f-r-o*m a do,main = t+h-a-t bel.ongs to anoth'er pa-rty. |
From: Moris P. <POL...@us...> - 2007-08-19 21:23:08
|
H E*R+E WE GO AGAI,N! T H'E B_I'G O'N-E BEF_ORE T H'E SEPTEMBE,R.RALL_Y! T_H'E MA,RKET IS A*BOUT TO P.O,P., A-N.D SO IS E-X+M_T,! Ti,ck: E X.M,T 5-da'y po-tentia*l: 0_.+4.0 F'irm: EXC'HAN,GE MO BILE T,E-L_E (,Other O T.C+: EXM+T.PK) A s,k': 0*._1_0 (+2-5.00%') UP TO 2+5 % in 1 day N o't o_n-l'y d-o_e-s t h-i s f+i r.m h-a'v*e grea+t fu-nda mentals, b'u.t get+ting t'h.i-s op-portuni.ty at t+h-e righ-t t+i+m+e., r,ight befo_re t+h'e ral,ly is w-h*a-t m,akes t*h,i+s d'e_a l so swee t! = T'h.i,s a g+reat op,portun+ity to at lea,st dou,ble up! A n,d som *etimes, w*h'e+n h.i_s o'w'n w*i_l*d s'peeche.s h+a d fil.led = h i.m w*i t+h a bu*rning el+at_ion, h-e_r fath+er wo'uld emb.race h+e*r = a*n*d sob+erly promi_se h e_r t h*e wor-ld. By defa,ul,t, t.h'i+s w'i l_l be t*h.e d efault l.ocale f*o+r t'h+e = serve,r. Ra-ndom frow.ned at h*e*r f athe-r's wat-ch, wh*ich didn+'t do a'n.y of = t_h.i+s'. To be f air, t+h.e U. By defi n ing t,h.e po rts in t*h-e "Na. meVirtualHost" t a-g*, y*o,u = c,a,n allo-w t*h i.s to w-o*r+k.. |
From: gerstmayer L. <ger...@bu...> - 2007-08-19 10:05:32
|
H,E*R'E WE GO A,GAIN! T+H.E B+I.G O_N'E BEFOR E T+H+E SEPTEMB ER.'RALLY! T H.E M ARKET IS ABOU_T TO P O-P_, A_N_D SO IS E+X*M+T_! T.ick: E_X'M+T 5 -day pot-enti_al: 0'.'4*0 Fir'm: EXCH.ANG_E MOB,ILE T_E_L E (-Other O,T'C+: EXMT.P+K) A's-k,: 0+.,1.0 (+25..,00%) UP TO 2.5_% in 1 day N'o+t o+n-l*y d_o'e,s t'h.i.s f+i-r,m h a*v.e grea*t fu*ndamental+s, b+u*t g_etting t_h i,s oppo.r-tunity at t*h_e righ_t t i'm'e_, ri+ght befo're t+h e r*ally is w-h'a+t m+akes t-h'i+s d e'a.l so s.weet! = T-h+i's a grea,t oppor tun'ity to at lea,st doubl,e up! T_h.e bla*ck m a*s*s wheel,ed twi_ce a.n+d h*eaded s_outh. Ad princip*e*m i-nerudi+tum, 7 8.0*b+. Resour+ce.s Resou_rce's a'r+e inde'xed by a mult.-iple lev el = binary-s-ort ed t,r*e e str.uct.ure. Y o,u mus+t, b+ecause i't_'_s t'h-e o n l.y r.e_a'l cha'nce Hil-lh+ome = h'a_s_. T'h,e Sco*ts m,i s*s h-e'r+. |
From: Baba C. <Bab...@ma...> - 2007-08-18 17:59:08
|
T'H_E B+I.G O*N,E BEF ORE T'H_E SEPT.EMBER.RAL-LY! H*E_R-E WE GO AGA*IN! T-H'E MARK ET IS AB,OUT TO P+O.P+, A N*D SO IS E*X_M.T_! Tic.k: E'X*M*T F irm: E*XC-HANGE MOBI,LE T'E_L_E (O+ther O T+C+: EXMT .PK) 5-da,y potential,-: 0*.'4.0 A,s,k+: 0..'1_0 (+ 25.00.%) (*U*P TO 2.5'% in 1 d.a y,) N_o't o+n_l.y d-o_e*s t_h,i s f,i-r+m h+a*v.e grea+t fundam,entals*, b.u't gett-ing t*h+i*s opportu.nit y at t.h+e r'ight tim,e, rig ht b-efore t_h-e ra.lly is w+h-a,t m+akes t.h*i-s d,e a l so sweet,! T.h*i*s a gr'eat oppo*rtuni_ty to at le,ast doubl e up! Thi+nk n*o,t of glory.. Additio.n*ally, on x 8*6 sy-stems a_l_l pr,oce'ssors m_u_s,t e_ither h,a,v e flo.ati.ng poi*nt cap*ab'ilities, or n*o*n-e should+. Co_nt+ains p,i*n informatio n f,o'r registe++ring a filt_er. T-h_e soone.r y_o_u m_o.v e agains+t y-o*u,r enemy_, t_h*e soo,ner y+o-u*r s*leep is untrou_bl,ed. Griev e n.o,t t*h+a-t I am fa*ll'n to t-h.i_s f-o.r y_o_u-, F-o r her,ein Fortun*e sho,ws herse*lf m*o'r_e k-i*n+d T'h_a,n is h+e r cust*om. |
From: pia B. <Bog...@sp...> - 2007-08-17 19:58:35
|
H.E_R-E WE GO A,GAIN! T+H E B'I,G O N,E BEF.ORE T_H_E SEPTEMBER.RAL'L+Y! T-H,E MARKE-T IS ABO,UT TO P,O-P-, A N-D SO IS E'X-M*T,! Fir m: EXC,HA*NGE MOBIL*E T,E'L-E (Oth.er O*T,C_: E.XMT.PK) T-ick: E+X*M+T A_s,k': 0*.-0'8 5--day pote*ntia l: 0...4 0 T.h i.s a g+reat o_pport-unity to at leas t doubl_e up! N'o,t o*n l+y d o e*s t,h.i+s f+i'r m h,a v_e gre,at fundame.ntal*s, = b.u_t gettin'g t.h_i*s oppo r,tunity at t.h,e r-ight t ime, righ,t = be_fore t,h.e rall,y is w_h,a*t m_akes t+h*i*s d*e,a.l so swe,et! Watc h it s+o+a+r_! T,h.i*s is an intern.'al membe.r funct-i*on t.h.a-t g e*t,s c'alled = w.h_e_n t.h.e so*urce rec t_angle chang es. He glan-ced at Perr+in'*s e,y-e,s - Pe*rrin k n_e.w h*o w t_h+e y = m'u+s_t sh+ine, burnis.h-ed g o*l+d in t'h'e m,oo,nlight - b'u't he = d_i*d n'o*t me.ntion t_h e m.. H'o w to i nt-ercept t_h+e D N,S_. A*n,d w'h'y doe*sn't M*F'C u*s*e m,o+r e c_o,p,y constr,u_ctors. He s_a-i'd n*o+t to wo-rry abo_ut h,i.m-, he wou*ld g-e-t a-long a+l l = righ*t. |
From: ioannis M. <io...@bo...> - 2007-08-09 18:21:00
|
L.I.V.E F.R.O.M T.H.E S.T.R.E.E.T! Sym: (P_R_T_H) Pr: .11 (UP 25%) A nnounces the Opening of Two New Stores by (PIN_KSHE_ETS: P-R-T-H) is pleased to announce that P uerto R ico 7, Inc. has opened two new stores. The stores are recorded as Pinero II and Borinquen Towers. Both locations were researched demographically to deliver above average sales due to high traffic streets and communities directly surrounding the stores. The Management team believes that the stores will each quickly reach an annualized run rate of 1.2 Million dollars of sales. |
From: Ashiq K. <Kar...@am...> - 2007-08-07 04:18:28
|
22a2F5f1 |
From: James W. <lei...@gm...> - 2007-07-31 19:07:41
|
Hi Martin, Thanks for the link to the paper which I found very interesting - it really states the case for open source software well. The rigserve project has got me interested in python as a language and I've been bowled over with the flexibility and power of a 'scripting' language. I've written a small utility that plots out voacap area maps, the output of which may be seen at; http://homepage.mac.com/jimwatson/voacapl/ - jim |
From: Martin A. <aa...@ew...> - 2007-07-31 14:09:44
|
The DCC contribution I mentioned is now available through my blog at http://blog.aa6e.net/2007/07/sourceforge-hamlib-and-rigserve-dcc07.html Anyone else going to DCC? I recommend it! 73 Martin AA6E |
From: Martin A. <aa...@ew...> - 2007-07-31 01:58:07
|
I just sent off an article to the Digital Communications Conference Proceedings that talks about Hamlib, Rigserve, and open source development. The DCC meeting for 2007 is in Hartford CT next month. I'd be happy to send a copy to anyone on the lists who requests it. I would have circulated it for comment, but the deadline came up too soon. For the live presentation, I should have a chance to revise things, so I'd be happy for any corrections or suggestions. 73 Martin AA6E |
From: James W. <lei...@gm...> - 2007-07-24 17:11:11
|
Hi Martin, Thanks for getting back to me. I've come across the documentation on CI-V before and agree that all of the Icom rigs appear to be outwardly the same yet are tantalisingly different when it comes down to the details. I've noticed that the mode/filter commands are slightly different for example. The setting that I've used in the R75 class are based on the front panel display, and don't align with the documentation in the manual and took a couple of hours messing around to get it sorted - I've just checked to link you provided and it acknowledges the mistake in the manual (Homer Doh!). As far as establishing a capability goes, I feel that 'generic' libraries such as Hamlib, rigserve etc should adhere to a simplified common denominator command set that apply across the board to all rigs. I make use of the 'grig' application to control my radio but the front panel doesn't fully align with the capabilities of the receiver. I prefer to see a smaller number of fully operational features than a larger set of loose ends that may or may not apply to a specific receiver. I would find a library that had common commands for all rigs to be of most use - there's nothing stopping users from extending the core functionality to create rig specific GUIs and applications. I really see rig control only useful when working with other applications, not as an end in itself. e.g. I developed a couple of OSX apps (homepage.mac.com/jimwatson) that allow a user to search the ilg database and present search results in a table. Double clicking a table entry re-tuned the receiver. Digging deep into menus on a screen just doesn't appeal when I could simply lean over and twiddle 'real' buttons. The program fldigi is an excellent example of a program making use of a generic library. I'm still not up to speed with Python but was thinking that a single 'CIV' class could be used to define a generic set of methods. Instantiate the class with a separate rig specific class that essentially contains a set of definitions, similar to the way that the serial class is generic but fully defined when it's instantiated with a class defining port locations, speeds etc. I'm not sure that my programming skills will allow me to illustrate what I'm talking about here but am prepared to give it a go at the weekend. All the best for now Jim On Mon, 2007-07-23 at 21:47 -0400, Martin AA6E wrote: > Jim, > > I have been looking at the problem of multiple Icom rigs & classes a > little bit. There is useful CI-V command documentation at > http://www.plicht.de/ekki/civ/index.html - if that helps. The > conclusion is (in part) that Icom CI-V capable rigs are all quite > similar, but they are all different. How to express all that > information in a natural and compact way is an interesting question. It > would be nice to have a CIV base class with subclasses for each distinct > model. > > On the other hand, in the short run it's way easier to do what you've > done and just copy the hardware interface subroutines and adapt to the > one particular model you're interested in. > > There is also the problem we have talked about in Hamlib for some time. > Are we trying to invent a system that expresses the full capability of > each type of rig, or are we looking to implement some lowest common > denominator? For example, I'm inclined to ignore the scanning and > memory capabilities that vary a lot from rig to rig - at least until > someone comes along who really wants to implement it. > > Hopefully, I'll have more to say after a while. > > 73 Martin AA6E > > James Watson wrote: > > Hi Martin, > > > > Sorry for the delay in getting back to you but I've been stupidly busy > > at work. > > > > I've attached the files that so far seem to work on my R75. I've tested > > most routines fairly thoroughly. I've also added a simple routine ant to > > select the antenna input (my first Python script). > > > > I'm not sure of the best way to organise the code to reduce re-coding > > for similar receivers but was wondering about a CIV class that > > initialised with rig specific class that consisted essentially of > > definitions, i.e. dictionaries of valid modes (the modes/filter > > bandwidths are called up with the same syntax but not all modes appear > > to be supported on all receivers). > > > > Anyway, I hope the attached is of interest. If there's anything I can > > do to help, please let me know. > > > > > > > > > > o readOn Sun, 2007-07-15 at 16:00 -0400, Martin AA6E wrote: > >> Jim - > >> > >> I would only point out that the Python 'serial' package already provides > >> the basic serial class. Is there something that it lacks for our work? > >> > >> Maybe there is room for a CI-V class that is effectively based on 'serial'. > >> > >> -Martin > >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Rigserve-devel mailing list > Rig...@li... > https://lists.sourceforge.net/lists/listinfo/rigserve-devel |
From: Martin A. <aa...@ew...> - 2007-07-24 01:48:00
|
Jim, I have been looking at the problem of multiple Icom rigs & classes a little bit. There is useful CI-V command documentation at http://www.plicht.de/ekki/civ/index.html - if that helps. The conclusion is (in part) that Icom CI-V capable rigs are all quite similar, but they are all different. How to express all that information in a natural and compact way is an interesting question. It would be nice to have a CIV base class with subclasses for each distinct model. On the other hand, in the short run it's way easier to do what you've done and just copy the hardware interface subroutines and adapt to the one particular model you're interested in. There is also the problem we have talked about in Hamlib for some time. Are we trying to invent a system that expresses the full capability of each type of rig, or are we looking to implement some lowest common denominator? For example, I'm inclined to ignore the scanning and memory capabilities that vary a lot from rig to rig - at least until someone comes along who really wants to implement it. Hopefully, I'll have more to say after a while. 73 Martin AA6E James Watson wrote: > Hi Martin, > > Sorry for the delay in getting back to you but I've been stupidly busy > at work. > > I've attached the files that so far seem to work on my R75. I've tested > most routines fairly thoroughly. I've also added a simple routine ant to > select the antenna input (my first Python script). > > I'm not sure of the best way to organise the code to reduce re-coding > for similar receivers but was wondering about a CIV class that > initialised with rig specific class that consisted essentially of > definitions, i.e. dictionaries of valid modes (the modes/filter > bandwidths are called up with the same syntax but not all modes appear > to be supported on all receivers). > > Anyway, I hope the attached is of interest. If there's anything I can > do to help, please let me know. > > > > > o readOn Sun, 2007-07-15 at 16:00 -0400, Martin AA6E wrote: >> Jim - >> >> I would only point out that the Python 'serial' package already provides >> the basic serial class. Is there something that it lacks for our work? >> >> Maybe there is room for a CI-V class that is effectively based on 'serial'. >> >> -Martin >> |
From: Martin A. <aa...@ew...> - 2007-07-21 21:23:52
|
Jim - Thanks for the contributions. I will be looking at them carefully, but I'm not sure when I will be able to get to them. Stand by... 73, Martin AA6E James Watson wrote: > Hi Martin, > > Sorry for the delay in getting back to you but I've been stupidly busy > at work. > > I've attached the files that so far seem to work on my R75. I've tested > most routines fairly thoroughly. I've also added a simple routine ant to > select the antenna input (my first Python script). > > I'm not sure of the best way to organise the code to reduce re-coding > for similar receivers but was wondering about a CIV class that > initialised with rig specific class that consisted essentially of > definitions, i.e. dictionaries of valid modes (the modes/filter > bandwidths are called up with the same syntax but not all modes appear > to be supported on all receivers). > > Anyway, I hope the attached is of interest. If there's anything I can > do to help, please let me know. > > > > > o readOn Sun, 2007-07-15 at 16:00 -0400, Martin AA6E wrote: >> Jim - >> >> I would only point out that the Python 'serial' package already provides >> the basic serial class. Is there something that it lacks for our work? >> >> Maybe there is room for a CI-V class that is effectively based on 'serial'. >> >> -Martin >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Rigserve-devel mailing list >> Rig...@li... >> https://lists.sourceforge.net/lists/listinfo/rigserve-devel >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Rigserve-devel mailing list >> Rig...@li... >> https://lists.sourceforge.net/lists/listinfo/rigserve-devel |