Jump to content

Darkflame808

Members
  • Posts

    9
  • Joined

  • Last visited

Profile Information

  • Location
    Honolulu, HI

Darkflame808's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. Thank you for clarifying. Just thought I would ask. On a positive note I found a solution to the problem. I used the BSRobots file that was posted by Imgburn Member: Disemble. This one only initializes the correct autloaders. Thanks to both for your efforts in creating these great programs and autoloader drivers.
  2. Good morning, I wanted to ask if it were possible to have the Imgburn stop initializing the other autoloaders once the NK50 was found? The reason I am asking is I actually have two autoloaders from acronova. One is the Nimbie NK50V/Y and the other is the Nimbie 11. When I open IMGBurn this is what I get. I 10:18:46 ImgBurn Version 2.5.8.0 started! I 10:18:46 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 10:18:46 Total Physical Memory: 4,075,224 KiB - Available: 1,463,476 KiB I 10:18:46 Initialising BS_Robots... I 10:18:46 BS_SDK Version 2.2.0.277 Build 2013.02.22 I 10:18:46 Initialising SPTI... I 10:18:46 Searching for Auto Loader devices... W 10:18:47 I/O Interface 'Debug Mode' has been Enabled! D 10:18:48 BS_Robots_Connect - Robot Count: 2, Return Code: 0 I 10:18:49 Initialising Device (Auto Loader 0)... D 10:18:49 BS_Robots_GetRobotInfo - Robot ID: 0, Model Name: Nimbie NB11, Version Info: Ver:V1.10.05.26, Return Code: 0 D 10:18:49 Robot ID: 0 - Model: Nimbie NB11, Version: 1.10.05.26 D 10:18:49 BS_Robots_EnumDrives - Robot ID: 0, Drive Count: 1, Drive IDs: F, Return Code: 0 D 10:18:49 Robot ID: 0 - Drives: 1 D 10:19:07 BS_Robots_Active - Robot ID: 0, Status Code: , Status Description: , Return Code: 0 D 10:19:07 BS_Robots_GetDriveName - Drive ID: F, Drive Name: F: Optiarc DVD RW AD-5280S, Return Code: 0 D 10:19:07 Robot ID: 0 - Drive ID: F, Drive Name: Optiarc DVD RW AD-5280S I 10:19:07 -> Auto Loader 1 - Info: Nimbie NB11 1.10.05.26 I 10:19:07 Initialising Device (Auto Loader 1)... D 10:19:07 BS_Robots_GetRobotInfo - Robot ID: 1, Model Name: NK50, Version Info: Ver:1.13.02.20, Return Code: 0 D 10:19:07 Robot ID: 1 - Model: NK50, Version: Ver:1.13.02.20 D 10:19:07 BS_Robots_EnumDrives - Robot ID: 1, Drive Count: 1, Drive IDs: F, Return Code: 0 D 10:19:07 Robot ID: 1 - Drives: 1 D 10:19:26 BS_Robots_Active - Robot ID: 1, Status Code: , Status Description: , Return Code: 0 D 10:19:26 BS_Robots_GetDriveName - Drive ID: F, Drive Name: F: Optiarc DVD RW AD-5280S, Return Code: 0 D 10:19:26 Robot ID: 1 - Drive ID: F, Drive Name: Optiarc DVD RW AD-5280S I 10:19:26 -> Auto Loader 2 - Info: NK50 Ver:1.13.02.20 I 10:19:26 Found 2 Auto Loaders! I 10:19:26 Searching for SCSI / ATAPI devices... I 10:19:26 Initialising Device (\\?\usbstor#cdrom&ven_optiarc&prod_dvd_rw_ad-5280s&rev_1.z8#0100420085000000001&0#{53f56308-b6bf-11d0-94f2-00a0c91efb8b})... I 10:19:26 Device Address: [0:0:0] I 10:19:26 Drive Letter: (F:) I have one autoloader for my DVD drive and one autoloader for my printer. The IMGburn program will initialize both which will break the autoloader for the printer until I reinitialize with the NK50V software. With that said, is there a way to make a routine that says if Nimbie 11 is found, stop searching for any more BSRobots? In an older driver I found before it would pop up a dialog box asking to select the autoloader but that broke any command line batching options cause it would hang on that screen waiting for input. For now I've resorted to just reinitializing every time I run Imgburn but just thought I would ask. Thank you!
  3. Ok I downgraded to 2.5.5.0 and it reset all my settings, I decided to go again back to 2.5.6.0 (with all reset settings) and it seems to be picking up the right loader again. I guess this is a fluke of my unique install and not a bug in the program. Disregard.
  4. Hi, I have a Nimbie N11 autoloader DVD drive and a Nimbie NK50V Autoloader printer drive. I've been using Imgburn 2.5.5.0 with my nimbie dvd auto loader without problems. I recently upgraded to 2.5.6.0 and when I went to start it up, instead of the dvd autoloader doing it's normal tray eject/close function. My printer autoloader started humming like it was trying to process a dvd through the printer. (the printer loader was empty as I had not yet transfered my imgburn copies from the dvd autoloaders eject bin to the printer autoloaders input bin yet). It also resulted in a crash with the usual close, retry etc. I have since downgraded to 2.5.5.0 and after reenabling the acronova autoloader checkbox everything is in working order again. Thanks!
  5. Hey Ligthning!, Thanks for the response. I'm in Hawaii, my timezone might be a little off from yours and also here in the states we are celebrating a Holiday. I am uploading a video that shows the operation right now as we speak to youtube. ETA for upload completion is 24 minutes then youtube does their own conversions. Once their conversion is complete I will post a link for you to view the video. If you need anything else, let me know. I may not be able to assist you till tomorrow though as I will be out of my home all day today. I'll get that link to you as soon as youtube emails it to me. Thank you for all your support, I am looking forward to your next release Have a great day! -Richard Heres the video you requested. Http://www.YouTube.com/watch?v=4b9gjrrbOhw Thanks! I've been looking at the sdk and there is a initialize bravo command you can send as the first load function. This would tell the bravo to eject tray and the robotic arm would check the tray first and remove the disc if any are found before loading the tray to prevent double stacking if a disc is already in the tray. All subsequent jobs would use the standard load function.
  6. Just wanted to add that minor suggestion to imgburn. When doing a job using a primera publisher unit the final job leaves the drive tray open after completion. It's more cosmetic then practical but closing the drives after a job could help prevent dust (or critters) from exploring into the drive during downtime between jobs.
  7. Thank you Cynthia for the quick replies. I look forward to seeing the release of 2.5.2.0. Keep up the great work you guys. Imgburn is hands down THE best program for managing my burning needs.
  8. Is 2.5.2.0 available for download? If it's beta i'd love to try it out if it's open to new people. If not i'll grab a cookie and patiently wait
  9. Good morning. I wanted to ask about your developments in autoloaders. I saw that you had recently added support for what appears to be a Bravo SE (according to the picture shown your tutorial). I was wondering if you had plans to support bravo's other line of products. Specifically the Bravo II. I currently own a Bravo II and I have followed your instructions of placing the files located in the PTRobot archive into the installation directory. When opening up IMGburn I have checked off the auto loaders checkbox but yet the unit still returns 0 autoloaders found. Could this be due to it not being compatible? I've tried to read the SDK and see that there are different initialize strings for each of the autoloaders but my abilities to figure it out beyond that are limited. I've resorted to using a macro to control the robot through the calibration utility but it's klunky and if I get an error the macro starts spitting discs everywhere and jams the unit up. If you need access to my terminal to implement bravo ii capabilities please let me know! I'd be glad to help! Thank you very much! -Richard
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.