Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

Redacted 00101100


  • Please log in to reply
126 replies to this topic

#121 Cuno

Cuno

    Advanced Member

  • Members
  • PipPipPip
  • 144 posts
  • LocationZrich / Switzerland

Posted 04 April 2012 - 07:29 PM

http://nwazet.com/product/module

Fabien,

very interesting product!

If I understand correctly, your touch display has its own microcontroller, between the display and the Netduino Go. Is the "SPI up to 40 MHz" between display and your microcontroller?

What exactly is the higher-level protocol on top of go!bus, between Netduino Go and your display module? Are the drawing primitives related to common .NET abstractions?

Could your display be used from a Gadgeteer mainboard as well, let's say through an SUX socket?

Thanks and looking forward to seeing the display in natura!

Cuno

#122 Bertrand Le Roy

Bertrand Le Roy

    New Member

  • Members
  • Pip
  • 7 posts

Posted 04 April 2012 - 09:15 PM

What exactly is the higher-level protocol on top of go!bus, between Netduino Go and your display module? Are the drawing primitives related to common .NET abstractions?


Rendering commands from your .NET code on the Go are serialized and sent over the wire, then deserialized by the screen's controller and executed there. The screen itself is running those commands in native code. The API is a canvas-like vector graphics API. It will evolve in the future but already has some interesting features. You'll see a lot of activity from us just around the screen. We have surprises in stock. :)

#123 Fabien Royer

Fabien Royer

    Advanced Member

  • Members
  • PipPipPip
  • 406 posts
  • LocationRedmond, WA

Posted 04 April 2012 - 10:07 PM

Hi Cuno,

I'm going to expand on what Bertrand wrote a bit and take your questions one by one :)

If I understand correctly, your touch display has its own microcontroller, between the display and the Netduino Go. Is the "SPI up to 40 MHz" between display and your microcontroller?



That's correct: the display has its own STM32F2, servicing commands from the application running on the GO! mainboard received / sent over SPI. In turn, the display module drives the actual LCD screen and handles the interactions with the touchscreen.

What exactly is the higher-level protocol on top of go!bus, between Netduino Go and your display module? Are the drawing primitives related to common .NET abstractions?



I wrote a generic lightweight message serialization / deserialization system for passing messages / objects (in network byte order) between a C# app and the C code (and vice-versa) interpreting the commands. The buffer containing the serialized messages is used by SPI directly.


Could your display be used from a Gadgeteer mainboard as well, let's say through an SUX socket?



Yes, it should work just fine.

Thanks and looking forward to seeing the display in natura!


Thanks,

Cheers,
-Fabien.

#124 Terry Massey

Terry Massey

    Advanced Member

  • Members
  • PipPipPip
  • 77 posts
  • LocationPekin, IL

Posted 04 April 2012 - 10:13 PM

From the specs page:

"
all 8 sockets: go!bus modules
up to 2 sockets: Gadgeteer S-U-X
"

So it looks like there is some gadgeteer compatibility, right?


Any one else think maybe the S-U-X was on purpose???
Thanks,
Terry Massey

#125 Cuno

Cuno

    Advanced Member

  • Members
  • PipPipPip
  • 144 posts
  • LocationZrich / Switzerland

Posted 04 April 2012 - 10:36 PM

Hi Cuno,

I'm going to expand on what Bertrand wrote a bit and take your questions one by one :)

...

Thanks! More and more interesting...

#126 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 05 April 2012 - 01:26 AM

Hi Terry,

Any one else think maybe the S-U-X was on purpose???

It's an unfortunate consequence of an otherwise technical naming scheme. This was the Gadgeteer socket type which fit go!bus pin requirements. Hopefully those who have Gadgeteer modules find the compatibility mode useful.

Chris

#127 carb

carb

    Advanced Member

  • Members
  • PipPipPip
  • 352 posts
  • LocationCrystal River, Florida

Posted 06 April 2012 - 09:12 PM

Darn the bad luck, I got the only UPS driver in the state of Florida that has never gotten a speeding ticket. It is after 5:00 pm and still no Netduino Go!.

At least at this speed it should get here safe. Poor thing has been in the truck since 6:28 am this morning.

In-Patiently waiting,
Chuck




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.