I am using beagle bone black (very similar to Rasp pi). I created an program to open a file and read temperature readings from it. It works fine when I run the code manually in the Codesys IDE. However when I create a boot application and restart my Beagle bone, the file is not opening.
This is the path to the file: /sys/bus/w1/devices/28-44260f1e64ff/w1_slave
The file I am trying to open is also from a boot application (One-wire temp sensor).
link shows how i created one-wire boot app: http://klaus.ede.hih.au.dk/index.php/BBB_and_OneWire
Thanks.
Related
I currently working on an Altera FPGA. In this project, we were given only the soft software source code using Nios II Software Build Tools for Eclipse I like to run and build the original code before making any changes to it. However, only a .pof programming file and a .cdf file was given to us, so when setting the Hardware design setup, please correct me if I’m wrong, I need the SOPC file and .sof file to configure the hardware?. I tried using the .pof or .cdf files in some way but with no success. Is there a way I can compile and build this application somehow using the .pof file or other way and thus be able to create a bsp project and load the .elf file to the FPGA. Or do I need this .sopcinfo and .sof files. Thank you.
I have a Universal App that I'm sideloading in Windows10. I would like to create a script (Powershell, VBS, batch, etc) to pin it to the Start Menu.
I have found many examples of how to write a script that pins a desktop application (like this one: https://gallery.technet.microsoft.com/scriptcenter/Script-to-pin-items-to-51be533c ). I've tried using the script to pin the actual App .exe file located in C:\Program Files\WindowsApps... but that doesn't work. When I try and pin that way, I run DoIt(), which doesn't return anything. There are no error messages, but the tile is not pinned to the start menu.
My guess is that instead of using a ComObject to interact with the file system I need a ComObject that interacts with some sort of App manager. I'm not sure how to get a list of available ComObjects to tell if this is even a possibility.
We tried to Implement two types of scenarios on Monkey Talk
One is recording through Source Code and Converting Eclipse Project to Aspect J project-Its working fine.
Second scenario we tried to use the .APK file for same project we are unable to record the apk formatted set up
Clarifications needed for Below points:
Can we record .APK file setups in Monkey talk or not
As per My Observation from Web we can use .APK file but I am
Unable to Find out the Solution for my Problem.
Looking forward to assist with you if you have any concerns & Waiting or your Informative reply..
Best Regards,
Uday Reddy.S
I was able to record using .apk when the device was connected by the option Android Device(USB). You will have to wait for 10-15 secs for the record button to be enabled.
You first have to make your app source code compatible with Monkeytalk by below steps and after than you can automate it
steps are :
1)Download MonkeyTalk for gorilla logic website and unzip it.
2)Open Eclipse and convert your project on "Aspectj" (need a plugin aspectj - for eclipse)- Once it get downloaded right click on your app,configure,Convert to aspectj.
3)Then under your project folder structure search for "libs" folder if it's exist then ok else create it.
4)Once it get done go to monkeytalk,agents,android,Monkeytalkjar file. Copy it and paste it under libs folder.
5)Once it done click on "jar" file and right click on it,Aspectjtools,Add to aspectpath.
6)Then go to Androidmanifest.xml file where we have to add some permissions;
<Uses-permissions android:name="android.Permission.INTERNET/>
<Uses-permissions android:name="android.Permission.Get_TASKS/>
and save it.
7)Go to project click on it,Right click,properties,JavaBuild Path,Check the "Aspectj Runtime Library,Ok.
8)Run your application as a Android application.
9) Open monkey talk.
10) Create new project,Create new script.
11)Then set the android sdk path under prefences; MonkeyTalk,MonketTalkPrefences,Android SDK path,ok.
12) Connect to emulator on monkeytalk.
Now you will be able to record and play in MonkeyTalk.
Some start up code for your reference eg; if we have two textfield username and password and one button submit.
app.input("username").entertext("aakash");
app.input("password").entertext("jaiswal");
app.button("submit").tap();
I am trying to troubleshoot getting a Data/Service deployed to a live server in Flash Builder with an Air application.
I am using AMF/Zend but provided my own Php file called database.php. I'm trying to find somewhere in the code base where that is referenced, but I can't find anything, other than a link to my php file in the /services folder, which I have no idea how to change to linking to a remote file.
I'm trying to build a LabVIEW plug and play instrument driver project for a device we sell. I followed the instructions to create a project, and it created the project in with the LabVIEW program:
C:\Program Files\National Instruments\LabVIEW 2011\instr.lib
I suppose I could connect that folder to source control and just do all the work there, but it feels weird to be working under Program Files. When I tried to move the project folder out into my regular workspace folder, it broke all the subpalette files (*.mnu). I could recreate them, but I'm afraid they wouldn't work for our customers when they install the driver from the LabVIEW web site.
Is it possible to move a driver project around, or does it have to stay in the default location? If one of our customers has installed LabVIEW in a different location (say on drive D:) will the driver menus not work for them?
I'm not in favour of user.lib for SCC'd items. using several LabVIEW versions at a time is a big problem.
Here is my routine:
Create the instrument library and save all code in a folder starting with an underscore ('_') (_foo)
Create an .mnu file in the parent folder of '_foo' Mylib.mnu, add the icons you need.
With OpenG package builder I create an installer routine that placed the the mnu file and the folder in instr.lib
After a restart of LabVIEW the instrument driver shows up in the instruments palette.
If you keep the code in the same relative position to the mnu file there is no problem with missing VIs.
Ton
Instrument drivers are always located in the 'instr.lib' folder in the current LabVIEW version folder. There is an environmental path set up in LabVIEW for this intrument driver folder so it will always point to the correct drive for the installation of LabVIEW used.
You should keep the folder in the location used by the wizard to ensure that when distributed to your customers the sub palette menus point to the correct location and all the VIs link correctly.
I use source control for user.lib which is in a similar location and have no problems.