Thanks a lot Fred for the answer! My concerns are not related to burst transfer but to response time... for example if I am controlling an industrail process with some small sampling period (high sampling rate), and i fire an interrupt to the usb in order to do something on the andoprid device... let's say some intenisive processing, making use of its GPU... then, i couldn't increase the sampling rate more than 10hz (100 ms perioad)... in your slides, let's say, i'm interested in the time elapsed between two succesive call of dataPipe.write function ... are they be able to respect the deadlines? Thank you again for the presentation and answers!
Yes I think I understand. You say CCS is running inside MPLAB X environment. ? Is MPLAB X running inside B4A ? so that makes the B4A IDE integral? Thanks again Fred until tomorw. I'll repost this in Thursday's Post thread of comments.
The firmware is written using CCS C. I run CCS C inside of MPLAB X to use the MPLAB X IDE instead of the CCS C IDE. MPLAB X instructs the CCS C compiler and linker to act on the CCS C source code. The compiled CCS C code is then programmed into the PIC using a PicKit3 that is also under the control of MPLAB X. The PicKit3 attaches at the lower left of the board via the ICSP commector.
What are the pros of using the ViniculumII V2-EVAL motherboard versus the VINCO Arduino compatible board ? Can you write the same type of USB/SPI/PWM/... VOS code for each, or is the VINCO restricted to Arduino APIs ?
In this case, the byte going to the PIC carries the virtual LED illumination status. The byte coming from the PIC carries the actual bluLED illumination status. It is just to demonstrate how to communicate the status between the Android device and the PIC device.
Random development platform question: I should be able to use (roughly) any PIC development board I have laying around that either supports USB or even a simpler board plus a USB-UART bridge chip to port your examples and create my own extensions; does that sound accurate?
CCS has built-in functions that allow you to code without having to load each and every bit in each and every register your code touches. CCS C will also run within the MPLAB X IDE. CCS C will allow you to twist every little bit knob there is as well. In the end, there are no differences in using CCS versus using XC compilers as you can make it as hard or as easy as you want using CCS C or you can make it as hard or as easy as you want using XC compillers. By "hard" I mean keep manual watch over every little bit in your code. The XC compilers are very easy to use as they have access to the Microchip peripheral libraries that are made up of built-in fuctions. If you want to use the Microchip Application Libraries, it is easier to use the XC compilers as the example code is written using the XC compilers. Or, you can port the MAL library code to CCS C. The bottom line is that it all comes down to what you are most comfortable with.
Nope. Visual Designer sets the attributes of the display, buttons and widgets used in the Activity displays. B4A code is then written to manipulate these diaplay, button and widget attributes programatically.
I think I may have the anwser to my own question "? So B4A codes and compiles basic for Adnroid but ? what IDE tools were used to write source code and run as firmware on the Adroid device?" Code Composer Studio from TI?
USB can fire more data in 1ms than any normal microcontroller can handle. USB dataflow depends on the type of endpoint you use. For instance, you can set a bulk in endpoint to transfer 64-byte packets in every transfer.
Higher speed USB implementations can fire 512-byte packets in the same timeframe. Plus the packets can be buffered. The USB host runs the show and everything has to be coordinated with the USB host's scheduling.
Don't get Visual Basic confused with B4A. The syntax is similar but the end product is different. Visual Basic compiles for Windows and B4A compiles for Android. There is a difference reference in the B4A documentation that points out the syntax differences in VB and B4A.
What are the Real-Time constrains of Android in terms of asynchronous communication on USB? Or, in other terms, what is the minimum time below which the android device will miss USB interrupts, will miss deadlines?
!!!What are the Real-Time constrains of Android in terms of asynchronous communication on USB? Or, in other terms, what is the minimum time below which the android device will miss USB interrupts, will miss deadlines?
Hi all -Audio is live! If you don't see the audio bar at the top of the screen, please refresh your browser. It may take a couple tries. When you see the audio bar, hit the play button. If you experience audio interruptions and are using IE, try using FF or Chrome as your browser. Many people experience issues with IE. Also, make sure your flash player is updated with the current version. Some companies block live audio streams, so if that is the case for your company, the class will be archived on this page immediately following the class and you can listen then. People don't experience any issues with the audio for the archived version.
The streaming audio player will appear on this web page when the show starts at 2 PM Eastern time today. Note however that some companies block live audio streams. If when the show starts you don't hear any audio, try refreshing your browser. If that doesn't work, try using Firefox or Google Chrome as your browser. Some users experience audio interruptions with IE. If that doesn't work, the class will be archived immediately following our live taping.
Engineers at Fuel Cell Energy have found a way to take advantage of a side reaction, unique to their carbonate fuel cell that has nothing to do with energy production, as a potential, cost-effective solution to capturing carbon from fossil fuel power plants.
To get to a trillion sensors in the IoT that we all look forward to, there are many challenges to commercialization that still remain, including interoperability, the lack of standards, and the issue of security, to name a few.
This is part one of an article discussing the University of Washington’s nationally ranked FSAE electric car (eCar) and combustible car (cCar). Stay tuned for part two, tomorrow, which will discuss the four unique PCBs used in both the eCar and cCars.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.