-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPS PPS pin #2
Comments
Yes, The PSS pin is now connected to the LED and a pin header. it is not connected to the HAT now. |
Thanks, would it be possible to have this either directly connected to one of the gpio pins or with a jumper to enable this is used for the GPS Rx/Tx? It seems that a number of tutorials about using Raspberry Pi with GPS to feed NTP where the PPS pin has been connected to GPIO pin 18 (physical pin 12) so could it be worthwhile using that pin for maximum compatibility? |
Hi, Romeo,
Thanks for this info. we will also add this feature. Can you point me the link so we can have a test on it?
Best Regards,
Edwin
发件人: Romeo-Golf [mailto:[email protected]]
发送时间: 2017年1月5日 8:28
收件人: dragino/Lora
抄送: edwin; Comment
主题: Re: [dragino/Lora] GPS PPS pin (#2)
Thanks, would it be possible to have this either directly connected to one of the gpio pins or with a jumper to enable this is used for the GPS Rx/Tx?
It seems that a number of tutorials about using Raspberry Pi with GPS to feed NTP where the PPS pin has been connected to GPIO pin 18 (physical pin 12) so could it be worthwhile using that pin for maximum compatibility?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#2 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnz1n8zwW87LNkFvgTt7_OUuiIKTNVTks5rPDj5gaJpZM4LUhkM> .说明: 图像已被发件人删除。
|
In order to use timing information from GPS to NTP it is required to take the PPS into a GPIO pin on the Pi, am I reading the schematics correctly that this PPS pin is only wired to the external pin on the HAT?
The text was updated successfully, but these errors were encountered: