Time pulse pin Reach RTK (original Reach) and hardware resources

[tobias-dahms]

Does the original Reach break out the time pulse or PPS, (Reach M+ has PPS at least) future at any pin?

And BTW how much resources are left on the intel chip to perfom other operations? Or is there more room for such things at the M+ or the upcoming M+2?

[tobias-dahms]

Could someone please clarify whether this has been implemented in the mean time or how I can implement that myself? Or has someone e.g. @vclor implemented it and would share the solution?

I would also be interested whether there is a delay introduced by mirroring.

PPS output on the Reach

Hi, I’m looking for a way to get PPS output from the reach. Is there a way to send it on one of the output pins? Thank you in advance for helping.

[bide]

@tobias-dahms

Does the original Reach break out the time pulse

Sorry, no PPS (time pulse) output on the original Reach module:

Specification | RTK Modules

@tobias-dahms

And BTW how much resources are left on the intel chip to perfom other operations?

It has been a while since I looked at the processes on the Edison, but I believe there were plenty of resources available for other tasks.

I am not sure if the PPS is wired to the Edison such that it could be routed to a spare GPIO. Hopefully someone else knows the answer to that.

[tobias-dahms]

Thank you, I think I mixed up Time pulse and PPS. PPS is basically a time pulse per second, with a rising edge at very full second (23:59:59.000), right?

I think I can work with PPS, my goal is to sync inputs from different sensors with the gnss data.
Could that program mentioned below be written in Python and would that program be fast enough to introduce no delay?

Is their a developer guide some where?

Some information I have collected from the forum which gives hints but leaves a lot of questions and I would be interested to have more/clarified information about it.

@igor.vereninov

Those are different pins, timepulse and timemark. Tie pulse is routed to Edison GPIO128, you can setup an interrupt that will move one of GPIOs on the DF13 headers accordingly.

Is that PPS or configurable time pulse?

@egor.fedorov

It means you can write program to read Edison’s GPIO128 state and mirror it on one of the pins in the DF13 connector.

I.e. it could be mirrored on GPIO46 or GPIO77?

@zlo

I’m trying to get PPS events but there is no interrupts at GPIO128 pin. At the same time I see interrupts at GPIO13 with 1000ms interval. Maybe GPIO13 is routed to uBlox timepulse?

Is that PPS or configurable time pulse?

@zlo

I’m sorry, my fault. GPIO128 MRAA number is 13, so these interrupts are pps.

@egor.fedorov

There certainly is some confusion due to different GPIO numbering systems. Good luck.

Where is the confusion (M8T pins, or Edison pins and naming in hardware and software?) and where can I read about that?

GPIO46, GPIO77, PWM, SCL, SDA, TX, RX are connected to Intel Edison via buffers and are 3.3 V logic level, 5 V tolerant.

SCL and SDA belong to I2C1 on Intel Edison, I2C1 also could be used to communicate with internal magnetometer in MPU9250.

This could be used to output the MPU9250 data or record other sensor data with the Edison?

PWM belongs to PWM3 GPIO183 on Intel Edison