Hi, i have no experience with pic mcus, but after quick look at the PIC18F2680 firmware and datasheets, there are impression that "precise" part of timestamp are incorrect, as the same timer used for latching CAN message receive time and software interval counter. If i understand it correctly CPR1H and CCPR1H latch state of TMR1H and TMR1L at receiving CAN message, but TMR1 are used for software count 1ms interval in TimeStampLongISR, and content of TMR1H and TMR1L are modified by software every isr - it looks wrong.
Hi, i have no experience with pic mcus, but after quick look at the PIC18F2680 firmware and datasheets, there are impression that "precise" part of timestamp are incorrect, as the same timer used for latching CAN message receive time and software interval counter. If i understand it correctly CPR1H and CCPR1H latch state of TMR1H and TMR1L at receiving CAN message, but TMR1 are used for software count 1ms interval in TimeStampLongISR, and content of TMR1H and TMR1L are modified by software every isr - it looks wrong.