HERSOUT2 (Weird problem)

[HenrikOlsson]

Hi,
I guess a schematic of your setup would help, at least for me. But I guess that when you "remove" the MAX232 (provided it's located between the PIC and the camera (you DO have the RS232 version of the camera and not the TTL version, right?) the USART input on the PIC is floating, tricking the HSERIN2 statement into believing it's actually received something so the execution falls thru to the HSEROUT statement

Another thing that sticks out is you have COM declared as an array of 12 bytes and the response from the camera response to a SYNC is, as far as I can see, 6+6 bytes but you're only grabbing the first one with your HSERIN2 statement. Then it all starts over and there may be a residual byte in the USART buffer.

/Henrik.

[Dave]

This looks like a loop to me...
SYNC:
HSEROUT2 [$AA,$0D,$00,$00,$00,$00]
HSERIN2 1000,SYNC,[COM]

[Megahertz]

Hi,
I guess a schematic of your setup would help, at least for me. But I guess that when you "remove" the MAX232 (provided it's located between the PIC and the camera (you DO have the RS232 version of the camera and not the TTL version, right?) the USART input on the PIC is floating, tricking the HSERIN2 statement into believing it's actually received something so the execution falls thru to the HSEROUT statement

Another thing that sticks out is you have COM declared as an array of 12 bytes and the response from the camera response to a SYNC is, as far as I can see, 6+6 bytes but you're only grabbing the first one with your HSERIN2 statement. Then it all starts over and there may be a residual byte in the USART buffer.

/Henrik.

Ok, lets start solving the puzzle.

1) The camera is RS232 type
2) USART was floating. I tied it high and no reply back now - this problem is solved (cheers for that)

secondly can you suggest on how do I get these 12 bytes if HEX8 is the highest I can use

[HenrikOlsson]

If you know the length of the response, 12 in this case:

HSERIN2 1000,SYNC,[COM\12]

Since the normal response packet (except image data) seems to be 6 bytes and the camera response to a SYNC is an ACK (6 bytes) and a SYNC (6 bytes) I'd probably do it in two steps

COM1 VAR BYTE[6]
COM2 VAR BYTE[6]
HSERIN2 1000,SYNC,[COM1\6]
HSERIN2 1000,SYNC,[COM2\6]

[Megahertz]

If you know the length of the response, 12 in this case:

HSERIN2 1000,SYNC,[COM\12]
[

Not quiet sure about this. Doesn't seem to be valid.
I have instead declared 12 different variables and trying to get the response in them...i.e. - HSERIN 500,SYNC,[COM,ID,P1,P2,P3.....]

But it does not work, must be something with the baud, any idea what is the MAX baud we can do with 8MHz osc. I will appreciate if you can show as to how you can calculate it.

[rsocor01]

Not quiet sure about this. Doesn't seem to be valid.

The following text is taken from the manual. You will probably need to include the STR modifier.

STR ArrayVar\n{\c}
Receive string of n characters optionally ended in character c

must be something with the baud, any idea what is the MAX baud we can do with 8MHz osc.

Since you are dealing with HSEROUT2 (Hardware), my guess is that the answer to your question will be in the PIC datasheet.

[Megahertz]

ok. I tried to get 512 bytes using string (STR command) and the following statements

MESS1 VAR BYTE[512]

HSERIN2 [STR MESS1\512]

The data seems to be getting corrupted as I believe some bytes arriving in HEX format don't add up in a sensible way in string format. Like $00 will be considered as null. Is there any idea as to how to get them in HEX format?

[rsocor01]

The maximum number of bytes in an array is 96 according to the manual.