LabTool on Raspberry Pi

[Tony Abbey]

Has anyone got LabTool working on the Raspberry Pi? I followed the instructions to install the application from the binary, and had to make a few binaries executable before I got a desktop display - initially it was only the simulator, but when I made the linux-armel binaries executable, the LabTool device was accessible in the menu. It also appeared as an NXP device with lsusb. However, when I tried to get data from a scope input the application said the device was not accessible. It disappeared from the menu, and now doesnt appear in lsusb. Do I need to install any special libraries - I have installed the rules for the device. I have tried running as root or pi, but that makes no difference. Is there a reset button on the hardware to restore initial conditions?

Tony

[Anders Rosvall]

Hi Tony,

There is no reset button on the hardware and there are no special initial conditions on the HW that can be restored.

The LPC4370 starts up as a DFU unit (a unit that boots via USB). When the LabTool GUI starts up on the PC/RPi it detects this DFU unit and downloads the firmware. After that, the LPC4370 will show up as another type of unit. It is this unit that the LabTool GUI then communicates with. Whenever the USB cable to LabTool is unplugged the process of downloading the firmware must be redone. It is handled automatically in the background by the LabTool GUI.

Kind Regards,

Anders

 

2014-04-03 12:51 GMT+02:00 Tony Abbey <tabb...@gmail.com>:

Has anyone got LabTool working on the Raspberry Pi? I followed the instructions to install the application from the binary, and had to make a few binaries executable before I got a desktop display - initially it was only the simulator, but when I made the linux-armel binaries executable, the LabTool device was accessible in the menu. It also appeared as an NXP device with lsusb. However, when I tried to get data from a scope input the application said the device was not accessible. It disappeared from the menu, and now doesnt appear in lsusb. Do I need to install any special libraries - I have installed the rules for the device. I have tried running as root or pi, but that makes no difference. Is there a reset button on the hardware to restore initial conditions?

Tony

--
You received this message because you are subscribed to the Google Groups "LabTool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to labtool+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
__________________________________________________
Anders Rosvall, Technical Director

Embedded Artists AB
Davidshallsgatan 16
SE-211 45 Malmö, SWEDEN

E-mail: Anders....@EmbeddedArtists.com
http://www.EmbeddedArtists.com
____________________________________________________
This communication is confidential and intended solely for the addressee(s).
Any unauthorized review, use, disclosure or distribution is prohibited. If
you believe this message has been sent to you in error, please notify the
sender by replying to this transmission and delete the message without
disclosing it. Thank you.
E-mail including attachments is susceptible to data corruption,
interruption, unauthorized amendment, tampering and viruses, and we only
send and receive e-mails on the basis that we are not liable for any such
corruption, interception, amendment, tampering or viruses or any
consequences thereof.

[Tony Abbey]

Thanks for the explanation Anders.

However, that doesnt help - whatever I have done so far on the Pi I can no longer see the LabTool. I will try later to install the software on my Mac, and see it it behaves differently.  BTW, I also downloaded the Lab_Tool_Demo.axf file but that only gives me a "Killed" message when run - not sure what it is.

Got to go out now.

Tony

[Anders Rosvall]

Hi again Tony,

To test RPi I highly recommend that you follow the instructions here (https://github.com/embeddedartists/labtool) exactly, i.e., start with 2013-09-25-wheezy-raspbian.zip

Kind Regards,

Anders

--

You received this message because you are subscribed to the Google Groups "LabTool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to labtool+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tony Abbey]

Hi Anders
I thought I had followed the instructions. Anyway - I have just solved the problem - a hardware one - I measured the 5V rail at the LabTool and it was just over 4.5V. I rearranged the USB cables so the powered hub fed the LabTool with a very short cable - the voltage is now 4.64V (4.7 before software loaded). Now lsusb showed the device, and running the application now has a black ticked LabTool device in the menu. I can now get a scope trace with a bit of noise on it and the supply voltage drops to 4.60V when capturing data - probably need to play around with my power supplies to get something a bit higher.

Lots of fun to play with it now, but I must go out!

Tony

On Thursday, April 3, 2014 11:51:07 AM UTC+1, Tony Abbey wrote:

[Tony Abbey]

Hi Anders et al

I have been experimenting with the LabTool on the R Pi - at first it was able to capture data, but as time went by, it seem to become more difficult to use, despite reconnecting a few times. At first I had problems with the analog inputs indicating full scale - playing with the drag and drop centring and/or range sometimes helped, and I was able to get D0 to show the PWM test signal. Now I cant get it to trigger or display D0. Not sure what it needs to make it work reliably. Presently I can see the PWM on A0, but it is displaying 14.29V max level on the square wave from the PWM, and that with a 10:1 probe!

Tony