Log In
Register
Forum
Topic RSS
2:21 am
September 24, 2015
Offline
In working toward the Master/Slave loop-back code, I’m getting an compile error from slave code (attached) to service a simple request for a fixed message (code attached). What am I missing here?
Jim
3:08 am
March 12, 2015
Offline
I didn't look at your code (I dont have LV2015 setup yet on a VM), but from the error Im guessing you have an input (control) wired to the connector pane of the Callback where it shouldn't. Take a look at the context help. It says the callback VI should not take in any parameters (unlike Attach Receive Interrupt). This is in line with the Arduino function call here.
4:43 pm
September 24, 2015
Offline
I followed the context help for the I2C Attach Request Interrupt VI: nothing attached to the connector pane (no controls or indicators in the callback code to attach).
The code was saved for 2014; reattaching those 2014 versions just in case.
Jim
4:17 am
March 12, 2015
Offline
Thanks Jim.
I looked into this one and it appears there is an issue in how the Attach Request Interrupt is interpreted. I created Issue #126 for this. It may be a few weeks before another release. There may be a workaround through the use of a user library in the meantime to implement the callback handling properly. If I have some time in the next few days I will see if I can try it out and can send it to you if it works.
4:13 pm
September 24, 2015
Offline
I’d say don’t worry about it Steffan … the loop-back work was to get ready for reading the BME280. The master code seems to be working as it runs and reads (trash, since the slave is not running). I’ll modify it to address the registers and try reading from the ‘real’ board.
Unless you find something you want me to try, I’m happy waiting for the fix in the next release.
Jim
4:50 pm
March 12, 2015
Offline
Ah ok. Sorry for the inconvenience. Go ahead and give the real board a try. The master side should work as we have many working projects based off master I2C comm. Well have the slave interrupts fixed in the next release. Thanks for bringing this to our attention.
21
1 Guest(s)
