plule

Nice, it would be quite cleaner. As you say, since I updated to Sysmac 1.10 (from 1.08), it lets me map a variable to the physical outputs even when an axis manage the drive. However, even if it shows no error or warning while compiling or transfering, it doesn't seems to work. (physical outputs stays at low). The unit version of our NJ is 1.06, is it too old? Is it upgradable? (I can't find a complete history of revisions nor how to update the firmware) Thanks.

Thanks a lot, I learned a lot about the SDOs! I just embedded it in a FB, I attached it if someone is interested (with a small variation, I think quick variations of the input could leave an output in the wrong state). We're almost there, but strangely enough the outputs only deliver 0.24V when active... It might be a wiring problem, we're looking into it. Have a nice day and thanks again. edit: It was a wiring problem, it works like a charm now :) SDOTest.zip

Hello, I'm stuck with a simple problem : I need to manage a drive (R88D) and control its programmable outputs (named R-OUT1 and R-OUT2). The usecase is that the motor controls an unreversible pump and both outputs are supposed to control the movement direction. I'm able to access these two bits via the I/O map (bits 16 and 17 of the output "Physical Output"), HOWEVER as soon as I link a sysmac studio axis to this drive, the output "Psysical Output" in the I/O map isn't accessible anymore (as it is supposed to be managed by the sysmac studio axis). Once the axis linked to the drive, Sysmac Studio's axis system doesn't seems to offer a way to access these variables, and I can't find a configuration that fits my usecase. So I can either manage the outputs or the drive but not both. Another solution would be to manage the drive myself without the axis system, but I've not been successful in this direction (and it seems to be a lot of work for a simple problem), but since I don't need to do anything fancy with the motor, this might be the solution. Any help would be appreciated, thanks a lot.