illustrate
Products            Buy            Support Forum            Registrations            Professional            About           
 

Composer Max Batch Ripper Drivers

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    I have only done 2 of the drive so far and I can always re-calibrate.

    Leave a comment:


  • bhoar
    replied
    Re: Composer Max Batch Ripper Drivers

    Originally posted by EliC
    Brendan,
    Can you comment on

    1)--composerdrive= how do I know which to choose?
    2)--drivebank= do I change this value?
    1) You'll need to experiment. There's no rhyme nor reason as to the association between windows drive letter and composer drive position. FWIW, they are layed out like this (facing the unit), if my memory of an hour ago still works:


    B A
    D C

    2) Doesn't matter too much at the moment, I'm running with all four set to --drivebank=1. If you set A and C to --drivebank=1 and B and D to --drivebank=2, there might be some slight robotic optimization possible now, maybe more in the future, but let's keep thing simple for the moment, shall we?

    Originally posted by EliC
    no love with

    --spacestring=+

    does it matter where in the line I add the code? or just anywhere in each command line?
    See email for an updated driver kit, should work out of the box now.

    Originally posted by EliC
    BTW, I guess all 716s are not created equal, though I can't believe theirs isn't off the shelf. The drive bay comes out to far. I had firmware 1.06. Tried upgrading to their firmware 1.10. Its a bit better but the tray will need a little modding to get rid of the vertical disc tabs.
    As I said, always measure (comparatively) the tray spacing and clearance before installation. There are multiple reasons I said leave some original drives in - helps with aligning new drives comparatively but, more important from my point of view, now you're possibly stuck having to reseat the originals in the correct positions and robot problems might come up that seem like driver problems but are really drive or placement problems.

    Also, depending on the mounting arrangement, you might be able to install the 716 drives farther back to workaround the tray extension issue.

    -brendan

    Leave a comment:


  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    BTW, I guess all 716s are not created equal, though I can't believe theirs isn't off the shelf. The drive bay comes out to far. I had firmware 1.06. Tried upgrading to their firmware 1.10. Its a bit better but the tray will need a little modding to get rid of the vertical disc tabs.

    Leave a comment:


  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    no love with

    --spacestring=+

    does it matter where in the line I add the code? or just anywhere in each command line?

    Leave a comment:


  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    Brendan,
    Can you comment on

    1)--composerdrive= how do I know which to choose?
    2)--drivebank= do I change this value?

    Leave a comment:


  • bhoar
    replied
    Re: Composer Max Batch Ripper Drivers

    Originally posted by EliC
    Finally got something that may have more meaning:

    [codebox] MOVE:2 SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _MOVE`{ib}:I{ib}M PICK SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _PICK:BXOLast command failed or timed out, skip value is cyclebins...
    MOVE:3 SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _MOVE`{ib}:I{ib}M PICK SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _PICK:BXOLast command failed or timed out, skip value is cyclebins...
    MOVE:4 SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _MOVE`{ib}:I{ib}M PICK SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _PICK:BXOLast command failed or timed out, skip value is cyclebins...[/codebox]
    Er, try adding --spacestring=+ to each command line

    (edit: changed ] to + as cancel batch needs the brackets)

    -brendan
    Last edited by bhoar; July 04, 2008, 03:09 AM.

    Leave a comment:


  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    Primera sells the PX-716A with a standard bios, so I think at least that one is safe. If the other drives don't work I will have to buy some more 716s.

    Leave a comment:


  • bhoar
    replied
    Re: Composer Max Batch Ripper Drivers

    Originally posted by EliC
    I will wait patiently until Sat. In the mean time I will be busy swapping out drives. Anyone in the market for some Pioneer DVR-105 drives?
    Just for reference purposes, I strongly suggest leaving either the top or bottom pioneer drives in to begin with, until you get the alignment right on the replacements and/or double check whether they need to have the faceplates removed and/or have the metal casing modified.

    -brendan

    Leave a comment:


  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    I will wait patiently until Sat. In the mean time I will be busy swapping out drives. Anyone in the market for some Pioneer DVR-105 drives?

    Leave a comment:


  • bhoar
    replied
    Re: Composer Max Batch Ripper Drivers

    Originally posted by EliC
    yes, baud and com are set correctly in dBpoweramp

    Tested and working fine with both Primo and GD3 Encode Center - I know the baud and com are independent in these programs, just saying the robot is working.
    Do the commands work correctly in hyperterm?

    Perhaps the baud rate is adjustable and these other programs first probe to find the serial port speed?

    Anyway, as I said via email, I can't check against my unit till saturday.

    -brendan

    Leave a comment:


  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    yes, baud and com are set correctly in dBpoweramp

    Tested and working fine with both Primo and GD3 Encode Center - I know the baud and com are independent in these programs, just saying the robot is working.
    Last edited by EliC; July 03, 2008, 10:06 PM.

    Leave a comment:


  • bhoar
    replied
    Re: Composer Max Batch Ripper Drivers

    Originally posted by EliC
    what is the drive bank setting? Maybe this is where I am going wrong?
    Is the baud rate set correctly? Is the com port set correctly?

    -brendan

    Leave a comment:


  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    what is the drive bank setting? Maybe this is where I am going wrong?

    Leave a comment:


  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    Finally got something that may have more meaning:

    MOVE:2 SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _MOVE`{ib}:I{ib}M PICK SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _PICK:BXOLast command failed or timed out, skip value is cyclebins...
    MOVE:3 SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _MOVE`{ib}:I{ib}M PICK SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _PICK:BXOLast command failed or timed out, skip value is cyclebins...
    MOVE:4 SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _MOVE`{ib}:I{ib}M PICK SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SI SICommand Failed: _PICK:BXOLast command failed or timed out, skip value is cyclebins...

    Leave a comment:


  • EliC
    replied
    Re: Composer Max Batch Ripper Drivers

    Using lastest drivers
    -which drive in the matrix is A? B? C? D?
    -how many of the bins is the robot using? which ones? for what?
    -robot does not seem to respond at all (robot is fixed and responding in Primo)
    -every test I run in the configuration menu gives the following error:

    [][cancel batch]

    Leave a comment:

Working...