 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Pages: 1 2
Hi,
I noticed in some posts that a new firmware for the motorcontroler of our heads is available. Can somebody give any details? What are the improvements from 020681?
Best Regards,
Volker
Offline
Hi Volker,
It's supposed to allow faster move of head but we still need more tests on it to be sure it works fine with Papywizard and that it doesn't break or damage motors 
Vincèn
Offline
vincen wrote:
It's supposed to allow faster move of head
I hope it comes soon this new firmware 
Tobias
Offline
After seeing a post by Claude (http://www.autopano.net/forum/p71914-to … -30#p71914) and speaking to Josef by e-mail, there appears to be the potential for substantial speed gains by updating to this latest firmware.
Regarding the concerns raised by vincen, has anything occured to give reason to believe that the motors may be damaged by the new firmware?
After searching the forums for how to update the firmware, it appears there may be a 'communal' ready to use USB-TTL cable for connecting a PC to merlin to update, is this still so?
I cant seem to find any posts on how to actually update the firmware once connected. Where does one download the latest version, and is instalation technical, or is there a simple program to run?
Offline
PAY ATTENTION THAT THE NEW FIRMWARE 020781 COULD ONLY BE APPLIED ON MERLIN VERSION 2 AND NOT ON VERSION 1 !!!
PARTIAL CONCLUSIONS
Hello Will ("wjh31") and the others ...
- After upgrading and tests, I can say that the upgrade will not dammage the motors.
- Several "USB to TTL" convertors (for the upgrade) are at disposal of the users in the different countries for free, the only charge is to ship the device to the next user who need it.
Have a look on the next "sticky" subject :
http://www.autopano.net/forum/t8080-fir … -inventory
In the second post, you will find where are the "USB to TTL convertors" (differents countries ... please manage that the devices stay in the dedicated countries !!!)
Please inform me if you move the convertors from one user to another, so I can update the data's !
- The installation is simply running a "firmware uploader" , no secrets ... no special knowlegdes !
The only condition is to establish a "wired" connection from the PC to the Merlin !
A wireless connection can't be used for the upgrade.
The upgrade can't be done by a MAC or a Unix/Linux machine ... only PC's running Windows !
- Now that the tests are finished and that no risks have been detected (the results will be published soon ...), I have put the new firmware at disposal together with the Firmware uploader and documents describing the procedure:
http://www.papymerlin.com/merlin-firmware-upgrade/
FINAL TEST RESULTS
Hello all,
Thanks to the local distributor of the Merlin head in Belgium, I have
finished the experiments with the new Firmware 02.07.81.
It should be remember that the the upgrade to this firmware 02.07.81 is
reserved to Merlin V2 (generation 2 = all Merlin's with firmware type
02.##.##)
This is confirmed in the next official document of Synta :
http://www.papymerlin.com/app/download/ … 1288734168
The results are :
1. No risk for the Merlin head ... Anyway this is allways possible to
downgrade to the 02.06.81 if necessary !
2. The main objectives was
2.1. Speed problems : (10 x 10 = 100 pics STD conditions as defined by
Andrew)
2.1.1. Solved with "alternate drive OFF" : the speed is much faster
then the Merlin V2 (firmware2.06.81) 13 min 27 sec <> 31 min 19 sec
2.1.2. With "alternate drive ON" : the speed is slightly lower then
the Merlin V2 (firmware2.06.81) 16 min 10 sec <> 14 min 17 sec
2.2. Scaling effect : Solved, no scaling effect anymore .... The start/stop
steps are visually "smoother" with the new firmware !
Subsequent to this observation, I have downgraded the Merlin to the firmware
02.06.81 and make a new serie of trials with the "alternate drive on"
As immediate result, the scaling effect was back !!!
By tightening the bolt of the yaw axis of the Merlin (it was not more
possible to move the head by hand...), I have repeated the trial with the
"alternate drive on" and the scaling effect disapear !!!
Conclusion: the utilisation of the "alternate drive" cause "brutal
movements" who result with the scaling effect mainly on the yaw axis (all
the weight of the Merlin and the camera is concentrated on the yaw axis,
much less on the tilt axis !
General conclusion : the "upgrade" could/should be done without any
problems, this will really improve the speed, suppress the scaling effect,
result in more smouth movements as for results probably less problems with
long focals (less blur ...) in Gigapixel's
Recommandations : Go ! but don't use the "alternate drive ON" anymore !!!
Claude Offline
claudevh wrote:
In the second post, you will find where are the "USB to TTL convertors" (differents countries ... please manage that the devices stay in the dedicated countries !!!)
Thanks, i have emailed krtekcz2000 regarding this
Offline
claudevh wrote:
- Shortly, after the last "ongoing" tests, I will put the new firmware at disposal together with the Firmware uploader and documents describing the procedure:
http://www.papymerlin.com/merlin-firmware-upgrade/
Since I have the Goto version this should work for me, but I have one question... is the .HEX file the one I need to update with? The pdf it talking about a .MCF file. Just making sure before I upgrade.
Offline
Hello Kevin,
No the .HEX isn't the right file !!!
The right file is a .MCF file ...
You want to go too fast, in my previous post, I have said:
Shortly, after the last "ongoing" tests, I will put the new firmware at disposal
NOW ALL NECESSARY FILES ARE AT DISPOSAL herafter :
http://www.papymerlin.com/merlin-firmware-upgrade/
Claude Offline
claudevh wrote:
Hello Kevin,
No the .HEX isn't the right file !!!
The right file is a .MCF file ...
You want to go too fast, in my previous post, I have said:Shortly, after the last "ongoing" tests, I will put the new firmware at disposal
NOW ALL NECESSARY FILES ARE AT DISPOSAL herafter :
http://www.papymerlin.com/merlin-firmware-upgrade/
Claude,
If only V2 Merlin mounts can be upgraded with this firmware:
http://www.autopano.net/forum/p71940-ye … -12#p71940
Then I think it would be good to state that on the web page for firmware and loader download AND also to provide there a the description of how to determine which version of head you have; because at the moment the words that stand out on that page at first glance are 'ALL MODELS'.
Offline
claudevh wrote:
- The installation is simply running a "firmware uploader" , no secrets ... no special knowlegdes !
The only condition is to establish a "wired" connection from the PC to the Merlin !
A wireless connection can't be used for the upgrade.
The upgrade can't be done by a MAC or a Unix/Linux machine ... only PC's running Windows !
I you don't mind to risk a bit, you can use wine emulator on Linux. I successfully updated it today with wine-1.3.6-1.1.x86_64 on openSUSE 11.3
Radek
Offline
Thank-you for the info Radek !
Claude Offline
Yes Andrew, you are right !
Upgrade only for Merlin V2 and how to find the informations about the version ...
I will put the informations on my web page.
Thank-you Andrew !
Claude Offline
Update complete Version 02.07.81
Offline
Thank you to develop a new firmware.
But what is it you guys abandoned me?
My name is not listed in my country too.
I, PC and Merlin does not have a cable connection.
My PC is no slot for RS-232, RS-232C no slots.
On my PC I have is only USB1 and USB2.
My PC;
os: Windows XP SP3
Bluetooth: Serial port COM40
Other:
Touch Control Panel (firmware2.0)
I do what Merlin can do to upgrade the firmware?
Regards.
Offline
Hello "Mamoo"
In order to help you, we must know where you live ... (GMT + 7 will be somewhere in Asia)
This will be added to your profile in our Papywizard "Known" Users database/
http://www.autopano.net/wiki-en/action/ … back#mamoo
In function of your Country, I will try to help you with a maximum of informations !
Anyway your Dell Vostro have USB connectors and it is possible with the right device to connect the Merlin with a "USB to TTL 5V" wired connection and make the upgrade ...
Waiting for news from you ...
Where do-you live ?
Claude Offline
Hi Claude
I bought a kit on Kolor. So, all personal data available kolor.
For further information, please get the kolor.
Where I live in Japan.
I look forward to your support.
Best regards
Offline
Hello "mamoo"
For the firmware upgrade, you will need to establish a "wired" connection between your PC and the Merlin.
This could be done via a "USB to TTL 5V" device.
I recommand the "FTDI-TTL232R 5V" that can find everywhere in the world.
Exemple in Japan : http://jp.mouser.com/ProductDetail/FTDI … 9QpQ%3D%3D
You will need the FTDI-TTL2325 5V himselve, a phone cable with a RJ12 (= RJ25) connector and 2 resistors of 220 Ohm.
Then you must assemble all together according the pictures herafter.
Then you will need to make the firmware upgrade himselve ... For that you have all explanations, the firmware uploader and the firmware himselve availlable on the next web site :
http://www.papymerlin.com/merlin-firmware-upgrade/
Good luck !
Claude Offline
Hi Claude,
many thanks for the upload of the new firmware 02.07.81.
I installed it without any problems (WIN7/64/FTDI).
regards
Volker
Offline
Hi Claude,
Thank you for introducing me to the net shop.
I like his #17post create the image of the cable unit.
Best regards
Offline
Hi Claude,
Update complete.
Results update:
1. "T and C controller" of the moving speed becomes faster.
2. "Win PC for Papywizard" was less an offset of the picture in mosaic mode. In particular, "Lens: 300mm: Pitch arm side: right" if, "Inertia angle: 1.0deg" no problem at all either.
I sincerely appreciate your efforts.
Imaging conditions the image below:
"Win PC for Papywizard", "Lens: 300mm: Pitch arm side: right", "Inertia angle: 1.0deg"
Thank you
Offline
Hello Mamoo,
Happy that you succeed with the firmware upgrade !
Two small things:
- you can use the FTDI convertor as a "wired connection" if you want .... with the PC. Sometime beter if you want to use your camera with "tethered shooting" !
- for the mosaic mode (and others), please set the "alternate drive" to OFF, this will be more efficient with Papywizard now !
Have fun !
Claude Offline
Hi Claude,
Thanks for letting me know the information to become.
It is important to use cables.
By the way, "alternate drive OFF" is shorter than a 200mm lens effect. However, 300mm lens move that would slow.
Attach the bottom log data.
Thank you
Extract of Debug logdata DATA:Papywizard(Win32 PC),Mosaic-NbPicts,Pitch-right,Orientation-landscape,Direction-pitch --------------------------------Lens 300mm----------------------------------------- Alternate drive OFF <startTime> 2010-11-10_09h36m05s <endTime> 1m53s(per9image) 2010-11-10_09h37m58s Alternate drive ON <startTime> 2010-11-10_09h43m25s <endTime> 1m10s(per9image) 2010-11-10_09h44m35s ************************* pitchAxis moving time ********************************* Alternate drive OFF 'pitchAxis' *>* 11sec 2010-11-10 09:36:33,890::Main::DEBUG::ShootController.__onShootingSequence(): sequence=moving 2010-11-10 09:36:33,890::Shooting::DEBUG::MerlinOrionAxis.drive(): 'yawAxis' drive to -3.7 2010-11-10 09:36:33,921::Shooting::DEBUG::MerlinOrionAxis.drive(): 'pitchAxis' drive to -2.4 *2010-11-10 09:36:34,155::Merlin-Orion_pitchAxis::TRACE::MerlinOrionAxis._directDrive() *2010-11-10 09:36:45,405::Shooting::INFO::Stabilization Alternate drive ON 'pitchAxis' *>* 4sec 2010-11-10 09:43:43,125::Main::DEBUG::ShootController.__onShootingSequence(): sequence=moving 2010-11-10 09:43:43,125::Shooting::DEBUG::MerlinOrionAxis.drive(): 'yawAxis' drive to -3.7 2010-11-10 09:43:43,171::Shooting::DEBUG::MerlinOrionAxis.drive(): 'pitchAxis' drive to -2.4 *2010-11-10 09:43:43,390::Merlin-Orion_pitchAxis::TRACE::MerlinOrionAxis._alternateDrive() 2010-11-10 09:43:43,453::Merlin-Orion_pitchAxis::DEBUG::MerlinOrionAxis._alternateDrive(): alternate speed move 2010-11-10 09:43:45,000::Merlin-Orion_pitchAxis::DEBUG::MerlinOrionAxis._alternateDrive(): final move *2010-11-10 09:43:47,733::Shooting::INFO::Stabilization ************************* yawAxis moving time ********************************* Alternate drive OFF 'yawAxis' *>* 4sec 2010-11-10 09:36:48,092::Main::DEBUG::ShootController.__onShootingSequence(): sequence=moving 2010-11-10 09:36:48,092::Shooting::DEBUG::MerlinOrionAxis.drive(): 'yawAxis' drive to 0.0 2010-11-10 09:36:48,125::Shooting::DEBUG::MerlinOrionAxis.drive(): 'pitchAxis' drive to -2.4 *2010-11-10 09:36:48,328::Merlin-Orion_yawAxis::TRACE::MerlinOrionAxis._directDrive() *2010-11-10 09:36:52,453::Shooting::INFO::Stabilization Alternate drive ON 'yawAxis' *>* 6sec 2010-11-10 09:43:50,421::Main::DEBUG::ShootController.__onShootingSequence(): sequence=moving 2010-11-10 09:43:50,421::Shooting::DEBUG::MerlinOrionAxis.drive(): 'yawAxis' drive to 0.0 2010-11-10 09:43:50,467::Shooting::DEBUG::MerlinOrionAxis.drive(): 'pitchAxis' drive to -2.4 *2010-11-10 09:43:50,703::Merlin-Orion_yawAxis::TRACE::MerlinOrionAxis._alternateDrive() 2010-11-10 09:43:50,733::Merlin-Orion_yawAxis::DEBUG::MerlinOrionAxis._alternateDrive(): alternate speed move 2010-11-10 09:43:52,842::Merlin-Orion_yawAxis::DEBUG::MerlinOrionAxis._alternateDrive(): final move *2010-11-10 09:43:56,937::Shooting::INFO::Stabilization --------------------------------Lens 200mm----------------------------------------- Alternate drive OFF <startTime> 2010-11-11_06h21m56s <endTime> 1m09s(per9image) 2010-11-11_06h23m05s Alternate drive ON <startTime> 2010-11-11_06h20m07s <endTime> 1m17s(per9image) 2010-11-11_06h21m24s ************************* pitchAxis moving time ********************************* Alternate drive OFF 'pitchAxis' *>* 6sec 2010-11-11 06:20:25,640::Main::DEBUG::ShootController.__onShootingSequence(): sequence=moving 2010-11-11 06:20:25,640::Shooting::DEBUG::MerlinOrionAxis.drive(): 'yawAxis' drive to -5.5 2010-11-11 06:20:25,687::Shooting::DEBUG::MerlinOrionAxis.drive(): 'pitchAxis' drive to -3.7 *2010-11-11 06:20:25,983::Merlin-Orion_pitchAxis::TRACE::MerlinOrionAxis._directDrive() *2010-11-11 06:20:31,187::Shooting::INFO::Stabilization Alternate drive ON 'pitchAxis' *>* 3sec 2010-11-11 06:22:11,812::Main::DEBUG::ShootController.__onShootingSequence(): sequence=moving 2010-11-11 06:22:11,812::Shooting::DEBUG::MerlinOrionAxis.drive(): 'yawAxis' drive to -5.5 2010-11-11 06:22:11,858::Shooting::DEBUG::MerlinOrionAxis.drive(): 'pitchAxis' drive to -3.7 *2010-11-11 06:22:12,000::Merlin-Orion_pitchAxis::TRACE::MerlinOrionAxis._alternateDrive() 2010-11-11 06:22:12,140::Merlin-Orion_pitchAxis::DEBUG::MerlinOrionAxis._alternateDrive(): alternate speed move 2010-11-11 06:22:14,140::Merlin-Orion_pitchAxis::DEBUG::MerlinOrionAxis._alternateDrive(): final move *2010-11-11 06:22:15,905::Shooting::INFO::Stabilization ************************* yawAxis moving time ********************************* Alternate drive OFF 'yawAxis' *>* 4sec 2010-11-11 06:20:33,875::Main::DEBUG::ShootController.__onShootingSequence(): sequence=moving 2010-11-11 06:20:33,875::Shooting::DEBUG::MerlinOrionAxis.drive(): 'yawAxis' drive to 0.0 2010-11-11 06:20:33,905::Shooting::DEBUG::MerlinOrionAxis.drive(): 'pitchAxis' drive to -3.7 *2010-11-11 06:20:34,171::Merlin-Orion_yawAxis::TRACE::MerlinOrionAxis._directDrive() *2010-11-11 06:20:38,953::Shooting::INFO::Stabilization Alternate drive ON 'yawAxis' *>* 6sec 2010-11-11 06:22:18,608::Main::DEBUG::ShootController.__onShootingSequence(): sequence=moving 2010-11-11 06:22:18,608::Shooting::DEBUG::MerlinOrionAxis.drive(): 'yawAxis' drive to 0.0 2010-11-11 06:22:18,655::Shooting::DEBUG::MerlinOrionAxis.drive(): 'pitchAxis' drive to -3.7 *2010-11-11 06:22:18,750::Merlin-Orion_yawAxis::TRACE::MerlinOrionAxis._alternateDrive() 2010-11-11 06:22:18,890::Merlin-Orion_yawAxis::DEBUG::MerlinOrionAxis._alternateDrive(): alternate speed move 2010-11-11 06:22:21,546::Merlin-Orion_yawAxis::DEBUG::MerlinOrionAxis._alternateDrive(): final move *2010-11-11 06:22:24,515::Shooting::INFO::Stabilization
Offline
How to find what version of Merlin head do I have? (Non GoTo = V1, GoTo = V2?)
Offline
FelixAutopano wrote:
How to find what version of Merlin head do I have? (Non GoTo = V1, GoTo = V2?)
As mentioned here:
http://www.papymerlin.com/merlin-firmware-upgrade/
The Merlin version can be found in the Papywizard log file just after connection, a few lines before the end. The Merlin version is indicated by the first two digits of the firmware !
Offline
Hello "felixautopano",
Version 1 and version 2 are linked to the versions of the main printed circuit board of the Merlin's ...
This has nothing to do with Goto or Non Goto ! There is no difference between the Merlin's Goto or Not Goto ... except the hand-controler ... the Non Goto Hand controler has no screen, only buttons !
As allready said by Andrew ("mediavets"), just look into the log file of Papywizard.
According the informations that we have, you have a Non Goto Merlin V2, with the firmware 020681, you have ugraded from 020581 to 020681 time ago.
You can upgrade to the firmware 020781 if you want without problems ...
Claude Offline
Pages: 1 2
