![]() |
|
|
|
|
|
||||||||||
|
| User list | You are not logged in.
Hello chaps,
now my Merlin is up and running, modified and I have a lot of fun looking at it when it´s doing all the work for me.
During the processing of a spherical panorama I realized that the time between two shots in the same row varied quite a lot. Sometimes Merlin moved to the next position very quick, sometimes it creeped awfully slow. When I talked to Tobias he confirmed this behaviour on his Merlin.
Now I renamed the files shot in the same row (screenshot below), the numbers after the @ give you the exact time hh-mm-ss picked up from the exif date in every single file. There is a clear system. It´s 8 seconds - 24 seconds - 8 seconds and so on. 8 seconds between two shots feel good, but 24 for the same distance/angle are a pain in the - well, you know.... What I would really like is 8 - 8 - 8 - 8 -.......
Is this behaviour of Merlin known, is it new, did I miss the magic "optimize time" button in a menue I have not looked at by now? My Merlin works with a win xp pc, pw 2.1.11, Claudes bt-module and fresh batteries. Tobias (360pano) uses a very similar environment, but pw 2.1.12.
Regards Martin
Last edited by emess (2009-11-01 01:10:11)
Offline
Hi Martin, nice to meet you here! ![]()
I have just built up my Merlin-System and tested it and noticed same affect. Moving time between shots is 3times longer every second shot.
System: HP-notebook VISTA 32, N800, ursaminor Bt, Merlin - no crown modifying, adapter modified for the 5D MKII but only with ATX 10-17 usable. (just cut and glued to get the lens on the middle of the axis)
H.a.n.d.
Chris
www.insight360.de
Offline
Could you send me a complete log file with a few images showing this problem (witch the log level to trace before)? does it happen only when you are in bright sun?
Offline
Hello Frederic,
unfortunately I can not provide you the logfile - after updating to 2.1.12 I cleared it.
5:20pm at this time of the year is not the time for bright sunlight here in Dortmund. The test shot was done in my workshop, with a neon lamp at the ceiling. I read about the light influence issue of the sensor, so I shaded the area of the bubble level with my hand, because I had this idea, too. But that did not influence the behaviour of the rotation axis.
The set of pictures above was produced with the 4+12+12+12+8 (32mm) preset that came with pw. The screenshot shows the data of the 0 deg pitch row. Thinking about it again, I might have NOT changed the value for the focal length of the lens in the camera/lens configuration tab. But thats impossible to verifynow. And if I understand the idea of the presets right, this should not interfere, should it?
If you give me an exact idea of what data you expect I´ll shoot the test row again.
Regars Martin
Offline
Right, preset don't need focal lenght... Try to reproduce the problem, and as soon as it occurs, send me the log file (with trace turned on). There are 2 different routines for positionning: one which uses the goto function of the head, an another one wich first make an external closed loop, then use the goto function. This is for moves < 6°... There is maybe an issue, there.
Offline
Hi, made my own preset 6 shots at 0° for the ATX @ 14mm
you can see every second move is slow:![]()
I don`t know, how to upload a file so here is part ot the log-file:![]()
Erstellt von Papywizard 2.1.12
<preset name="EOS 5D Tokina ATX @ 14mm"/>
</header>
<shoot>
<pict bracket="1" id="1">
<time>
2009-11-03_09h37m54s
</time>
<position pitch="0.0" roll="90.0" yaw="0.0"/>
</pict>
<pict bracket="1" id="2">
<time>
2009-11-03_09h38m06s
</time>
<position pitch="0.0" roll="90.0" yaw="60.0"/>
</pict>
<pict bracket="1" id="3">
<time>
2009-11-03_09h38m38s
</time>
<position pitch="0.0" roll="90.0" yaw="120.0"/>
</pict>
<pict bracket="1" id="4">
<time>
2009-11-03_09h38m50s
</time>
<position pitch="0.0" roll="90.0" yaw="180.0"/>
</pict>
<pict bracket="1" id="5">
<time>
2009-11-03_09h39m23s
</time>
<position pitch="0.0" roll="90.0" yaw="240.0"/>
</pict>
<pict bracket="1" id="6">
<time>
2009-11-03_09h39m35s
</time>
<position pitch="0.0" roll="90.0" yaw="300.0"/>
</pict>
<pict bracket="1" id="7">
<time>
2009-11-03_09h39m55s
</time>
<position pitch="90.0" roll="90.0" yaw="300.0"/>
</pict>
<pict bracket="1" id="8">
<time>
2009-11-03_09h40m28s
</time>
<position pitch="-90.0" roll="90.0" yaw="300.0"/>
</pict>
</shoot>
</papywizard>
complete file is here for download: www.dd-webtest.de/kundendownloads/papyw … preset.xml
reg Chris
www.insight360.de
Last edited by grosserfox (2009-11-03 10:05:13)
Offline
Really strange...
Offline
Hello, made another test with 20 shots 18°. Time between shots 6 sec, every second shot 22 sec.
Claude told me, that my bt unit from ursaminor with black knob has a known defect! (thanks to claude
)
So silly question: could this be caused by the bt-unit?
@ Martin, what kind of bt-unit are you using?
reg Chris
Last edited by grosserfox (2009-11-03 21:38:28)
Offline
The one below, so I don´t think the bt-module is under suspicion.
I made some tests with interesting results today (Frederic will get a full logfile tomorrow - it´s stored on the other computer).
First - 32mm preset:
The creeping effect is there, as described below in all rows.
Second - 10-17, 8 around preset:
Creeping every second shot, horizontal and vertical movements are affected depending on what movement comes last.
Third - Mosaic with 300mm focal length lens:
NO creeping at horizontel movements (< 6 deg increments WITHOUT overlap) BUT at vertical movement (> 6 deg increments WITHOUT overlap). Unfortunately Frederics idea to force the movement mode (forcing NON-positioning with the head goto function) came too late, I´ll have to check the creeping behaviour again tomorrow.
Regards Martin
Offline
Hi all,
I use of-course the same module as as Martin ...
Nice your GIF ! Can-I use it ?
Generally, I use a Nokia N770 with Papywizard 1.6 and I never had this kind of problems ...
I use also from time to time a Netbook, but wit Papywizard 2 stable release, no problems ...
I use only a laptop PC (Vista 32) for test purpose only ... I will try tomorrow if I can reproduce this problem.
Fréderic do-you remember when you have introduced the new algorithm's for the "optimized movements" in Papywizard (Version ?)
Offline
claudevh wrote:
Fréderic do-you remember when you have introduced the new algorithm's for the "optimized movements" in Papywizard (Version ?)
Yes, sure: it has been added in the 2.1.6 release. But it can be switched off from the second tab of the Merlin/Orion plugin configuration dialog...
Martin, could you send me your preset (input) file? I will have time to make some tests tomorrow...
Offline
Frederic,
I used the standard presets which come with pw 2.1.12. No customization. Do you still need them?
Logs are on the go.
Regards Martin
Last edited by emess (2009-11-04 07:44:28)
Offline
emess wrote:
I used the standard presets which come with pw 2.1.12.
And the problem occurs with all of them?
Offline
I just made some tests, but I can't reproduce the problem... I really need to see your log file when it happens.
Offline
That is strange - maybe a firmware update in the Merlin itself?
My Merlin is one of the latest batch afrer it was reported that they were unavailabe fur some time in late summer. Chris, when did you purchase yours? It seems to me that this issue was not reported before. This made me wonder, because it is very obvious. Maybe someone of you out there can cross-check with an older Merlin head? Just let the 32mm preset proceed and have a careful look if every second movement is very slow.
I dont´t remember that there is a serial no. on the head, does anybody know exactly? Or is there a way to find out the firmware version of Merlin via pw?
Regards Martin
Offline
Hello,
The version of the firmware can be queried with the ":e1" command on the larger SkyWatcher mounts (EQ6, HEQ5)
Maybe this works with Merlin also.
Use my Terminal program to send the command and see the result.
It can be downloaded from:
http://www.ursaminor.hu/downloads_en.html
Best regards,
Tamas
Offline
Tamas, it seems to work
Mine returns '010981'. I added this command at init stage, so it will appears in the log.
But I don't know if this issue is related to the firmeware. BTW, does it occurs with mosaic mode? Try to setup a config with the same steps as with the presets...
Offline
Frederic,
please have another look at the mosaic logfile. i had the impression that the vertical movement was quite slow in comparison to the horizontal. Without overlap that is just over the 6 deg border.
I see there are some more things to check for me tonight.
Regards Martin
Offline
@ Martin, bought my Merlin 3 weeks ago!
reg Chris
Offline
Hi, not very familiar with mosaic mode, but built one and run it: same effect every second shot movement was much slower!
reg Chris
Offline
question on the fly...
are autofocus, image stabilizer, exposure time & aperture set to off on your cam?
Liebe Gruesse,
Georg
Offline
gkaefer wrote:
question on the fly...
are autofocus, image stabilizer, exposure time & aperture set to off on your cam?
Hi Georg this even happens without camera connected and shutter set to simulation mode!
thks reg Chris
Last edited by grosserfox (2009-11-04 22:50:20)
Offline
ok...
also antivirus software, firewalls, even vpn clients, boinc clients for seti projects etc. shutdown?
lg
Georg
Offline
Powered by PunBB
© Copyright 2002–2005 Rickard Andersson
|
CHOOSING KOLOR Why choose Kolor? Which solution to choose? Download a trial Where can I buy? Education |
SOFTWARE Autopano Pro Autopano Giga Panotour Panotour Pro XnView |
ACCESSORIES Training DVD Panobook PROJECTS Paris 26 Gigapixels Yosemite 17 Gigapixels |
COMMUNITY Forums Blog |
COMPANY About Kolor Corporate blog Resellers Contact |
PRESS Press center Press review TOOLS My account |
