Reprise du message précédent :
Argh ! I have all but crystal. My elec shop can't get one 20 MHz ! :-(
 
I have to order one crystal at selectronique !
 
B.
 
P.S. : Fariouche, pwd en mp ;-)

 
 
I've uploaded some of my captured packets.
http://rt3wiki.free.fr/pmwiki.php?n=Main.VANPackets
 
When I will captures some more packets, I will try to figure out the "8fc" packet...
 
Fariouche

Hi,
 
   another small sniffing session today..
 
 4D4:
 
   It seems some fields were inverted in my
 first implementation of of van-frames.
 
 Those are the changed lines, I'd appreciate
 if someone can confirm:
 
4D4::6:0x7F:int: X-0x3F : balance
4D4::6:0x80:bit:        : + updating
4D4::7:0x7F:int: X-0x3F : fader
4D4::7:0x80:bit:        : + updating
4D4::8:0x7F:int: X-0x3F : bass
4D4::8:0x80:bit:        : + updating
4D4::9:0x7F:int: X-0x3F : treble
4D4::9:0x80:bit:        : + updating
 
 4FC:
 
  It seems there's a gauge in byte 6:
  (it changes from FF when the dashboard is on)
 
  4FC: WA- 8000054800005924640000 A
  4FC: WA- 800005480000FF24640000 A
 
  4FC::6::bcd:            : unknown gauge
 
  any idea?
 
 524:
 
 byte 9, as we know, refers to the message that the display
 will show.
 
 This line was wrong:
 
  524::9:0x01:bit:        : ? door(s) open
 
 instead:
 
  524::9::cmp:0x01        : door(s) open
  524::9::cmp:0x41        : ASP/ESR disabled
  524::9::cmp:0x44        : Automatic lighting active
  524::9::cmp:0x45        : Automatic wiping active
 
 it seems that byte 8, bit 5 is used to tell the display
 to show the message:
 
 sent when disabling auto wiping: 524: W-- 0000010000000000184500000000 -
 sent when enabling:              524: W-- 0000010000000000384500000000 -
 
 so I'd add:
 
 524::8:0x20:bit:        : show message
 
 664:
 
 664::3:0x04:bit:        : related to mileage counter
 664::3:0x02:bit:        : esp off button
 
 8A4:
 
 Those three seems wrong:
8A4::1:0x01:bit:                        : contact
8A4::1:0x02:bit:                        : engine
8A4::1:0x04:bit:                        : economy
 
 I would suggest:
 
8A4::1:0x01:bit:                        : key pos A (1)
8A4::1:0x02:bit:                        : key pos M (2)
8A4::1:0x04:bit:                        : engine running
 
 and:
 
8A4::0:0x80:bit:                        : unknown
 
 
 If someone can confirm these discoveries I'll update
 the WiKi..
 
--
 
 - alex.

Hi,
 
For 4fc, I've actually noticed something similar.
byte6 is FF until a put the key in position 2 (engine ready to start)
In position2, byte6 keeps increasing from 0d to 3f and byte7 change from 00 to 62.
Then, I start the engine -> byte 6 value drops to 40. And just after the engine started, the value goes up to 3f, byte7 still remains at 62.
It's somewhat related to the engine status (maybe to the "glow plug" (I'm not sure about the english word... THe french word is "bougie de pre-chauffage")
Also, when I switch off the engine, the values becomes 40 for some time and then FF.
 
For 664, mine is always:
664 WA- 00000F04FFFF00FFFFFF00 A
 
For 8A4 I confirm. But I will add that the bit 1 is still ON when key in pos M.
My values are:
01 when key in in pos A.
03 when in pos M.
07 when engine running.
and in my case, byte0 is always 8F.
 
For 524:
mine is:
524 W-- 000000000000000040FF00000000 - (doors unlocked by remote control)
524 W-- 000000000000000041FF00000000 - (doors locked by remote control)
In my case, byte 9 is always FF (did not tried to open/close the doors)
My car does not have ESR and auto light, so I cannot confirm that
524 W-- 082080032001800040FF00000000 -
I have this kind of values just after putting the key to pos M -> Maybe related to engine/car check up status, that are related to the dash board lights switching ON and OFF (ABS/ Battery/etc...)
 
Fariouche

 
 Thank you, I've modified the WiKi. How do we want
 to call pos A and pos M ? We need better names
 
--
 
 - alex.
 
 

Nobody said to me that there is a 20 MHz crystal in each NetworkInterfaceCard ... and I have a lot of old card ;-)
 
So I have all for my VAN Monitor interface now :-)
 
B.

 
 Glad to hear that!
 
 Your first assignment is to check that everything
 that is described in ParseableCommands applies to your car
 
--
 
 - alex.
 

dwery a écrit :   Thank you, I've modified the WiKi. How do we want  to call pos A and pos M ? We need better names   --    - alex.

 
Hehe. I've had the same feeling...
I think that pos A is a good name (accessory position)
Pos off for key just inserted?
The most difficult to name is the pos2 (pos M) for ready to start engine...
 
Fariouche

Well done. If all is good I should get my operationnal VAN Monitor Interface this week-end :-)
 
Just a question : where did you get VAN and VAN/ on the car ? Behind the RD3/RT3 ? Is it possible to get it at the BSI, which is much easy ? Which wire ?
 
Thx
 
B.

 
Hi,
 
 it's possibile but I don't know the pinout on the BSI.. I use the mini-ISO connector
 on the RD3.
 
--
 - alex.

 
 
For me, I've taken the VAN signals directly from the Main connector (Connector ISO A with an ISO to ISO cable)
 
Fariouche

Also, do you think that it's possible to use the "Audio Synt Voc" audio instead of the CDC audio input?
 
Fariouche

 
 I don't know if that input is available on the RD3, as the
 pinout refers to the RD2, but if yes they probably have
 to be activate via software..
 
--
 
 - alex.

I finally got some time for experiments in my car. The following behaviour for possible CDC ports 0x8EC and 0x4EC are:
 
The display (or radio?) tries to read data from 0x4EC every second. It reading this port with the same interval as the radio audio settings at 0x4D4 and it keeps on even when the radio is off. I tried to return the same packet as the radio uses when playing the built in cd (82D60003000303..) but the CDC button didn't work.
 
The display (or radio?) tries to send data to 0x8EC when the radio is powered on or off. During power on, "1181" is transmitted to this address three times since the display doesn't get an expected response. After these three times, no new data are transmitted to this address until the radio is powered off. When powered of the display tries to send the data "1101" to address 0x8EC. It tries three times and then it's silent.  
 
I think some type of answer like the radio "8C4 WA- 8A2440 A" are expected but we need more clues here. There are atleast 2^24 combinations assuming the message is 3 bytes long.
 
I switched to CDC audio input with a command "t8D4C1203" and the radio went silent and the display stopped updating the cd-info. When I held down a button on the radio, assuming the radio would send this information to the CDC instead of the radio/built in cd, I noticed some new messages.
 
For example, if the CD button is held down about 5 seconds and then released, the radio sends the following messages:
 
8C4 WA- 8A221D A
8C4 WA- 8A229D A
8C4 WA- 8A22DD A
..
8C4 WA- 8A22DD A
8C4 WA- 8A225D A
 
After about 2 seconds, bit 7 is set ("9D" and then also bit 6 ("DD". "8C4 WA- 8A22DD A" is repeated 2 times every second. When the button is released, bit 7 is set to 0 and bit 6 is still 1 ("5D". These bits looks the same when I test to press and hold down "Radio", "Cd", "CDC", "Seek-", "MAN", "Seek+", "1".."6" so all these keys can probably be used to control our own "CDC".
 
"Seek-" generates the message "8A2213" when pressed, "MAN" - "8A2217" and "Seek+ - "8A2214". The audio settings buttons and volume knob works as usual (and also updates the display) when the CDC input is activated.
 
/Per

Hi guys,
 
I worked this week-end on my Van Monitor. Finally I took VAN bus on the Part C of the radio connector. I take VCC on the +perm, on the connector. Should I use +VAN ?
The four wires goes out with a USB fem cable VCC - VAN - VAN/ - GND
 
But results was not good :-(
 
I can't get the Monitor working. But tonight I checked my PIC : it's a 16F876A and the A one need alignment program by 4 words --> the hex code of rev3 is not align to 4 words :-(
I should add a nop or using a 16f876 : I have a 16F876, so I can test tomorrow again :-)
 
Another point : in the code, I saw a possibility to put a led for status on rb4. How I can use it ? Using a led and a resistor (around 1KOhms ?) between the RB4 pin and VCC or GND ?
 
Thx
 
B.

OOps' I forgot something :
 
Compiling rev3 software with MPLAB, I got an error :
 
Warning[219] QBDIC-PROGVAN MON REV3.ASM 329 : Invalid RAM location specified.
 
It's a problem ?
 
B.

Brouno a écrit :   OOps' I forgot something :   Compiling rev3 software with MPLAB, I got an error :   Warning[219] QBDIC-PROGVAN MON REV3.ASM 329 : Invalid RAM location specified.   It's a problem ?   B.

 
Are you sure that you selected the correct type of microcontroller under MPLAB?
For rb4, it's only used for timing debugging.
 
Also, do not forget to disable the watchdog in MPLAB.
 
Fariouche

Pfff ... I'm very disappointed :-(
 
This is not working ! I never get the prompt '>' or a sign of life ...
 
The only thing that seems good is ... alimentation ... and hopefully compilation of soft rev3
 
I'm using MPLab for compilation. All seems good but I have always the error at line 329
A quick check on the 16F876's datasheet reveal to me there is no memory at bank3/0x90 ?? But I think this not the real pb for me ...
 
I checked my pic : I was using a 16F876-4/SP --> Yes I'm a newbie in pic : It's a 4MHz one !
 
Using my other one (16F876A-I/SP), should be OK. I added some nop for code alignement
 
I'm using IC-Prog for programming the pic. Watchdog Timer (WDT) was on by default --> off now
 
I'm using a max232 with external 1uF capacitors as in datasheet (between 1-3, 4-5, gnd-6, 2-vcc, 16-gnd, polarity checked) rather than the max233
 
So what else ??
 
I have no oscillo, so I can check nothing :-( Is there a possibility to add a led (blinking ??) on the pic, for diag ?
 
B.

Hi,
 
You can add a led to a gpio on the PIC.
Just add a resistor in line with the LED (about 200ohm should be ok)
 
Then use port B4 (witch is already set as an output) and set it to high at boot time. Check the output with the LED (or just a voltmeter!). If it's ON, then your PIC is ok. Else check your code and if still nothing, the PIC may be faulty (I had one that did not work as expected!)
If the gpio is ON, then your PIC is most likely ok. -> the problem can be on the MAX232 converter. I'm using the max233 (witch is a lot simpler to solder)
 
Fariouche

Ok, I'll try that.
 
For setting B4 to high, using
 
bank0
bsf PORTB,4
 
is OK ?  
 
B.

Yes, that's it.
and bcf to clear.
 
Fariouche

 Brouno,
 
   also check that all the other config bits are ok.
 The correct config word has been posten a couple of weeks ago.
 
 anyway, XT osc, powerup timer, no watchdog
 
--
 
 - alex

Hi
 
The assembler returns a "Invalid RAM location specified" because it cannot check which RAM bank the program is using. The "Bank3" macro changes the bank to 3 so the "movwf 0x90" acutally writes to the valid RAM address at 0x190.
 
Where have you added these "nop" instructions to align the code? It is possible they can interfere with the timing used to read/write data from/to the VAN but the "nop" instructions shouldn't stop the software from returning the ">" prompt.
 
/Per

 
 
Isn't it HS osc for 20Mhz? XT is for 4MHz?
 
Fariouche

 
 ooops...you're right, HS osc.

Thx guys for yours tips. I was not here the last three days.
 
So, it's not working at this time, but you get me other tips : the config word.
I get no attention to this. I was using RC oscillator :-( , no powerup timer :-(
 
So I'll try that.
 
I put the nop just after the _main label.
 
For getting the led on at start, now my code look like this :
 
    ORG 0x0000  
 
_ResetVector:  
  clrf    PCLATH          ; Set page bits for page0
  Bank0
  bsf     PORTB,4
  goto    _Main           ; Go to startup code
 
I tested too to use the org directive, as that is, if I understood well, for putting code at determined address.
 
I'll keep working
 
B.

You must place the "bsf PORTB,4" -instruction before right the "_WritePrompt:" label. Otherwise the interrupt routine is overwritten by the "goto _Main" instruction (or viceversa) and the PIC code will fail to start.
 
/Per

No wdt, powerup timer, hs osc, code alignment, ... what else ?
 
I am desperate ...
 
I think I'll try a simpler program now ...
 
B.

 Hi,
 
   any news? I use an F876A too and the code you can
 download from the wiki works without modifications...
 
 I've been quite busy.. saw the last report about the CDC
 status and think we need to snoop a real one. I'll try to see
 if I can manage to meet someone with a cdc...
 
--
 
 - alex.
 

Hi all,
 
Well, it seems that we are all a bit busy these days... :-)
 
Brouno, I think that you still did not corrected your problem?
You problem sounds weird... Maybe I can help you if we meet (I see that your are located in france, 78... I'm in the 94 ;-) )
 
My car will go to the garage (to repair my clim). Anyone know if it's necessary to declare the CDC in the BSI to be able to use the CDC input, or will the pic be able to auto-declare the CDC?
 
Fariouche

You'll need peugeot to declare the cdc. Et demande a etre là, sinon ils te diront qu'on peut pas sans cdc efectivement branché....

 
 
Ok, merci!
 
Fariouche

Hello  
I have just finished to weld my electronic circuit and to compile the program of the PIC16F876.  I think of beginning the tests in the weeks next. If you want I can provide you my diagram of electronic circuit and the typon for update on wiki.
 
Best regards
Lio

Hi Lio,
 
   welcome aboard. We will appreciate any help you
 can provide.
 
  I've just won an auction on ebay for a cdc charger..
 i'll snoop it as soon as I can... 10/15 days probably.
 
--
 
 - alex.

Hi,
 
Welcome lioelec!
 
That's cool for the CDC! This will help a lot for sure
 
Fariouche

Welcome Lio!
 
The more people we get, the more we will find out..
 
I got a puppy last week so there hasn't been so much time for the computer or CDC project. I tries to follow the thread.  
 
The CDC will probably be the key to how the PIC should react on the VAN. I'll try to implement the behaviour in the code as fast as possible when we have the logs.
 
/Per