Re: SI message port: WIKI error?
Posted: Wed Apr 21, 2021 5:32 am
Hi Tony,
I fully understand what you are saying and you are absolutely correct. There is enough information there to cover the operation. I really DO appreciate the input and feedback from all.
It is so easy for me, normally' to use a serial print / serial monitor debug from the IDE when learning anything new such as the 'struc' within the context of Arduino. Obviously this is not easily done here without passing all the Arduino information that I want to look at back to the AM console. I would find it MUCH easier to have debug at each end due to the difference in syntax between Arduino and LUA. I am just so used to having the debug console available within arduino when working on something new. Old age and habit...
Anyway I had a brainwave last night (dangerous I know.... ) and thought - heck - why not just use an Arduino DUE !. It has 2 usb serial ports on board and in theory I can use one for Messageport and the other as a debug monitor for the arduino code - and of course, For LUA I have the console within AM.
This probably sounds, at first glance, more complex than piping it all back though the AM console but I have few DUE Arduinos sat on the bench and it it would seem to offer the best of both worlds - at first for the viewing of the breakdown of the structure that I want to understand in a more hands on way, and play around with various options for breaking down and using the data 'struct' data within the Arduino IDE. so.............. The big thing then is that It will also massively help in the development of the more complex actual full arduino code for the Arduino end hardware / final project for whatever use it will be put to. I can develop on the DUE with the serial monitor from the second port and then use a 2560 for the final project if the DUE is overkill as to all intents and purposes the DUE can be used as a pseudo MEGA 2560 and has the same footprint / pin compatibility.
Anyway. I will experiment over the next day or so and then hopefully contribute something back to the community.
I will also try to offer feedback on using the Arduino DUE as a debug method for Message Port based hardware Arduino code in general.
Huge thanks again to Jackz Corjan and your good self.
Joe
I fully understand what you are saying and you are absolutely correct. There is enough information there to cover the operation. I really DO appreciate the input and feedback from all.
It is so easy for me, normally' to use a serial print / serial monitor debug from the IDE when learning anything new such as the 'struc' within the context of Arduino. Obviously this is not easily done here without passing all the Arduino information that I want to look at back to the AM console. I would find it MUCH easier to have debug at each end due to the difference in syntax between Arduino and LUA. I am just so used to having the debug console available within arduino when working on something new. Old age and habit...
Anyway I had a brainwave last night (dangerous I know.... ) and thought - heck - why not just use an Arduino DUE !. It has 2 usb serial ports on board and in theory I can use one for Messageport and the other as a debug monitor for the arduino code - and of course, For LUA I have the console within AM.
This probably sounds, at first glance, more complex than piping it all back though the AM console but I have few DUE Arduinos sat on the bench and it it would seem to offer the best of both worlds - at first for the viewing of the breakdown of the structure that I want to understand in a more hands on way, and play around with various options for breaking down and using the data 'struct' data within the Arduino IDE. so.............. The big thing then is that It will also massively help in the development of the more complex actual full arduino code for the Arduino end hardware / final project for whatever use it will be put to. I can develop on the DUE with the serial monitor from the second port and then use a 2560 for the final project if the DUE is overkill as to all intents and purposes the DUE can be used as a pseudo MEGA 2560 and has the same footprint / pin compatibility.
Anyway. I will experiment over the next day or so and then hopefully contribute something back to the community.
I will also try to offer feedback on using the Arduino DUE as a debug method for Message Port based hardware Arduino code in general.
Huge thanks again to Jackz Corjan and your good self.
Joe