Re: [time-nuts] python or matlab/octave for Keysight instruments?

[Keenan Tims]

PyVISA depends on the NI binary VISA libraries, which you then need to
get to work with your instruments. Getting this all working is an
endeavour I quickly gave up on.

I've had good luck with python-ivi:
https://github.com/python-ivi/python-ivi which should work well with
modern instruments that support USBTMC or VXI11 (SCPI-over-IP), and I
wrote an adapter for the Keithley 2000 serial interface that was also
pretty easy. It can also use PyVISA as a backend if you've got some
'real' GPIB gear you need to deal with. The only real gotcha is that
if your instrument is not supported 'natively' you will need to write
the object-oriented driver code yourself. This is not particularly
difficult, and most of the standard device classes need very little
modification, but it might be a turn off if you just want to throw a
few commands at the devices.

This same python-ivi project also contains lower-level VXI11 and
USBTMC drivers you can use if you prefer.

On 2 July 2016 at 09:09, jimlux  wrote:
> I'm looking for a *simple* *portable* software library to do some
> control/data acquisition from either python or octave for Agilent/Keysight
> gear, specifically over the USB or Ethernet interfaces.
>
> the "Keysight IO Libraries Suite CD " is, I think, Windows only
>
> I'm fine with writing the SCPI commands and parsing the output, I'm just
> looking for the "glue" between "send_message_to_instrument" or
> "read_message_from_instrument" and the instrument itself.
>
>
> Sort of like the python interfaces to the Prologix Ethernet/GPIB
> controllers.
>
> I've got the whole numpy/scipy infrastructure already installed, if that's
> relevant.
>
> Is PyVISA reasonably easy to work with, or is it one of those "once you've
> spent 6 weeks recompiling the kernel and finding all the libraries from 4
> different sources, it works great"..
>
> There's also the Agilent Command Expert which seems to provide a matlab and
> python interface, but, looks like "windows only" and I'm in a cross platform
> environment (OS X, Ubuntu, Windows) (Hmm, KCE isn't as nice an acronym as
> ACE)
>
>
>
>
> ___
> 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] Ublox Neo-6M time error.

[Keenan Tims]

FYI, u-center works fine in Wine. It also works (and installs)
perfectly in a Windows VM without any network access. So I don't know
what problem you're having, but I don't think it's caused by ublox.

On 1 June 2016 at 14:02, Mark Sims  wrote:
> I have no idea... I can't run Ucenter.  It requires an internet connection to 
> run (or at least register).  All my current Windoze boxes are XP,  and 
> there's no way in hell I'm connecting an XP box to the internet.  Other GPS 
> makers don't have such a requirement to use their software,  so I avoid using 
> Ublox products.
>
> I'm pretty sure the issue is the "when does the time message come out in 
> relation to the 1PPS" question.  It seems Ublox is the odd man out compared 
> to the 11 other receivers from 6 different makers that I have tested.
>
> Oh, and whoever thought sending out sawtooth corrections after the 1PPS was a 
> good idea needs to treated to a severe atomic wedgie...
>
> ---
>> What does u-center report for the NEO-6M?
> ___
> 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] Last Call Group Buy Ublox LEA-6T

[Keenan Tims]

I had some of these boards made:
http://openbsc.osmocom.org/trac/wiki/osmo-lea6t-gps from the Gerbers
in the git repo. I'm running the cheaper LEA-6S modules for
prototyping but the boards seem to work well and were designed for the
pin compatible LEA-6T you're after.

On 25 May 2016 at 23:30, Keenan Tims <kt...@gotroot.ca> wrote:
> I had some of these boards made:
> http://openbsc.osmocom.org/trac/wiki/osmo-lea6t-gps from the Gerbers
> in the git repo. I'm running the cheaper LEA-6S modules for
> prototyping but the boards seem to work well and were designed for the
> pin compatible LEA-6T you're after.
>
> On 20 May 2016 at 01:27, Angus <not.ag...@btinternet.com> wrote:
>>
>> On Wed, 18 May 2016 05:31:45 +, you wrote:
>>
>> >There is what looks like a decent carrier board for Ublox modules on 
>> >OSHPARK.COM's shared project library.  It has a voltage regulator and 
>> >RS-232 interface on it... would be nicer if it had a prototype area and 
>> >swoopty PPS driver,  but I'm too lazy to lay out a better one.  Three 
>> >boards will cost you $30.
>> >https://oshpark.com/shared_projects/8QR7ymk8
>>
>> Just in case anyone thinking of it has not noticed - that one is for
>> the smaller NEO version rather than the LEA version.
>>
>> So if anyone knows of a LEA version, or has one that they want to
>> upload or whatever... ideally with sawtooth correction  :)
>>
>> Angus.
>>
>>
>> ___
>> 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] GPSDO Alternatives

[Keenan Tims]

As a lurker, I just want to chime in and say that I for one would love
to see an open-source GPSDO implementation. There are quite a few open
hardware designs out there, but as Bob suggests, all the interesting
bits are tied up in the closed-source software they run. And most of
them are no longer maintained, meaning it's getting hard to find parts.

I've thought on designing a hardware platform to support a GPSDO as
well, but don't have the time-nut or control theory skills (or
equipment) necessary to make the software any good. My hope at the time
was that a build it and they will come approach would solve those
problems, but I haven't had time to make that gamble.

As far as uP choice, Arduino's only saving grace is the pool of existing
'developers' in the amateur community for it - but that's perhaps a big
deal here. It's expensive, doesn't include debug hardware, and is slow
with not many peripherals. I'd second the STM32 ARM Cortex platform, or
suggest MSP430 if you want to stay cheap and slow.

Keenan
VE7XEN

On 2012-12-06 1:28 AM, Chris Albertson wrote:
 On Wed, Dec 5, 2012 at 2:50 PM, saidj...@aol.com wrote:

 If there is one thing I learned, it is that one is never finished improving
  the software. That is why we are time-nuts I guess.

 This is the reason I suggested using the Arduino.  It is so easy to program
 that MANY people will be able to contribute.  That is my goal, a GPSDO that
 can be a living project that is not dependent on one or a few experts.
 I'd like to see a budget of well under $100, again so that more people can
 contribute and experiment.

 A design that can evolve will have just about any performance people want.
  So don't worry about if it is 1E-12 or 1E-15.  Just make it transparent
 and easy to understand and modify.



___
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] Fwd: Re: Contact: Jupiter GPS questions

[Keenan Tims]

There is an MSP430 port of GCC that works fine, and mspdebug is able to
write the code to the chip via the programming hardware that comes on
the Launchpad boards. TI also provides several free IDEs with code size
limits, if you prefer that route. Definitely not as easy for a beginner
as an Arduino - the chips are more complicated and the documentation a
bit more arcane - but there's still a good community around them and
decent tools available for free. There's also the ST 'DISCOVERY' series.
Much more powerful chips, on a board, with a USB programmer still around
the $10 mark, but coding for ARM is again another step up the difficulty
ladder.

Plenty of options that will work to send a few bytes of serial at power
on, but for a complete beginner I'd say just spend the extra money and
get an Arduino or chipKit because they're super easy to get going on.
Such a project should be a couple hours of work, even for a beginner.
Just figuring out how to set up the compiler and linker properly and
init the chip can be a week's work for a newbie on ARM...

The other option, of course, is to modify whatever you're using for APRS
to send the string. I don't think you mentioned which tracker / software
you intend to use, but it maybe be possible.

Keenan VE7XEN

On 2012-10-19 6:45 AM, shali...@gmail.com wrote:
 Hi TJ,

 The Jupiter receivers I have are the standard part, and like you I have found 
 detailed design info hard to come by.

 All I can suggest for your issue is to use a small microcontroller to send 
 the commands to the receiver at power up, then go to sleep until the next 
 power cycle.

 I have been using Silabs' Toolsticks for hacks of that nature. There is an 
 example of such hack with my GPS monitor project.

 You do not need to buy any software (the Silabs IDE is free, and you can use 
 either the free and limited Keil demo C compiler, or the free and unlimited 
 SDCC C compiler.)

 I have C code for talking to a Maxim DS1629 RTC, and you could use my GPS 
 monitor project as a starting point.
 Even though the GPS monitor only listens to the Thunderbolt, there is 
 software support for sending messages as well in the source code.

 The F330 Toolstick is about $10 and the programmer is about $20. Alternately, 
 TI has cheaper kits for their MPS430, but the C compilers are not free, and 
 writing in assembly is not my idea of fun.

 I am sure those familiar with the PICs will suggest their favorite solution 
 as well.

 Didier

 PS: I take the liberty of sending this to the time-nuts list, as there may be 
 other people interested to chime in.

 Sent from my Droid Razr 4G LTE wireless tracker using MailDroid.



 -Original Message-
 From: TJ Fiel zulut...@yahoo.com
 To: didier_ju...@yahoo.com
 Sent: Thu, 18 Oct 2012 3:41 PM
 Subject: Contact: Jupiter GPS questions

 Name: TJ Fiel

 Email: zulut...@yahoo.com

 Subject: Jupiter GPS questions

 Message: Hello KO4BB,

 Many thanks for making so many resources available through your
 website.  I'd never seen Labmon 7 before and it cured several
 problems with previous versions.

 I'm attempting to use a Jupiter serial GPS receiver with APRS.  This
 is an OEM version made for Etak/Sony about 1999, p.n. TU40-D310-011. 
 It uses the Rockwell Scorpio DSP (11577-11) but implements few
 features.  I've never found a datasheet or even a pinout for this
 chip.  Conexant stopped producing this chip about ten years ago and
 now they don't appear to answer their phones.  Apparently they never
 released chip level data to the public for this DSP, only for
 built-up GPS modules.

 My biggest issues are automatically forcing NMEA out at startup and
 possibly adding an RTC.  Any insights you can give will be greatly
 appreciated.

 Best wishes and thanks,
 TJ Fiel

 IP: 71.34.158.74
 HOST: 71-34-158-74.clsp.qwest.net

 ___
 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.