Ziwi

Well all ready to load up my project, but at 260kb it wont fit in my attachments. Perhaps I could get upgraded to super cool user and get a massive 1mb attachment limit?!! I could delete stuff, but that would make the posts relevant to that obsolete? Anyway Tim before you get terribly excited, I did end up using the FHPP protocol instead of 402, mainly because it is easier. The code will look very familiar to you as it is your code!! There are only a few PDO's going back and forth. But I did test 402 and was able to hold comms between the Unitronics and the entire EDS range of 402 using SDO. I don't think there is any reason why it won't work. I had simulation software for the FHPP that I used to control the servo whilst logging PDO traffic with Canopen magic pro. Then it was just a case of deciphering with manuals etc, and getting the PLC to do the same. It wasn't too painful. FHPP looked to have far fewer commands etc. I think the reason 402 isn't supported officially is that there are a few enable/start/run/stop routine's required (or suggested). For Unitronics to claim compliance they would need a custom Function Block. But there is no reason why this can't all be programmed in ladder. Unfortunately I dont have the time to do this at the moment, but wouldn't hesitate to specify a Unitronics to 402 device in the future.

Hi Ofir Yes, I'll post an example just as soon as I've finished de-bugging. It's mostly done.

Well it seems my dilemna is solved. The error seen happens when the eds file doesn't match the device. (Thanks to www.esacademy.com support) Between config, firmware and several resets I managed to get DS402 configured and communicating with the PLC. Festo also uses a custom (alternative) protocol called FHPP. Festo tech support New Zealand helped me get FHPP working. Basically "Communication Profile" objects are mapped according to the EDS, but "Manufacturer Specific" objects don't appear to be mapped as per EDS. Fortunately the relevant PDO's are pre-mapped in the drive, and Unitronics Tx's and Rx's these PDO's without problem. All of this de-bugging would not have been possible without software such as CanOpen Magic Pro. On the plus side it seems that Unitronics can communicate with DS402 and FHPP devices.

Hi Team. I'm working through my first CanOpen project involving a safety controller and 4 drive's. 3 drive's are on DS402. I can read and write SDO's until I get to the "manufacturer profile area" at which stage I get "Object does not exist in the object dictionary" (Logged using canopen magic pro) Is this a case of Uni not supporting DS402? Incidentally the canopen magic pro can't access these SDO's either. Some of the DS301 devices are working nicely, PDO's etc. Many thanks to Tim Moulder and Fantasia for their examples.

Hi Tim I'm finally working on my first CanOPEN project comprising of a V1040, 1 x Weiss (Acopos) Rotary Servo, 3 x Festo Servo's and 1 x Sick Flexisoft safety controller. I've bought (on your recomendation) the CanOpen Magic Pro software, waiting for the USB adapter to clear customs! A question though. The Festo servo's are DSP402 which appears to be an add on to DS301? From looking at the EDS file it seems there are standard 402 index's such as 6041 -Statusword. I am planning to map relevant 402 index's to PDO's. Do you foresee any problems? Thank-you. Your help file has been extremely useful.

Thanks Ofir. I've seen that comparison, doesn't list canopen though?? Anyway will likely go with Can.

Hi All. I am familiar with Modbus RTU having done a Unitronics to VSD project, and am familiar with CanOPEN having a few systems around the factory. I am doing a new project which is leading towards CanOPEN as it is the most common denominator, although it does scare me a little. The fieldbus will consist of 4 servo drives and a safety controller (not for safety comms) Basically was trying to get an understanding of comparisons such as: a- Speed b- Stability c- Configuration ease. Modbus does seem to be a little slow - in my project using PHR/RHR (3) due to to non contiguous registers, I get R/Write times of 43 ms, adding up to 2 seconds to update 50 registers. Thanks

http://www.unitronics.com/Data/Uploads/V120/V120-22-UN2.pdf Page 2, thermocouple's, Note 1 describes the wiring. Jumper settings are laid out on page 4. In Visilogic, goto Hardware Configuration, select V120-22 and under snap in select UN2. On the Analog Inputs tab you will have No. 0 & 1. Under type, select T/C type J or K or whichever you are using. Then attach it to a variable MI123, name it something. You can also select a filter to smooth out ripple in the readings.

I remember getting caught by this "trap". Maybe it's Unitronics way of getting newbie's to understand positive transition contacts! I like the idea Damian.

Not much happens over the weekend here, and you're right about the tone of your first post! To answer some of your questions, which are in help, but to sumarise: Bits are boolean operators, ie on or off, 1 or 0. Integers are numeric values -32768 to +32767 System Bits and Integers are pre-defined, such as SB3 - I second pulse, SI32 - Current date. Memory bits and integers are freely definable by the programmer. Here is a screenshot of the simple scenario you spoke of. In hardware config, link the thermocouple input to MI1. Link MI2 and 3 to setpoints on the HMI.

Hi Janne, I know this is a few months old, but there is a better way of achieving the above without creating duplicate screens. SB 39 - See screenshot.

I've had success in using MB3 in the following attachment to reset ethernet. Useful when you have just changed parameters. Connection drops when you toggle MB3, but seeing as you have used a -|P|- contact, you can just reconnect. If you use a -| |- contact you disable ethernet!

Good tip, this works, but how are the screen numbers assigned? I watched SI252 while I flicked through the screens, and these are my screen numbers: 2,43,49,57,93,126,130,154. Seems pretty random, how are these numbers assigned or edited?

Thanks TM Very useful reference. To prove I read it, Pg 6, 2nd last paragraph I think MB123 should be 128. Regards Ziwi.

Thanks TM Like I said in my PM's this has been a great help. For the benefit of others this is also the identical comm's structure to the Beckhoff BK5120 I/O module's. CanOpen Documentation here: http://www.tritek.co.../io/bk51x0e.pdf Question: NMT status Integer (MI125 in your example) Where do I find a list of stati? (Plural of status!) I have looked through Uni and CanOpen documentation, but missed it. Ziwi