From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <55C4ABEA.8040106@xenomai.org> Date: Fri, 07 Aug 2015 09:00:26 -0400 From: Jorge Ramirez Ortiz MIME-Version: 1.0 References: <55C17C8E.5000909@gatech.edu> <55C3AEBE.9080603@xenomai.org> <55C3C3F8.1090808@gatech.edu> <55C3C7F4.1030107@xenomai.org> <12F45B9B-70C3-4278-BA0E-DFC26E19DBF0@gatech.edu> <55C495D6.2070706@xenomai.org> <06B32287-9FE2-42E5-BC2B-E9C807D0BD69@gatech.edu> In-Reply-To: <06B32287-9FE2-42E5-BC2B-E9C807D0BD69@gatech.edu> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Subject: Re: [Xenomai] analogy calibration issue(s) List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Yogi A. Patel" Cc: "xenomai@xenomai.org" On 08/07/2015 08:43 AM, Yogi A. Patel wrote: >>> I did - and it turns out the error was due to this line: >>> >> >>> >> __debug("Calibrating AI: %s \n", cal_info[i]); >>> >> >>> >> changing this to: >>> >> >>> >> __debug("Calibrating AI: %s \n", cal_info[i].message); >>> > >>> > I already sent you a patch for this >>> >>> This patch needs to be applied to 3.0-rc6. >>> >>> > can you send the calibration file please? >>> >>> attached. >>> >>> >>> >>> >>> I spent some more time digging at the code. The insn_read process hangs at >>> a4l_read_calibration_file because when the for loop (line 214) runs the second >>> time, it does not find the string “elements”, and thus sets nb_elements to 65535 >>> - causing it to run forever. you didnt get any errors while calibrating? >>> >>> This is because it is looking for the elements string under “analog_output” in >>> the calibration file, however there is no such section in the calibration file. yes, read_int should be checking for errors. >>> >>> The calibration file also doesn’t include all the analog inputs (it only shows >>> 7, whereas the board has 16 AIs. So does the PCI 6220). What am I missing/not >>> understanding? yes I was looking into this as well; the soft calibration feature replicates the Comedi version behaviour so this is very likely a bug.