Log In
Register
Forum
Topic RSS
12:23 pm
March 19, 2015
Offline
Hello,
Starting this topic to assist the developing team in what features the community likes to have.
My wish is to get a comparable alternative to the Arduino IDE, if possible.
Please give a reply with your wishes for this product.
Regards, John
1:01 pm
March 19, 2015
Offline
My wishes:
- Add a feature that allows to incorporate/combine existing Arduino Libraries into the LabView environment.
- Manipulate microprocessor registers. (Bitwise, Bytewise, Short, Long, ..)
- SPI, I2C, CAN support. (Due, CAN0 & CAN1 port)
- Make parallel loops available. (If possible according to the resources available depending on microprocessor)
Thanks, John
3:31 pm
March 19, 2015
Offline
since the parallel loops behaviour is not possible on one threaded controller, probably a kind of scheduler could run behind the code, which allows using of a certain number of loops (let's say 4 or 6).
3:59 pm
March 19, 2015
Offline
Hello Viwoi,
Yes, you need some overhead (small scheduler) but 4-6 loops is already a good start. Perhaps only two for smaller targets.
Regards, John
4:25 pm
March 12, 2015
Offline
John;
Thanks for starting this discussion. It will be certainly very useful for us. I will be recording the incoming suggestions from the community to our list of features for next releases.
Thanks again.
Filipe
Cheers
Filipe
5:53 pm
March 20, 2015
Offline
A call library node that allows use of the numerous Arudino shields with libraries
Automatically include the lib in the build.
7:43 pm
March 12, 2015
Offline
As far as multi-threading goes, since AVR does not support hardware multi-threading and is meant for simpler applications, it is best to treat these as single loop interrupt driven systems. We do support pin interrupts with callbacks and timer interrupts are on the roadmap. This is usually sufficient for these types of systems. Since the Due supports hardware multi-threading, this is the architecture we would most likely have a chance at implementing a decent scheduler.
Other items listed above that are on the roadmap include SPI, I2C, and CAN.
Providing a generic interface to libs is very tricky. At this time we will be manually adding support for libraries based on priority.
Thanks for the suggestions.
1:30 pm
March 24, 2015
Offline
I2C and SPI are on the top of my wish list. Yesterday I posted on LinkedIn and Filipe pointed out I had a misunderstanding about being able to see the block diagrams and suggested I come here.
Already though this is WAY better way to program Arduino.
1:39 pm
March 12, 2015
Offline
Hi Greg;
You found us. 
Welcome. We are capturing the feedback from the community and, yes, SPI and I2C are quickly climbing the ranks. I do too like this way to program Arduinos better; but, then again, I am a little biased as a LabVIEW enthusiast.
Filipe
Cheers
Filipe
6:59 pm
March 19, 2015
Offline
Steffan said
As far as multi-threading goes, since AVR does not support hardware multi-threading and is meant for simpler applications, it is best to treat these as single loop interrupt driven systems. We do support pin interrupts with callbacks and timer interrupts are on the roadmap. This is usually sufficient for these types of systems. Since the Due supports hardware multi-threading, this is the architecture we would most likely have a chance at implementing a decent scheduler.Other items listed above that are on the roadmap include SPI, I2C, and CAN.
Providing a generic interface to libs is very tricky. At this time we will be manually adding support for libraries based on priority.
Thanks for the suggestions.
For the smaller Arduino's the timer interrupts option is a nice option to have small tasks beside the main loop. Combined with a case structure inside the timer interrupt, you can consider the Uno as a "serial interrupt based multi-tasking mainframe" 
.
For the Due (and other future platforms) a decent scheduler and multi-threading will make this Compiler a serious contender in the Arduino world.
The roadmap looks ok to me, perhaps the WatchDog is easy to include....? (first the other stuff)
About "interface to libs" ; what is the difficulty you face , and can we help to find solutions?
Regards,
John
8:10 pm
March 19, 2015
Offline
Interface to libs,
Perhaps something like Matlab Script node ?
7:15 pm
March 19, 2015
Offline
Steffan said
As far as multi-threading goes, since AVR does not support hardware multi-threading and is meant for simpler applications, it is best to treat these as single loop interrupt driven systems. We do support pin interrupts with callbacks and timer interrupts are on the roadmap. This is usually sufficient for these types of systems. Since the Due supports hardware multi-threading, this is the architecture we would most likely have a chance at implementing a decent scheduler.
The timer interrupts are a good "multi-threading" alternative for the Atmel AVR hardware.
Can we use the whole 32 bits usec range, from 1us to 4294.967295sec ?
Good job!
7:25 pm
March 12, 2015
Offline
Thats a good question and should have been specified in the documentation (will be added). The underlying library automatically adjusts the timer prescaler based on the input period. The minimum period or highest frequency this library supports is 1 microsecond or 1 MHz. The maximum period is 8388480 microseconds or about 8.3 seconds.
11:50 am
April 11, 2015
Offline
First of all, thanks for a really nice product!
In future versions I'd be happy to see support for clusters. I know the current reason for not supporting them is due to memory considerations, but I feel that it can't be impossible to solve, right?
I mean, I can certainly use structs in C /C++ on Arduino so with an efficient compiler that maps the cluster usage to similar constructs as in C the memory impact shouldn't be that large?
One more thing that I think would be very nice is to be able to debug my code. Without this possibility we would never be able to make any complex Arduino programs using LabVIEW.
I own an AVR Dragon that is capable of debugging the Arduino via debugwire if I'm developing C with the AVR toolchain. Wouldn't it be at least theoretically possible to extend the LabVIEW IDE and your compiler with the same ability?
/Leif
--- There are only 10 kinds of people in the world, those who understand binary and those who don't.---
9:36 am
April 21, 2015
Offline
Thank you for very nice product!
For now, my wish is Pro/ Pro mini 3.3V 8MHz support.
It will help to communicate with 3.3V I2C sensors.
2:47 pm
March 12, 2015
Offline
koji_ohashi said
Thank you for very nice product!
For now, my wish is Pro/ Pro mini 3.3V 8MHz support.
It will help to communicate with 3.3V I2C sensors.
Actually, this is already supported. Under the Tools>Board menu for the Pro Mini, there are 4 variants. The 8 Mhz variants are the 3.3V models.
12:14 am
April 21, 2015
Offline
Steffan said
koji_ohashi said
Thank you for very nice product!
For now, my wish is Pro/ Pro mini 3.3V 8MHz support.
It will help to communicate with 3.3V I2C sensors.Actually, this is already supported. Under the Tools>Board menu for the Pro Mini, there are 4 variants. The 8 Mhz variants are the 3.3V models.
Thanks.
It worked well on Pro Mini 3.3V 8MHz.
Also worked on the ATmega328 with bootloader(8MHz internal clock).
Great!
7:33 pm
March 19, 2015
Offline
Steffan said
Thats a good question and should have been specified in the documentation (will be added). The underlying library automatically adjusts the timer prescaler based on the input period. The minimum period or highest frequency this library supports is 1 microsecond or 1 MHz. The maximum period is 8388480 microseconds or about 8.3 seconds.
Steffan,
Inspired by the timer interrupt, i have made an example "task scheduler" that i want to share.
I wanted to open a new topic "Examples"but i realized that i could not upload a VI ?
What to do ?
Regards, John
7:36 pm
March 12, 2015
Offline
Thanks John. Thats a good point. Hang on to it, let me see if we can make it so the forum accepts non-image attachments. We can start a new thread once we figure that out. Thanks.
8:14 pm
April 27, 2015
Offline
What about supporting chipKIT WF32?
It is arduino compatible and has 80 MHz clock! I really would like to have a 80 Mhz resolution clock in my hands 
2
1 Guest(s)
