Clock

I read in BlackMagic Control pdf manual how to send commands by bluetooth LE https://documents.blackmagicdesign.com/ ... ontrol.pdf.

I managed to bond the camera and send commands like changing the focus or starting to record.

However, I still have some difficulties with the timecode. When I send a timecode, it displays it with an offset of one hour and 4 minutes.

In addition, the value I send for frames is never taken, but only hours, minutes and seconds are taken.

Here, an example of a message that I sent the camera :
Decimal values : [255, 12, 0, 0, 7, 0, 3, 0, 8, 0, 86, 34, 0, 0, 0, 0]
Hexadecimals values : [FF, 0C, 00, 00, 07, 00, 03, 00, 08, 00, 56, 22, 0, 0, 0, 0]
This message should send 22h56m00s08f to the camera, but camera display 00h00m00s$$. Dollar signs mean that those values are not affected by the command.

Does someone can explain me why there is an offset on all my commands on all my cameras and why my commands do not affect frame value?

Anyone can help??

I read in BlackMagic Control pdf manual how to send commands by bluetooth LE https://documents.blackmagicdesign.com/ ... ontrol.pdf.

I managed to bond the camera and send commands like changing the focus or starting to record.

However, I still have some difficulties with the timecode. When I send a timecode, it displays it with an offset of one hour and 4 minutes.

In addition, the value I send for frames is never taken, but only hours, minutes and seconds are taken.

Here, an example of a message that I sent the camera :
Decimal values : [255, 12, 0, 0, 7, 0, 3, 0, 8, 0, 86, 34, 0, 0, 0, 0]
Hexadecimals values : [FF, 0C, 00, 00, 07, 00, 03, 00, 08, 00, 56, 22, 0, 0, 0, 0]
This message should send 22h56m00s08f to the camera, but camera display 00h00m00s$$. Dollar signs mean that those values are not affected by the command.

Does someone can explain me why there is an offset on all my commands on all my cameras and why my commands do not affect frame value?

[Cameron Nichols]

Hi Keven, Alex,

It appears the issue is that the date field is invalid - the System RTC is set to an invalid value, hence time is wrong as well.

The command { 0xff, 0x0c, 0x00, 0x00, 0x07, 0x00, 0x03, 0x00, 0x08, 0x00, 0x56, 0x22, 0x04, 0x10, 0x19, 0x20 } will correctly set the camera system clock to 2019/10/04 22:56:00:08.

Regards
Cameron

Hi Cameron,

I tested the command you gave me : { 0xff, 0x0c, 0x00, 0x00, 0x07, 0x00, 0x03, 0x00, 0x08, 0x00, 0x56, 0x22, 0x04, 0x10, 0x19, 0x20 }.

Now, there is no weird offset. I got the value 2019/10/04 22:56:00.$$ on my camera.

The part with the frames are still not affected by the command.

Thanks for helping us.

Hi Cameron,

Thanks for your reply!

As nevekkeven said, we're still not able to send the frames. The camera return $$.

Any hints??

Thanks in advance!

Alex

Hi Cameron,

I tested the command you gave me : { 0xff, 0x0c, 0x00, 0x00, 0x07, 0x00, 0x03, 0x00, 0x08, 0x00, 0x56, 0x22, 0x04, 0x10, 0x19, 0x20 }.

Now, there is no weird offset. I got the value 2019/10/04 22:56:00.$$ on my camera.

The part with the frames are still not affected by the command.

Thanks for helping us.

Bump