[time-nuts] GPScon running on Raspberry Pi 3b
No, it's not a bug. It's the way it is intended to work. Whenever Heather sees a command to open/change the serial port, the currently open port (if any) is closed and the new one is opened. Heather lets you change the serial port or read a config file on the fly from the keyboard. Trying to filter when to ignore or delay opening the port is a needless and potentially error prone complication. The simple / robust / reliable thing to do is just try and open it whenever / wherever a serial port command is seen. Most people with just set up the config file for their default port and never use the command line option or do things like changing the port or loading a config file from the keyboard, but it can be quite handy if you are playing with lots of devices. - > So the bug reported below seems to be a bug. ___ 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] GPScon running on Raspberry Pi 3b
andrew.mile...@gmail.com said: > Beware that USB-to-Serial converters are pretty horrible for precise timing > applications, like PPS on the CD pin. It can be done on a GPIO pin instead, > but requires some hacking and re-compiling. What sort of hacking or re-compiling do you have in mind? I didn't have any troubles getting PPS via GPIO. It's a bit of editing on run-time config files. From my notes: in /boot/config.txt add new line: dtoverlay=pps-gpio,gpiopin=4 (The pin number depends on the GPS HAT.) In /etc/modules add new line: pps-gpio -- These are my opinions. I hate spam. ___ 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] GPScon running on Raspberry Pi 3b
On Mon, Jun 26, 2017 at 2:04 PM, Andrew E Mileskiwrote: > > The RaspberryPi 3 is a bit different. > > All the Pi models, 1 & 2 & 3, have two UARTs: a full-featured UART, and a > mini-UART. > > On the PI 3, the header pins for the serial port are routed by default to > the mini-UART, and the full-featured UART is used for Bluetooth. On the > older Pi models, the full-featured UART is routed to the header, > > It is possible to swap them back via software, but then you lose Bluetooth > functionality. > > The mini-UART has issues with its baud-rate generator: it is derived from > the system clock, not an independent clock generator like the full-featured > UART, so it doesn't work when dynamic system clocking for power management > is enabled, so you either have to run at max or minimum speed only. > > FWIW, I'm running a custom Fedora 25 on all my Pi3, as the default doesn't > support all Pi3 devices (and I don't want the U-Boot boot-loader either). > I'm using cheap $0.99 USD CH340 based USB-to-Serial converters from E-Bay > (I bought 10), as well as my bench equipment which are mostly FTDI (hacked > some to use standard VendorId and DeviceId) or PL. > > Beware that USB-to-Serial converters are pretty horrible for precise > timing applications, like PPS on the CD pin. It can be done on a GPIO pin > instead, but requires some hacking and re-compiling. > I should have cited my sources: most details can be found on the RPi Foundation's web site at: https://www.raspberrypi.org/documentation/configuration/uart.md Google: raspberry pi mini-uart ___ 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] GPScon running on Raspberry Pi 3b
On Sun, Jun 25, 2017 at 3:04 PM, Mark Simswrote: > Heather's configuration priority is to process: hard coded defaults, > then the config file, and finally the command line options. This lets you > set your preferred settings in the config file and then override your > config file options from the command line. > If that is the desired behavior and I think it is reasonable and what most people would expect, then the correct implementation of that behavior is to NOT ACT on any config setting until the command line options are read. Or in general never act on an instruction that might be overridden So the bug reported below seems to be a bug. > > > > > When I ran it with ./heather -4u, it first told me that it was unable to > open /dev/ttyUSB0 and > then told me it was unable to open /dev/ttyUSB3. This is probably due to > the > configuration file containing "-1u", but if that option is given on the > command line then the configuration file value should be ignored - or at > the > least it should be tried after the command line option. > ___ > 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. > -- Chris Albertson Redondo Beach, California ___ 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] GPScon running on Raspberry Pi 3b
On Fri, Jun 23, 2017 at 12:16 AM, Hal Murraywrote: > > hol...@hotmail.com said: > > The PI does have a couple of logic level serial ports on the expansion > > connector you can connect a level shifter two. One port is normally the > > Linux serial console which you can configure to be a general purpose > serial > > port (I've never used them, but others have). > > The console port used by the GPS HATs. Works fine. /dev/ttyAMA0 > > The PPS pin varies depending on which type of HAT you get. > The RaspberryPi 3 is a bit different. All the Pi models, 1 & 2 & 3, have two UARTs: a full-featured UART, and a mini-UART. On the PI 3, the header pins for the serial port are routed by default to the mini-UART, and the full-featured UART is used for Bluetooth. On the older Pi models, the full-featured UART is routed to the header, It is possible to swap them back via software, but then you lose Bluetooth functionality. The mini-UART has issues with its baud-rate generator: it is derived from the system clock, not an independent clock generator like the full-featured UART, so it doesn't work when dynamic system clocking for power management is enabled, so you either have to run at max or minimum speed only. FWIW, I'm running a custom Fedora 25 on all my Pi3, as the default doesn't support all Pi3 devices (and I don't want the U-Boot boot-loader either). I'm using cheap $0.99 USD CH340 based USB-to-Serial converters from E-Bay (I bought 10), as well as my bench equipment which are mostly FTDI (hacked some to use standard VendorId and DeviceId) or PL. Beware that USB-to-Serial converters are pretty horrible for precise timing applications, like PPS on the CD pin. It can be done on a GPIO pin instead, but requires some hacking and re-compiling. ___ 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] GPScon running on Raspberry Pi 3b
Mark, That is exactly the right processing order. However, it shouldn't actually try the USB port until after that processing is done. In other words, if the configuration file has -1u and the command line has -4u, it should never try USB0 because that was overridden on the command line. It should try USB3 and succeed or fail based on that. Did you get what you needed from the build this morning? Michael Lee Finney > Heather's configuration priority is to process: hard coded defaults, then > the config file, and finally the command line options. This lets you set > your preferred settings in the config file and then override your config file > options from the command line. > >> When I ran it with ./heather -4u, it first told me that it was unable to >> open /dev/ttyUSB0 and > then told me it was unable to open /dev/ttyUSB3. This is probably due to the > configuration file containing "-1u", but if that option is given on the > command line then the configuration file value should be ignored - or at the > least it should be tried after the command line option. > ___ > 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. -- Best regards, Timenutmailto:time...@metachaos.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] GPScon running on Raspberry Pi 3b
Heather's configuration priority is to process: hard coded defaults, then the config file, and finally the command line options. This lets you set your preferred settings in the config file and then override your config file options from the command line. > When I ran it with ./heather -4u, it first told me that it was unable to open > /dev/ttyUSB0 and then told me it was unable to open /dev/ttyUSB3. This is probably due to the configuration file containing "-1u", but if that option is given on the command line then the configuration file value should be ignored - or at the least it should be tried after the command line option. ___ 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] GPScon running on Raspberry Pi 3b
On Fri, Jun 23, 2017 at 1:36 AM, Mark Simswrote: > > I also have some CH3xx dongles that have some clone chips in them. Many > Linux drivers don't seem to be able to set the baud rate on those. > > I looked into this when I was struggling with a CH3xx interface recently. It appears to be OK if you have a 4.0 or higher kernel. Unfortunately this doesn't include what was until recently the current Debian distribution, jessie. However, the version released a few days ago (stretch) should be OK. ___ 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] GPScon running on Raspberry Pi 3b
Mark, I compiled and ran Lady Heather on my Tinker this morning. This is using the "stretch" distribution with GCC version 6.3.0 (and of course, the current version is 7.1.0 with more language changes). I received 8 warning messages, the first three are a language change and remainder are "misleading indentation" messages. To get a clean compile, I fixed the spaces and indentation, but looking at the code it is the type of thing that I would check to make sure that the control flow is correct - the indentation is indeed misleading which is always a potential sign of a bug. Here are the warning messages that I got: heather.cpp:13720:10: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix] heather.cpp:13720:27: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix] heather.cpp:13720:40: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix] heather.cpp:10881:26: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] heather.cpp:10883:4: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] heathmsc.cpp:2124:28: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] heathmsc.cpp:6710:24: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] heathgps.cpp:20433:7: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] Also, I am waiting for my USB to RS232 adapter, so I don't have anything plugged into the USB ports (other than keyboard and mouse). When I ran it with ./heather -4u, it first told me that it was unable to open /dev/ttyUSB0 and then told me it was unable to open /dev/ttyUSB3. This is probably due to the configuration file containing "-1u", but if that option is given on the command line then the configuration file value should be ignored - or at the least it should be tried after the command line option. Other than the above, it looks great given that nothing is plugged in! Thanks for the work you do maintaining this program. Michael ___ 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] GPScon running on Raspberry Pi 3b
I've got a Pi3 here on my desk. I only see one UART that connects to GPIO pins. But it turns out if you actually need to use serial you use the USB to serial dongles. If you need four serial ports use four dongles. That is just the way the Pi3 is. You can level the 3.3 volt serial port but then you are into a MAX chip and some passives or maybe just a couple transistors but the =USB-Serial dingle is easier then level shifting. If you want a Pi-like device that is better for real-time embedded use look at the Beagle Bone Black. But it was limited CPU and RAM compared to Pi3 but better IO. If you are building a NTP server, look at the Pi Zero version 1.3. $5 each. On Thu, Jun 22, 2017 at 7:51 PM, Orin Emanwrote: > On Thu, Jun 22, 2017 at 5:36 PM, Mark Sims wrote: > > > > > The PI does have a couple of logic level serial ports on the expansion > > connector you can connect a level shifter two. One port is normally the > > Linux serial console which you can configure to be a general purpose -- Chris Albertson Redondo Beach, California ___ 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] GPScon running on Raspberry Pi 3b
hol...@hotmail.com said: > The PI does have a couple of logic level serial ports on the expansion > connector you can connect a level shifter two. One port is normally the > Linux serial console which you can configure to be a general purpose serial > port (I've never used them, but others have). The console port used by the GPS HATs. Works fine. /dev/ttyAMA0 The PPS pin varies depending on which type of HAT you get. -- These are my opinions. I hate spam. ___ 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] GPScon running on Raspberry Pi 3b
On Thu, Jun 22, 2017 at 5:36 PM, Mark Simswrote: > > The PI does have a couple of logic level serial ports on the expansion > connector you can connect a level shifter two. One port is normally the > Linux serial console which you can configure to be a general purpose serial > port (I've never used them, but others have). > Oh, that's fun on the Pi, especially the Pi3. Here are my notes on the Pi3 from a different project. If you're really lucky, they didn't change it again. QUOTE: Well, they just couldn't make it backward compatible out of the box... By default, ttyAMA0 is used for Bluetooth so there are more hoops to jump through to wrest it away from the OS's grasp. ttyS0 is now wired to the IO pins which we could use if it worked correctly, but apparently its baud rate depends on the cpu core frequency which is _variable_*. Fortunately there is a way of routing ttyAMA0 to the IO pins As before, all references to ttyAMA0 need removing from /boot/cmdline.txt. To disable bluetooth: systemctl disable hciuart Add "dtoverlay=pi3-disable-bt" to /boot/config.txt Finally, perhaps unnecessary, use raspi-config to disable login on the serial port. (Serial under Advanced Options.) * https://frillip.com/raspberry-pi-3-uart-baud-rate-workaround/ https://www.raspberrypi.org/forums/viewtopic.php?f=107=138223 ___ 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] GPScon running on Raspberry Pi 3b
Heather only requires TXD, RXD, and GND. If you want to use the temperature control feature RTS and DTR. Most Linux distros have decent USB serial port drivers built in. I tend to use no-name Chinese PL-2303 based USB dongles... because I have them. They have worked fine on all the Linuxy stuff I have used and the Windows drivers they shipped with work. I no longer use FTDI based devices since there are LOTS of clone chips out there and FTDI is rather aggressive about having their (Windows) drivers not work with them. Since there is no way to tell what chip is actually being used in a dongle, I just avoid the FTDI stuff and any potential hassles. There are also fake Prolific chips out there and Prolific has also been known to block their Windows drivers from working with them. If you can find genuine FTDI / Prolific chip based dongles, they are great... but buyer beware these days. I also have some CH3xx dongles that have some clone chips in them. Many Linux drivers don't seem to be able to set the baud rate on those. Something recently changed on one of my Win XP boxes (perhaps installing the TL-833 prom burner software) and some of my PL-2303 dongles have started acting up. After a day or two of continuous operation they start randomly dropping received bytes. No issues running the same dongles on PI / Linux / macOS or previously on that XP system. The garbaged received data did help my find a bug in Heather... they could produce numbers like 1.2345E300. Heather was expecting a number like 9.8765 and tried to format and print the value. The resulting 300 character string overflowed a buffer and crashed the program. Now my number reader routines do a sanity check and reject obviously bogus values, NANs, INFs, etc. The PI does have a couple of logic level serial ports on the expansion connector you can connect a level shifter two. One port is normally the Linux serial console which you can configure to be a general purpose serial port (I've never used them, but others have). --- > Are there any special requirements for using a USB to RS-232 adapter on the Pi? Any specific features for the RS-232 adapter to get all of the features for Lady Heather? ___ 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] GPScon running on Raspberry Pi 3b
Mark, Are there any special requirements for using a USB to RS-232 adapter on the Pi? Any specific features for the RS-232 adapter to get all of the features for Lady Heather? Looking at eBay, it is not clear which adapter would be best. Some don't say anything about supported pins, other list the pins that are supported (and may differ). Which pins do you require / support? Are any device drivers needed for the Pi or Linux for those adapters? New to Linux, Pi and Lady Heather. Thanks. Michael > Lady Heather can run under Linux, macOS, FreeBSD, and Windoze. It runs > well on the PI (2 or 3) and the soon to be released version 6 has support > for the touchscreen and several new devices. I can send anybody interested > in testing the new version the latest source code to build. Contact me off > list. > New devices include the RFTG-m, Truepostion GPSDO, Zyfer Nanosync 380, > Brandywine GPS4, Jackson Labs LTE-lite, Oscilloquartz Star-4, NEC GPSDO, > Trimble TAIP receivers, most SCPI GPSDOs (Z38xx, HP-5), HP-5071A, TAPR > TICC, HP-531xx counters, generic time/frequency counters, etc > -- >> I believe that having a native GPS monitoring software on a Raspberry Pi >> instead of PC would become a game changer. > ___ > 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. -- Best regards, Timenutmailto:time...@metachaos.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] GPScon running on Raspberry Pi 3b
Lady Heather can run under Linux, macOS, FreeBSD, and Windoze. It runs well on the PI (2 or 3) and the soon to be released version 6 has support for the touchscreen and several new devices. I can send anybody interested in testing the new version the latest source code to build. Contact me off list. New devices include the RFTG-m, Truepostion GPSDO, Zyfer Nanosync 380, Brandywine GPS4, Jackson Labs LTE-lite, Oscilloquartz Star-4, NEC GPSDO, Trimble TAIP receivers, most SCPI GPSDOs (Z38xx, HP-5), HP-5071A, TAPR TICC, HP-531xx counters, generic time/frequency counters, etc -- > I believe that having a native GPS monitoring software on a Raspberry Pi > instead of PC would become a game changer. ___ 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] GPScon running on Raspberry Pi 3b
it looks to me like Olgierdhas a working INTEL linux os running on the Pi3. He installed Wine on the Intel Linux not on the ARM Linux It looks like maybe Michael has an ARM version of linux running native on the Pi3 Wine will not run on that If you need to run Wine, you need to fist have an INTEL lInux running. Remember "WINE= Wine Is Not an Emulaor" and it will not run Intel binaries on Arm. I'm skeptical it would be more then a stunt a triple stack of virtual environments. But if the final Windows app is not really doing anything with the CPU, maybe fast enough. ___ 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] GPScon running on Raspberry Pi 3b
Hi Michel, I installed Wine (Windows compatibility layer) within the ExaGear. After the installation of the ExaGear on a Raspberry Pi one gets a new icon on the desktop that just starts a session of Debian-8. Trying command "$ arch" returns "i686" beauty! What I did (within this Debian session) was: $ sudo apt-get update $ sudo apt-get upgrade (- this returned couple of warnings/errors mainly in the area of certificates updating - nothing critical I suppose) And just $ sudo apt-get install wine ...did the trick. Try then: $ wine --version $ wine start For the first time, Wine dowloaded itself some extra .Net emulation as well as Internet Explorer (Gecko) module. One needs also to create a sybolic link in ~/.wine/dosdevices to enable the serial port for Windows (assuming e.g. the FTDI driver recognised it on the Raspbian level): $ ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1 Note ExaGear offers three day trial for free. Let me add a quote from an Eltechs email: "The best way to get the trial is to install it directly from Raspberry Pi repository. For that, you have to open the command line and input two simple commands: sudo apt-get update sudo apt-get install exagear-desktop After the installation you need to run 'exagear' command and fill in the pop-up form to get trial license key." I believe that having a native GPS monitoring software on a Raspberry Pi instead of PC would become a game changer. My GPScon has been working flawlessly for few days now. Good luck! Olgierd Dnia 20.06.2017 o godz. 14:34 time...@metachaos.net napisał(a): > Neat! > > I just happen to be playing with a Pi this week as a class assignment > (retirement is wonderful - finally going back to college). > > I downloaded Lady Heather, compiled it, and got it to come up and run. Nothing > that I can plug in this week though, but it looks good. I also installed QEMU > in user mode which is similar to ExaGear, but slower and free (long run I will > probably get an ASUS Tinker as my lab computer, and it is a different > ExaGear). > > However, I could not find the steps to download wine. I understand that some > sort of patch is required, but all that I could find was complete linux images > that were already patched. What were your steps to download and install wine? > > Michael > >> Hi, >> This is my first post to the community I learned so much from. Just wanted >> to share -- I managed to succesfully install today the GPScon windows >> application on a micro computer Raspberry Pi 3 model B. CPU utilisation is >> 2% - a perfect overall result. >> I used an FTDI RS232 USB dongle to connect Z3805A/58503B to the Pi. First I >> installed on the Pi a Russian commercial I686 emulation software called >> ExaGear Desktop by Eltechs.com ($30). It provides a Debian-8 Intel >> environment on the Arm CPU. Next move was to (sudo apt-get) install wine >> Windows XP emulator and symlink therein com1 as /dev/ttyUSB0 - to enable the >> usb dongle to be seen by Wine as com1. >> Then I installed my copy of GPScon from 2013, which turned out to work >> pretty well. >> Hope this post was usefull. In case of interest I would exact steps to make >> this working. > >> Best regards >> Olgierd >> ___ >> 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. > > > > -- > Best regards, > Timenutmailto:time...@metachaos.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.
Re: [time-nuts] GPScon running on Raspberry Pi 3b
Neat! I just happen to be playing with a Pi this week as a class assignment (retirement is wonderful - finally going back to college). I downloaded Lady Heather, compiled it, and got it to come up and run. Nothing that I can plug in this week though, but it looks good. I also installed QEMU in user mode which is similar to ExaGear, but slower and free (long run I will probably get an ASUS Tinker as my lab computer, and it is a different ExaGear). However, I could not find the steps to download wine. I understand that some sort of patch is required, but all that I could find was complete linux images that were already patched. What were your steps to download and install wine? Michael > Hi, > This is my first post to the community I learned so much from. Just wanted > to share -- I managed to succesfully install today the GPScon windows > application on a micro computer Raspberry Pi 3 model B. CPU utilisation is 2% > - a perfect overall result. > I used an FTDI RS232 USB dongle to connect Z3805A/58503B to the Pi. First I > installed on the Pi a Russian commercial I686 emulation software called > ExaGear Desktop by Eltechs.com ($30). It provides a Debian-8 Intel > environment on the Arm CPU. Next move was to (sudo apt-get) install wine > Windows XP emulator and symlink therein com1 as /dev/ttyUSB0 - to enable the > usb dongle to be seen by Wine as com1. > Then I installed my copy of GPScon from 2013, which turned out to work pretty > well. > Hope this post was usefull. In case of interest I would exact steps to make > this working. > Best regards > Olgierd > ___ > 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. -- Best regards, Timenutmailto:time...@metachaos.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] GPScon running on Raspberry Pi 3b
Hi, This is my first post to the community I learned so much from. Just wanted to share -- I managed to succesfully install today the GPScon windows application on a micro computer Raspberry Pi 3 model B. CPU utilisation is 2% - a perfect overall result. I used an FTDI RS232 USB dongle to connect Z3805A/58503B to the Pi. First I installed on the Pi a Russian commercial I686 emulation software called ExaGear Desktop by Eltechs.com ($30). It provides a Debian-8 Intel environment on the Arm CPU. Next move was to (sudo apt-get) install wine Windows XP emulator and symlink therein com1 as /dev/ttyUSB0 - to enable the usb dongle to be seen by Wine as com1. Then I installed my copy of GPScon from 2013, which turned out to work pretty well. Hope this post was usefull. In case of interest I would exact steps to make this working. Best regards Olgierd ___ 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.