Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - clkdiv

Pages: 1 2 3 [4] 5 6 ... 10
46
Hello girls and guys.

I succeeded making the camera map a shared SMB folder on my notebook. But I wonder, if it is possible also to do this the other way round? Make the Notebook map a storage at the camera?

Thanks!

Also: The card for the OS has two partitions: A very small one with some boot stuff on it, and a  big one I can't access from within windows 10. Anyone knowing how to access the larger partition, when having the card in the card reader?

Thanks

47
Ah, could you please verify this, too:

When choosing record mode "live slow motion", I can start recording with an external trigger, right. But it records as if in "normal" record mode. Same when starting via web UI.

Whereas starting record with the dedicated red record knob and the same settings records "live slow motion", as suspected.

Can you confirm this, please?

 

48
Thanks. As said the signal is reported correctly at the cameras display when setting up IO, does not matter what cable i use, neither with switch nor blank copper at the ends.

Just to make sure we are talking about same thing: The "Live slow motion" is a recording mode, whereas "live record" to H264@60fps is an option within the UTIL page! Right?

49
Thanks. What do you mean exactly? You triggered it via web interface and afterwards it worked again without ethernet but with the BNC?

Just asking, because triggering via web has not been an issue here, but it also is no option for what I want to do. Thanks!

50
Hello, thanks for reading this.

The record mode called "live slow motion" would be useful for me, but only if it could be triggered by either an external trigger or the web interface. Both is not working. Only the "real" red record button allows using this mode. Is there anything I can do about that?

And, btw., same thing with the "live record mode" that automatically records h264 @ 60 fps additionally to the slow motion. That would be useful too...

Thanks. Martin.

51
Jesus! After testing more with the camera, same thing happened again! Starting possible, ending not.

After reinstallation of the OS everything fine again! @nikon1: Did you ever really work with the trigger-IOs?

Thanks! Martin

52
Ok, thanks. Its a little downer...

53
Hello, today i recognized a strange ghost shadow caused by a bright object within the frame. I shot a clip where water drops move towards the camera and sometimes the bright sun makes the drop burn out to pure white. That's normal. But every time such bright drop passes the cameras view, the drop causes a ghost shadow. See the attached clip, please.

Does anyone know whats going on there?

Actually I recognized this before when I had a scenery with strong contrast: At the left side of the image I had some trees and at the right side a bright sky with a meadow beneath. So the lower half of the image was more or less evenly lit, trees to the left, meadow to the right.  But the upper half of the image had much more dynamic range: at the upper left the trees (dark) and at the upper right the bright sky. This strong contrast caused the upper half of the trees being much darker than their lower half, the trees were completely unevenly lit.


54
Ok, here is the last update with this: After having reinstalled OS 0.6.0 not only the IO triggers do again but also the Frame Sync output. I tested that as nikon1 suggested: using the shutter to dim the led. Smart! Thanks!

OT: Memory still the same. I will address that later.

55
SOLVED: Now since the issue appeared at IO1 and IO2 and since the shortening/opening was actually recognized by the camera (the indicators reported it correctly), I was quite sure this was not a hardware issue. So the signal came to the cam but it did neither make the camera toggle nor end recording. It had to be a software issue.

I flashed the system card and really, at least triggering works as suspected again. So it WAS a software issue. I'll check frame sync output now too, but I am quite sure this will work now too.

How can such thing happen? One thing I have learned from this is: I will for sure have a readymade second microSD with the operating system in my camera bag!

I'll post here, if the frame sync output was fixed too. Thanks again nikon1! Thanks for your efforts!

OT and BTW.: I think I will have the money for the speedbooster soon! Cu! Martin

56
Thank you so much! I can use the BNC to start record, but not to stop anymore. starting is reliable, stopping impossible then. what the hell can that be? ok i have to go to bed, will go on tomorrow. Thanks again

57
Are you also on 0.6.0?

58
Ok, when unchecking the 20mA pullup, it states signal is LO. So this was my fault here, I think.

Now I tried to trigger the camera from IO2 by shortening pins 4 and 5, labeled "COM and TRG2". Same behavior there as IO1.

Still, signals are reported on the screen as if everything was okay, but still I cant end recording.

Now, when setting IO1 or IO2 to "Shutter gating", every shortening/opening results in capturing a single frame. So, the hardware is working correctly, right? Its just I cant end record/toggle. Hmmmmm.

59
Hello nikon1, thanks a lot.

Thanks you for testing. I'll try tomorrow.

For the moment I am much more concerned about the fact that the input behaves so strange.

When setting IO1 BNC to

Threshold = 2.50
Mode = Toggle
20mA Pullup = checked

and any other options off and no cable attached to the BNC input, IO1 is HIGH.

I suppose this is false. If nothing is connected, it should be low, like IO2 and Input 3, right?

It is even HIGH, if all Ports are set to "None". Would you mind to see how it is at your camera, please?

Nevertheless shortening and opening the switch results in changing to LO and back to HIGH, reliably.


60
Hey nikon1,

thanks for you reply. I have some more weird things going on with the camera. I wanted to trigger to toggle camera recording, but it doesn't do that anymore too. The strange thing: the hi/lo-indicator at the trigger/io-setup page reliably show the signal. So it is definitively not at hardware issue.

as far as i can see, the shutter does not matter at 3 fps, no? Also i am sure it is not the led, the led runs fine when triggered by code. If i code it that the led lits up for a second everytime the signal CHANGES, it does not light up too. So there is definitively nothing coming from the camera, i guess.

but much worse for no is that i cant trigger it remotely anymore.

any ideas. thanks.

Pages: 1 2 3 [4] 5 6 ... 10