by TickTock (Posted Sun, 07 Jul 2013 07:05:14 GMT)
I built another CANary yesterday and came across a strange issue with this batch of VP230's I thought I'd share in case anyone else encounters it. Very strange, but they are acting like VP231's. I double checked the package marking and even replaced one (but the replacement was from the same order). Anyway, the only difference between the 230's and the 231's is how sleep mode behaves. On the 230's it goes into a listen-only mode (TX disabled). On the 231's it goes into a full powerdown (TX & RX disabled). So what I am seeing is neither canbus receives any messages unless I set the sleep-mode to disabled with the jumper installed. Power supplies all look good. I've ordered some more parts but meanwhile am running with a software work-around. Isn't strictly required to keep them in sleep mode - I just did it this way as a double safety to prevent CANary from talking in case of a glitch in the program (commonly called "babbling idiot protection").
I'm guessing noone else has encountered this yet (or I would have heard about it). I've added a new define statement that can be set to vp231 mode (I will keep the default at vp230) as a work-around until my new parts come in.
I built another CANary yesterday and came across a strange issue with this batch of VP230's I thought I'd share in case anyone else encounters it. Very strange, but they are acting like VP231's. I double checked the package marking and even replaced one (but the replacement was from the same order). Anyway, the only difference between the 230's and the 231's is how sleep mode behaves. On the 230's it goes into a listen-only mode (TX disabled). On the 231's it goes into a full powerdown (TX & RX disabled). So what I am seeing is neither canbus receives any messages unless I set the sleep-mode to disabled with the jumper installed. Power supplies all look good. I've ordered some more parts but meanwhile am running with a software work-around. Isn't strictly required to keep them in sleep mode - I just did it this way as a double safety to prevent CANary from talking in case of a glitch in the program (commonly called "babbling idiot protection").
I'm guessing noone else has encountered this yet (or I would have heard about it). I've added a new define statement that can be set to vp231 mode (I will keep the default at vp230) as a work-around until my new parts come in.