AH-HAAAAAAAAAAAAAAAAAAHHHHHHHHHHHH
Sorry, went a bit Alan Partridge there
Looking at the dspic30F4013 data sheet
Input Pins
Datasheet wrote:
7.3 Input Change Notification Module
The input change notification module provides the
dsPIC30F devices the ability to generate interrupt
requests to the processor, in response to a Change-Of-
State (COS) on selected input pins. This module is
capable of detecting input Change-Of-States, even in
Sleep mode, when the clocks are disabled. There are
up to 10 external signals (CN0 through CN9, CN17 and
CN18) that may be selected (enabled) for generating
an interrupt request on a Change-Of-State.
On CAN
Datasheet wrote:
17.3.2 DISABLE MODE
In Disable mode, the module does not transmit or
receive. The module has the ability to set the WAKIF bit
due to bus activity, however, any pending interrupts
remain and the error counters retain their value.
If the REQOP<2:0> bits (CiCTRL<10:8>) = 001, the
module enters the Module Disable mode. If the module is
active, the module waits for 11 recessive bits on the CAN
bus, detects that condition as an Idle bus, and then
accepts the module disable command. When the
OPMODE<2:0> bits (CiCTRL<7:5>) = 001, that
indicates whether the module successfully went into
Module Disable mode. The I/O pins revert to normal I/O
function when the module is in the Module Disable mode
If I read that right the can bus reverts to a simple input pin
Datasheet wrote:
20.7.1 SLEEP MODE
In Sleep mode, the clock to the CPU and peripherals is
shut down. If an on-chip oscillator is being used, it is
shut down.
The Fail-Safe Clock Monitor is not functional during
Sleep since there is no clock to monitor. However, the
LPRC clock remains active if WDT is operational during
Sleep.
The brown-out protection circuit and the Low-Voltage
Detect (LVD) circuit, if enabled, remains functional
during Sleep.
The processor wakes up from Sleep if at least one of
the following conditions has occurred:
• any interrupt that is individually enabled and
meets the required priority level
From that I infer that an input change can wake the device from low power clocks off sleep. It would also appear the CAN interface can do the same
I think that means that you configure selected inputs to wake the module (via the PC configuration program) - door switches etc - and a module can then wake the rest of the system up via the CAN bus. Job jobbed