Re: [etherlab-users] problem with ethercat xml
Hi Graeme, I updated the eeprom from twincat. And it did not have any details in the xml apart from version and product code. Only after I ran the application which had the code to configure sync managers it populated the xmlwith those values. I was a little confused when in previous mail you said that get the pdo config from ethercat struct and then put it in the application. Can you please clarify on that ?. Thank you, Rahul On 8/25/17, Rahul Deshpande wrote: > Hi Graeme, > > I was going through the ethercat commands. I came across 'ethercat > struct' and 'ethercat xml'. When I used the 'ethercat xml' in pre-op > and op mode I got the following xml (PFA). > > Before and after running the application(In which we have configured > the pdos from the example you had sent), the 'ethercat struct' and > 'ethercat xml' produce the same data which does not consist of PDO > config settings. > > Is this a case of corrupt EEPROM or that we are unable to configure > PDOs in our application ? > > Regards, > Rahul > ___ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
[etherlab-users] problem with ethercat xml
Hi Graeme, I was going through the ethercat commands. I came across 'ethercat struct' and 'ethercat xml'. When I used the 'ethercat xml' in pre-op and op mode I got the following xml (PFA). Before and after running the application(In which we have configured the pdos from the example you had sent), the 'ethercat struct' and 'ethercat xml' produce the same data which does not consist of PDO config settings. Is this a case of corrupt EEPROM or that we are unable to configure PDOs in our application ? Regards, Rahul 1337 ___ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
[etherlab-users] (no subject)
Hi Sam, I saw your post on etherlab forum with respect to working counter 0. I am facing a similar problem. I am using xenomai environment. After I run the application it goes to the OP state. I get the same output as you have put up on the etherlab forum (https://www.mail-archive.com/etherlab-users@etherlab.org/msg01472.html) How did you fix this error ?. Looking forward to your reply. Thank you, Rahul ___ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
Re: [etherlab-users] No CoE communication
Hi Graeme, Thanks for the application. I tried implementing your master without the patches and with my application. It does not reach the application stage and throws this error prior to login. I get the following errors (PFA). It throws a reception of CoE dictionary request failed' Regards, Rahul On 8/23/17, Graeme Foot wrote: > Hi, > > I have attached a test app to have a look at. It is a (very) cut down > version of how my app works. Of course I use RTAI, so it won't be > compatible with your Xenomi environment. > > > In main.c at the top of runECat() I have a list of EtherCAT devices and > their addresses. It is hard coded here but can of course be loaded from a > config file. The device names match devices in the etherCATSlaves.c file. > > etherCATMaster.c contains the code to configure and run the master. > etherCATSlaves.c contains each slave's code. > > yaskawaSGDV_create() > - configures the device and gets the PDO command offsets > > yaskawaSGDV_prepareToRun() > - calculates each commands address (after the domains are populated and > allocated) > - sets cyclic synchronous position mode (optional, the mode can be set at > any time while running) > - sets the control word to zero, just in case > > yaskawaSGDV_run() > - is called once each scan. add code here to control the axis > > yaskawaSGDV_prepareToStop() > - is called when the app is closing. add any code here to clean up your > axis > > > Note: In this app the prepareToStop() functions are called once and then the > app is shut down immediately. In reality you should continue your realtime > cycle until all of the devices are stopped, disabled and safe to turn off. > The app also relies on some of my patches. > > > I hope this helps > > Regards, > Graeme. > > > > -Original Message- > From: etherlab-users [mailto:etherlab-users-boun...@etherlab.org] On Behalf > Of Graeme Foot > Sent: Wednesday, 16 August 2017 10:42 a.m. > To: Rahul Deshpande ; etherlab-users@etherlab.org > Subject: Re: [etherlab-users] No CoE communication > > Hi, > > I've been asked to let you know what master version and patches I'm using. > I'm still running an old version (2526 from the stable-1.5 branch, > 12/02/2013). The script I use to download it is attached > (004-etherlab_master). > > I use buildroot to create my linux system, so the script tar's the master > folder and puts it in the buildroot downloads folder. Note: I also use a > really old buildroot from 2012 with a few modifications, but I have attached > the mk file that it uses. > > The patches that I apply are also attached. > > The build options I use are: > --with-linux-dir="" > --enable-cycles > --enable-rtdm > --enable-e100 > --enable-e1000 > --enable-e1000e > --enable-cx2100 > > > I use RTAI, but that shouldn't make any difference. > > > Regards, > Graeme. > > > -Original Message- > From: etherlab-users [mailto:etherlab-users-boun...@etherlab.org] On Behalf > Of Graeme Foot > Sent: Tuesday, 15 August 2017 12:39 p.m. > To: Rahul Deshpande ; etherlab-users@etherlab.org > Subject: Re: [etherlab-users] No CoE communication > > Remember to reply-all to mail the forum as well. > > Line 85 has: #define Yaskawa_Sigma7 0x0539, 0x02200301 This is > different to my drive, so it may still be the Sigma 7 id causing a mismatch, > but it is the id being returned from the ethercat struct command. > > Other than that, I've got no idea. > > Graeme. > > > -Original Message- > From: Rahul Deshpande [mailto:rahulg...@gmail.com] > Sent: Tuesday, 15 August 2017 3:57 a.m. > To: Graeme Foot > Subject: No CoE communication > > Hi Graeme, > > I understand I have been mailing a lot, my questions may seem repetitive. > > The positive now is I was able to get to OP state by forcefully setting 1c12 > and 1c13 to 0 (PDO assignment fro SM2 and SM3). > > I am still not able to configure the PDOs though. What I have narrowed down > to is, somehow CoE communication just does not happen. I was going through > the etherlab forum and came across a post where they mentioned some sdo's > had to be set prior to configuring the PDOs. Is it that ? > > Also, It would be great if I could just reach out to you on your phone if > thats not an issue. Could sort out my problems faster and not disturb you > with constant emails. Do let me know if thats an option. > Thank you so much. > > Regards, > Rahul > ) AT91 NAND: 8-bit, Software ECC Scann
[etherlab-users] ethercat commands
Hi, I wanted to know where I can find the list of all ethercat diagnostic commands (ethercat slave, ethercat master, ethercat debug 1 etc). Thank you, Rahul ___ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
[etherlab-users] Problem with getting yaskawa sigma 7 into op state
Hi, I am trying to use the yaskawa sigma 7 servopack with the igh master. I am unable to get it into op state. It always gets stuck at pre-op state. Also there are many datagram timeouts. I have attached logs as well as my xenomai application which I am using for this. It would be really helpful if somebody could guide me in the right direction. Regards, Rahul Linux version 2.6.33 (root@linux-0mmn) (gcc version 4.3.6 (Buildroot 2011.11) ) #1 Tue Apr 11 09:38:47 CDT 2017 CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 CPU: VIVT data cache, VIVT instruction cache Machine: Atmel AT91SAM9G20-EK Memory policy: ECC disabled, Data cache writeback Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 Kernel command line: console=ttyS1,115200 root=/dev/mtdblock1 mtdparts=at91_nand:128k(bootstrap)ro,256k(uboot)ro,128k(env1)ro,128k(env2)ro,2M(linux),-(root) rw rootfstype=jffs2 PID hash table entries: 256 (order: -2, 1024 bytes) Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 64MB = 64MB total Memory: 61120KB available (3196K code, 333K data, 128K init, 0K highmem) Hierarchical RCU implementation. RCU-based detection of stalled CPUs is enabled. NR_IRQS:192 AT91: 96 gpio irqs in 3 banks AT91 I-pipe timer: div: 128, freq: 1.032000 MHz, wrap: 63.503875 ms I-pipe 1.16-01: pipeline enabled. Console: colour dummy device 80x30 Calibrating delay loop... 197.83 BogoMIPS (lpj=989184) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok devtmpfs: initialized NET: Registered protocol family 16 AT91: Power Management AT91: Starting after user reset bio: create slab at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Advanced Linux Sound Architecture Driver Version 1.0.21. Switching to clocksource at91_tc0 NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 2048 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 2048 bind 2048) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. NetWinder Floating Point Emulator V0.97 (double precision) I-pipe: Domain Xenomai registered. Xenomai: hal/arm started. Xenomai: scheduling class idle registered. Xenomai: scheduling class rt registered. Xenomai: real-time nucleus v2.5.6 (Wormhole Wizards) loaded. Xenomai: starting native API services. Xenomai: starting POSIX services. Xenomai: starting RTDM services. JFFS2 version 2.2. (NAND) (SUMMARY) Ā© 2001-2006 Red Hat, Inc. msgmni has been set to 119 io scheduler noop registered (default) atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL atmel_usart.1: ttyS1 at MMIO 0xfffb (irq = 6) is a ATMEL_SERIAL console [ttyS1] enabled atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL brd: module loaded loop: module loaded ssc ssc.0: Atmel SSC device at 0xc48c (irq 14) NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit) AT91 NAND: 8-bit, Software ECC Scanning device for bad blocks Creating 3 MTD partitions on "atmel_nand": 0x-0x0040 : "Bootstrap" 0x0040-0x0400 : "Partition 1" 0x0400-0x1000 : "Partition 2" atmel_spi atmel_spi.0: Atmel SPI Controller at 0xfffc8000 (irq 12) usbmon: debugfs is not available ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver at91_ohci at91_ohci: AT91 OHCI at91_ohci at91_ohci: new USB bus registered, assigned bus number 1 at91_ohci at91_ohci: irq 20, io mem 0x0050 hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. udc: at91_udc version 3 May 2006 mice: PS/2 mouse device common for all mice input: gpio-keys as /devices/platform/gpio-keys/input/input0 rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0 IRQ 1/rtc0: IRQF_DISABLED is not guaranteed on shared IRQs rtc-at91sam9 at91_rtt.0: rtc0: SET TIME! Registered led device: ds5 Registered led device: ds1 usbcore: registered new interface driver usbhid usbhid: USB HID core driver ALSA device list: No soundcards found. TCP cubic registered NET: Registered protocol family 17 rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock Empty flash at 0x001fe914 ends at 0x001ff000 VFS: Mounted root (jffs2 filesystem) on device 31:1. devtmpfs: mounted Freeing init memory: 128K ec_rt_dpr: module license 'unspeci
