Re: [time-nuts] Lady Heather's Fat Client
-Original Message- From: time-nuts-boun...@febo.com [mailto:time-nuts-boun...@febo.com]on Behalf Of Steve Rooke Sent: Wednesday, December 30, 2009 8:28 PM To: Discussion of precise time and frequency measurement Subject: Re: [time-nuts] Lady Heather's Fat Client Hi John, Sorry for the late posing to this thread but just to let you know that this works very well under OpenSuSE 11.2 Linux running under wine and installs without any problems. It would be great to see a Linux port of this software and I wonder what would be involved with this as there is obviously no windowing code so it would, hopefully, be mostly I/O. Congratulations on an excellent application and thanks for your time spent on producing such a useful application. You're welcome, thanks for the feedback! What I told Bob earlier would apply to Linux as well; sockets are sockets for the most part. Very little beyond the serial-port code would need to change. -- john, KE5FX ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Subject: [OT] short run cable assembly vendor?
Mary, the owner of ebay store QualityChinaGoods, had some RF pigtails for sale, but with the wrong connector on one end for my use. She very helpfully made up a small batch to match my needs, and put up a special Buy-It-Now auction for me. Peter Vince (G8ZZR, London, England) ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
Hi John, 2009/12/31 John Miles jmi...@pop.net: You're welcome, thanks for the feedback! What I told Bob earlier would apply to Linux as well; sockets are sockets for the most part. Very little beyond the serial-port code would need to change. So what's it written in, may I ask. Yes, if all the most complex it gets in I/O is sockets, it should be easy to port (assuming something like C). It could be easily ifdef'd between the two(?) OS's and BSD should be a very similar port to Linux if it's just down to sockets. What time frame are you looking to port, assuming you are inclined that way? Is the source available for perusal? 73 Steve -- Steve Rooke - ZL3TUV G8KVD A man with one clock knows what time it is; A man with two clocks is never quite sure. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
Steve Rooke wrote: Hi John, 2009/12/31 John Miles jmi...@pop.net: You're welcome, thanks for the feedback! What I told Bob earlier would apply to Linux as well; sockets are sockets for the most part. Very little beyond the serial-port code would need to change. So what's it written in, may I ask. Yes, if all the most complex it gets in I/O is sockets, it should be easy to port (assuming something like C). It could be easily ifdef'd between the two(?) OS's and BSD should be a very similar port to Linux if it's just down to sockets. What time frame are you looking to port, assuming you are inclined that way? Is the source available for perusal? Sticking to POSIX serial I/O interface should make it work on BSD, Linux or whatever else UNIX style OS of sufficient recent vintage being used. Should be a suitable common denominator and cause less hassle to maintain than #ifdefs for each OS-style available on the planet (which was the old way of dealing with portability). Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
2010/1/1 Magnus Danielson mag...@rubidium.dyndns.org: Sticking to POSIX serial I/O interface should make it work on BSD, Linux or whatever else UNIX style OS of sufficient recent vintage being used. Should be a suitable common denominator and cause less hassle to maintain than #ifdefs for each OS-style available on the planet (which was the old way of dealing with portability). But what about a single code to cover nix and DOS/Windows? 73, Steve -- Steve Rooke - ZL3TUV G8KVD A man with one clock knows what time it is; A man with two clocks is never quite sure. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
Steve Rooke wrote: 2010/1/1 Magnus Danielson mag...@rubidium.dyndns.org: Sticking to POSIX serial I/O interface should make it work on BSD, Linux or whatever else UNIX style OS of sufficient recent vintage being used. Should be a suitable common denominator and cause less hassle to maintain than #ifdefs for each OS-style available on the planet (which was the old way of dealing with portability). But what about a single code to cover nix and DOS/Windows? It should be possible to the best of my knowledge... I haven't played with DOS or Windows programming for years. Except for some simple GPIB exercises, it must have been back in mid 90ies or something. Anyway, I assume POSIX sockets and serial I/O exists. The only real cleanup is the GUI interface, where wxWidget or GTK might be the options to consider. Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
2010/1/1 Magnus Danielson mag...@rubidium.dyndns.org: Steve Rooke wrote: But what about a single code to cover nix and DOS/Windows? It should be possible to the best of my knowledge... I haven't played with DOS or Windows programming for years. Except for some simple GPIB exercises, it must have been back in mid 90ies or something. Anyway, I assume POSIX sockets and serial I/O exists. The only real cleanup is the GUI interface, where wxWidget or GTK might be the options to consider. Well, for all the nix variants, standard POSIX sockets and tty code will be the same but I have no experience of DOS/Windows system calls and functions period. As for the user interface, the existing application looks just like a DOS console application so there is no windowing code to my mind. It should be able to do it in a similar way with curses but I'm not sure how the screen is written. I do know that there is a fair amount of processor load, including a lot of system calls. On my system, running LH under wine takes the equivalent of 1 CPU on my quad core. That's a fair amount of processor load but it would only be fair to see what that is likely to be once a native port is done and the application could be profiled then. Cheers, Steve Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. -- Steve Rooke - ZL3TUV G8KVD A man with one clock knows what time it is; A man with two clocks is never quite sure. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
Steve Rooke wrote: 2010/1/1 Magnus Danielson mag...@rubidium.dyndns.org: Steve Rooke wrote: But what about a single code to cover nix and DOS/Windows? It should be possible to the best of my knowledge... I haven't played with DOS or Windows programming for years. Except for some simple GPIB exercises, it must have been back in mid 90ies or something. Anyway, I assume POSIX sockets and serial I/O exists. The only real cleanup is the GUI interface, where wxWidget or GTK might be the options to consider. Well, for all the nix variants, standard POSIX sockets and tty code will be the same but I have no experience of DOS/Windows system calls and functions period. As for the user interface, the existing application looks just like a DOS console application so there is no windowing code to my mind. It should be able to do it in a similar way with curses but I'm not sure how the screen is written. I do know that there is a fair amount of processor load, including a lot of system calls. On my system, running LH under wine takes the equivalent of 1 CPU on my quad core. That's a fair amount of processor load but it would only be fair to see what that is likely to be once a native port is done and the application could be profiled then. Which only shows to tell that using Wine is just a poor mans option and not a long-term option. I migth consider a port. Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
Hi, 2010/1/1 Magnus Danielson mag...@rubidium.dyndns.org: Steve Rooke wrote: 2010/1/1 Magnus Danielson mag...@rubidium.dyndns.org: Steve Rooke wrote: But what about a single code to cover nix and DOS/Windows? It should be possible to the best of my knowledge... I haven't played with DOS or Windows programming for years. Except for some simple GPIB exercises, it must have been back in mid 90ies or something. Anyway, I assume POSIX sockets and serial I/O exists. The only real cleanup is the GUI interface, where wxWidget or GTK might be the options to consider. Well, for all the nix variants, standard POSIX sockets and tty code will be the same but I have no experience of DOS/Windows system calls and functions period. As for the user interface, the existing application looks just like a DOS console application so there is no windowing code to my mind. It should be able to do it in a similar way with curses but I'm not sure how the screen is written. I do know that there is a fair amount of processor load, including a lot of system calls. On my system, running LH under wine takes the equivalent of 1 CPU on my quad core. That's a fair amount of processor load but it would only be fair to see what that is likely to be once a native port is done and the application could be profiled then. Which only shows to tell that using Wine is just a poor mans option and not a long-term option. I migth consider a port. Agreed, that's why I'm bringing this up. Well, if your having a port I might join you or perhaps a decent amontillado would be nice as well. Cheers, Steve Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. -- Steve Rooke - ZL3TUV G8KVD A man with one clock knows what time it is; A man with two clocks is never quite sure. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] Happy New Year
Well, to all of you that were expecting great things in 2010, I can tell you that 2 hours and 44 minutes of it have gone past here and nothing interesting has happened yet. Happy New Year to all of you!! Well, it is time related and not off-topic then. 73, Steve -- Steve Rooke - ZL3TUV G8KVD A man with one clock knows what time it is; A man with two clocks is never quite sure. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
Hi there, Steve Rooke wrote: Hi, Which only shows to tell that using Wine is just a poor mans option and not a long-term option. I migth consider a port. Agreed, that's why I'm bringing this up. The server side and for that matter related lower level and core should not be too hard. Well, if your having a port I might join you or perhaps a decent amontillado would be nice as well. Hmm, I may have a bottle of Sauternes laying around... several infact. Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
Hi I took a look at the server code last night. It is indeed pretty straightforward. It also is commented / documented in a style that makes sense (THANKS). Since the server side is pretty much stand alone from the client, I think it makes sense to start there. The client is still in the middle of being worked on, so the server is unlikely to change in the middle of a port. That of course assumes the port is done before the temperature control code is ready to be folded in. The only issue I see with the server is that there isn't a lot of coding to be done, but there is a lot of compiling and testing on various platforms needed. I would suggest that one person do the POSIX code and the rest of us look at what happens. A reasonable set of platforms to try this on (at least for the server): 1) FreeBSD (to get it onto a Soekris box or something like it) 2) OS-X (lots of older Macs running around ) 3) Several flavors of Linux I'm set up to try things on 1, 2 and a couple flavors of 3. So who wants to do what? I'm a better candidate for testing than coding. If everybody wants to drop by the house later to do the ports, I've got enough for everybody to drink in stock. I've even got a bottle of Sauterne Magnus ... Bob On Dec 31, 2009, at 9:11 AM, Magnus Danielson wrote: Hi there, Steve Rooke wrote: Hi, Which only shows to tell that using Wine is just a poor mans option and not a long-term option. I migth consider a port. Agreed, that's why I'm bringing this up. The server side and for that matter related lower level and core should not be too hard. Well, if your having a port I might join you or perhaps a decent amontillado would be nice as well. Hmm, I may have a bottle of Sauternes laying around... several infact. Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Why they call it Flori-DUH...!!
Mike, Not to worry. Sometime the massive influx of nS sized bits of information can overload the cranial logic gates and cause a temporary short circuit or at least a high impedance between the ears. I have suffered from it on more than one occasion myself. Happy New Year, Had K7MLR At 05:34 PM 12/30/2009, you wrote: Hello, Time Nuts-- Now you know why they started calling this far southeast corner of the nation Flori-DUH...!! Somewhere along in the process of installing LH v3.00 beta I managed to get John Miles on-line T-Bolt unit mis-labeled. Mike Baker WA4HFR Micanopy, Flori-DUH, USA A fine is a tax for doing wrong. A tax is a fine for doing well. Peter Cooper, of Fermi Lab, says, Every experimentalist knows that the apparatus, or at least your understanding of it, is always at fault until demonstrated otherwise. He also says, Nature is really unmoved by what I, or anyone else, believes. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] WWVB Kinemetrics 60-DC EPROM failure
Happy New Year everyone, I am hopeful someone may be able to help me with my Kinemetrics 60-DC WWVB receiver. Recently, several of the caps in the power supply shorted and burned up its transformer, but not before frying one of the 5V regulators, placing about 15V on the logic boards (CPU and RS232 boards). I wasn't ready to part with the unit and decided to replace all IC's with new ones (and put them in sockets). The dilemma I now face is finding replacements for the two fried EPROMS (M2716's) that make this clock tick. The EPROMS read as follows: C60522R7 RS232 (LO) F1E1 5/22/84 C60522R7 RS232 (HI) A81E 5/22/84 I would be grateful for any suggestions as to how I could obtain or burn replacements, and it does not have to be Gratis. Please feel free to reach me directly at jos @ mindspring . com (minus the spaces) Many thanks, Jos / W4JOS ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] chip scale atomic clock
Dear all, After very mild amount of homework, I think a followup was due. Magnus Danielson wrote: Peter Vince wrote: 2009/12/26 Robert Lutwak lut...@alum.mit.edu: ... CSAC is intended for portable battery-powered operation. Surely your basement has the space and wallplug power to support an LPRO. (p.s. don't cool the damn thing, heat it). ... Hi Robert, Do I understand you are suggesting heating an LPRO, not cooling it? That seems to go against what I understood, that greater cooling leads to increased life. While not directed to me, these are my understandings: Besides the power applied to heat the Rb lamp, the physical package needs to be at the sweet-spot in temperature, so heating is performed. Looking in the LPRO manual, as found in say: http://www.ham-radio.com/sbms/LPRO-101.pdf and the LPRO repair-guide: http://www.radcomms.net/EFRATOM%20LPRO%20101%20Repair%20Guide.pdf The Rb lamp heats to 110 C and the physical package to 78 C. Notice also figure 1.3 displaying power dissapation as a funciton of baseplate temperature. The simplified model for power consumption in chapter 3.2.3 gives a good hint about what is going on. For 20 degrees the RF lamp consumes about 1,7 W where as for 70 degrees it consumed about 750 mW. Similarly, for 20 degrees the physical package heating consumes about 3,8 W where as for 70 degrees it constumed about 520 mW. Thus, allowing the increase of baseplate temperature from 20 degrees to 70 degrees reduces the Rubidium assembly heating from a total of 5,5 W to 1,3 W. Looking at figure 1.3 and the equation again, we see that about 280 mA derives from the other electronics and that a lower (18 V) supply has significant shift in power. Thus, by paying attention to supplied power and baseplate temperature and cooling (which becomes more important to maintain baseplate below 70 degrees) less power dissapation can be achieved. With that in hand, both passive and active ovenizing could be considered. 5-6 W is significantly lower than 12-13 W and should allow for simpler solutions. There is also hints about how to temperature compensate the LPRO by steering the C-field from a temperature sensor. A sensible ovenization should reduce the need of such approaches, even if possible. Boxing one up similar to that of Thunderbolts may be the way to go. Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] WWVB Kinemetrics 60-DC EPROM failure
Boy that is a challenge. I do not have a dc-60. I checked and I see kinemetrics is still in business. Though interesting it looks like symetricom purchased the truetime division. Perhaps a call to them might obtain a copy of that eprom. Good luck On Thu, Dec 31, 2009 at 12:07 PM, Jos j...@mindspring.com wrote: Happy New Year everyone, I am hopeful someone may be able to help me with my Kinemetrics 60-DC WWVB receiver. Recently, several of the caps in the power supply shorted and burned up its transformer, but not before frying one of the 5V regulators, placing about 15V on the logic boards (CPU and RS232 boards). I wasn't ready to part with the unit and decided to replace all IC's with new ones (and put them in sockets). The dilemma I now face is finding replacements for the two fried EPROMS (M2716's) that make this clock tick. The EPROMS read as follows: C60522R7 RS232 (LO) F1E1 5/22/84 C60522R7 RS232 (HI) A81E 5/22/84 I would be grateful for any suggestions as to how I could obtain or burn replacements, and it does not have to be Gratis. Please feel free to reach me directly at jos @ mindspring . com (minus the spaces) Many thanks, Jos / W4JOS ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] Lady Heather Overhead
An idle Windows machine allocates 50% of its resources to a task when it starts up. This shows up as 50% CPU utilization. A second Heather will show as around 100% total utilization (50 % each). These usage numbers are totally bogus. Heather VERY periodically returns it's time slot to the system with the flag that says, Hey, if you aren't doing anything else, I'd kinda like that time back.. So if you bring up four Heathers, each will then show 25% utilization, etc. I have seen a dozen Heathers running on a fairly slow machine (and quite a sight it is). Basically all the Heathers soak up all the free time on the system and share it amongst themselves. The program runs just fine on a 100 MHz WIN98 laptop. If you are actually using a full core, you have other problems... There is a recently added command line flag (/tw=msecs) that says to force Sleep(msecs) calls in place of Sleep(0) calls. It slows the system response time down, but might be useful for power saving on laptops, etc. Mark John from a nut post: do know that there is a fair amount of processor load, including a lot of system calls. On my system, running LH under wine takes the equivalent of 1 CPU on my quad core. I'm sure not new to you and I hardly know what I'm talking about BUT what I have noticed is: MY LadyHeather programs will take all the spare windows processor time available even on my fastest windows XT machine. And then again I have no trouble running at least four simultaneous LH programs (even different versions) all at the same time on a slow machine, so they don't need much, they'll just take whatever is available, but they seem to share well. _ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141665/direct/01/ ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Heating or Cooling an LPRO (was Re: chip scale atomic clock)
Dear Peter, Peter Vince wrote: ...5-6 W is significantly lower than 12-13 W and should allow for simpler solutions. Thanks Magnus. If saving 7 watts is important, then OK, but I am more concerned about the significantly lower MTBF quoted on page 4 of the manual (the ninth page in the PDF file): Amb. Temp: 20°C25°C30°C40°C50°C60°C MTBF (hrs) 381,000 351,000 320,000 253,000 189,000 134,000 Well, the junction temperature of the heaters will lower as they burn less temperature. But the LPRO design is such that the physical package is very tightly connected to the electronics board. Separation of them would allow better temperature of those while the physical package would see about the same temperature regardless. But anyway, the point of the excersize was to show just how much cooling needs could be reduced if an external oven is applied. Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Heating or Cooling an LPRO (was Re: chip scale atomic clock)
Hi If you separate the the electronics from the physics package then you will need to think pretty hard about magnetic shielding. It is clear though that if you are going to run an LPRO off of batteries, you want to let it warm up. The energy savings likely outweigh the loss of reliability. The reliability penalty is real. I have indeed cooked rubidiums. In each case it was not the heater circuits or the lamp that failed. Bob On Dec 31, 2009, at 3:26 PM, Magnus Danielson wrote: Dear Peter, Peter Vince wrote: ...5-6 W is significantly lower than 12-13 W and should allow for simpler solutions. Thanks Magnus. If saving 7 watts is important, then OK, but I am more concerned about the significantly lower MTBF quoted on page 4 of the manual (the ninth page in the PDF file): Amb. Temp: 20°C25°C30°C40°C50°C60°C MTBF (hrs) 381,000 351,000 320,000 253,000 189,000 134,000 Well, the junction temperature of the heaters will lower as they burn less temperature. But the LPRO design is such that the physical package is very tightly connected to the electronics board. Separation of them would allow better temperature of those while the physical package would see about the same temperature regardless. But anyway, the point of the excersize was to show just how much cooling needs could be reduced if an external oven is applied. Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
Hi John, 2009/12/31 John Miles jmi...@pop.net: You're welcome, thanks for the feedback! What I told Bob earlier would apply to Linux as well; sockets are sockets for the most part. Very little beyond the serial-port code would need to change. So what's it written in, may I ask. Yes, if all the most complex it gets in I/O is sockets, it should be easy to port (assuming something like C). It could be easily ifdef'd between the two(?) OS's and BSD should be a very similar port to Linux if it's just down to sockets. What time frame are you looking to port, assuming you are inclined that way? Is the source available for perusal? See previous reply to Bob... -- john, KE5FX ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Heating or Cooling an LPRO (was Re: chip scale atomic clock)
Bob Camp wrote: Hi If you separate the the electronics from the physics package then you will need to think pretty hard about magnetic shielding. The physical package is what needs to sit inside the my-metal. It is clear though that if you are going to run an LPRO off of batteries, you want to let it warm up. The energy savings likely outweigh the loss of reliability. The reliability penalty is real. I have indeed cooked rubidiums. In each case it was not the heater circuits or the lamp that failed. The important thing for the exercise is to stabilize temperature. To what temperature is a matter of choise. Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
An even better solution would be for the server to actually parse the TSIP message from the Tbolt that has the temperature reading and for the server to do the PID algorithm and temperature control PWM. The temp control code is not that long or complicated. This method gets net delays, etc out of the equation. It does add the complexity of how to configure the PID parameters on the server. That's my plan -- once you're done with that code I'll move it to a separate .obj file and parameterize it in a way that'll link to both the cilent and server. It would be possible to send side-channel instructions to the server to tell it how to control the DTR/RTS lines on behalf of a PID loop running on a client. However, the other big reason to run the whole PID loop on the server, besides lag and reliability issues associated with the network link, is that we would otherwise need a way to decide which of several possible clients has the authority to run the control loop. Right now all clients are equal in the server's eyes, and I'd like it to stay that way for simplicity's sake. It would be OK for multiple clients to request different temperatures if they want to, just as we currently let multiple clients issue whatever TSIP commands they want, but giving direct control over the DTR/RTS lines to multiple clients would be asking for trouble. -- john, KE5FX ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
[time-nuts] Lady Heather's Fat Client
One thing that I have recently added is some hooks for making the Tbolt read only. Set the flag and it does not allow any message to be sent to the Tbolt that changes any oscillator settings. If that code is ported over to the server parser, you could add a password protect feature to the server. People could look and change their view settings, etc but would not be able to change critical parameters. _ Hotmail: Powerful Free email with security by Microsoft. http://clk.atdmt.com/GBL/go/171222986/direct/01/ ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Lady Heather's Fat Client
One thing that I have recently added is some hooks for making the Tbolt read only. Set the flag and it does not allow any message to be sent to the Tbolt that changes any oscillator settings. If that code is ported over to the server parser, you could add a password protect feature to the server. People could look and change their view settings, etc but would not be able to change critical parameters. Yeah, I like that idea regardless of what's done with the control loops... -- john, KE5FX ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] Heating or Cooling an LPRO (was Re: chip scale atomic clock)
Hi As I recall there are good reasons for the temperatures that the physics package gets stabilized to. Something about the C-field and the temperature combining to improve the state selection. Of course we have made it to the eiswein, so that may be a bit off... Bob On Dec 31, 2009, at 4:37 PM, Magnus Danielson wrote: Bob Camp wrote: Hi If you separate the the electronics from the physics package then you will need to think pretty hard about magnetic shielding. The physical package is what needs to sit inside the my-metal. It is clear though that if you are going to run an LPRO off of batteries, you want to let it warm up. The energy savings likely outweigh the loss of reliability. The reliability penalty is real. I have indeed cooked rubidiums. In each case it was not the heater circuits or the lamp that failed. The important thing for the exercise is to stabilize temperature. To what temperature is a matter of choise. Cheers, Magnus ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
