Ct Shield V2.0
Bok Mull
If you get an "Arduino MEGA Sensor Shield v2.0" board in a Starter Kit from China, be aware that there might be a missing connection (either that or my board doesn't have proper plated-through holes and a connection on the other side of the board on that line).
However, at least on my board, between signal 35 and 36 on the V (5 Volt) row, there is NO CONNECTION. This means that the logic of having 5V on the middle pin is lost for signal pins 36 - 45 and the middle V pin will float.
Second, big, problem (that is well documented on the internet) is the 'USB Connector Shield shorts-out with one pin of the 2 pin PWR_SEL jumper. Ouch and dangerous. The first time I plugged the board in I got no LED and wondered what was happening. I was holding the board and felt intense heat. It was shorting the power supply completely.
It is easily rectified, however. Just snip off both of the PWR_SEL pins as close to the board as possible and sand down the pin closest to the edge with a Dremel tool and 2-seconds of contact or sandpaper used gingerly.
Then place a square of good-quality (3M Temflex 1700C, or equivalent) electrical tape, carefully cut and wrapped snugly around the USB connector. Then place a tiny 1/4" x 1/4" tape on the circuit board over that pin.
I believe that that board is now up to version 2.4; so they probably got rid of those problems in the newer version boards (hopefully); but for those who are still getting Starter kits from China, their old stock will probably last quite some time.
I suspect that many different manufacturers (Bangood, SainSmart, Mausan, HiLetGo, etc.) are all copying each other on this board; so most probably don't exhibit these problems. It should be pretty simple to determine whether you have this board. Just look to see if pin 45 is labeled correctly on the PC Board Silkscreen. If it is labeled 44, you have a board which might exhibit these problems.
Just plug in your Breakout board, and before you plug in either the USB cord or power cord ensure that the pin doesn't touch the shield. Second, take a continuity reading between pins 35 and 36 on the V line to ensure they join. Since these guys copy each other's boards... I wouldn't put it past them to have the same problem exhibit on all v2.0 boards.
I know this has been inactive for a while, but I've got a quick question I thought you might be able to help with: I'm using the same sensor shield (says "Arduino MEGA sensor shield v2.0"), and my code has recently begun to malfunction after I unplug the USB cable from my PC.
I'm not sure what "USB Connector Shield shorts-out with one pin of the 2 pin PWR_SEL jumper" means exactly, but I've lifted the board up enough that there isn't anything touching the top of the USB jumper (if that is what it means). Do you think the shorting has anything to do with this?
Hard to say if mega chip is damaged but I think no. Does this problem repeat without sensor shield? You should use tape over usb chase three times. These pins on the back are still sharp and it drills the tape. Try to cut these pins on the back shorter.
This thread is still relevant to anyone ordering from China on Aliexpress! for AUD$3.55 and shipping shared with other cool boards, worth it, even with needing to solder a bridge in, and insulate the USB-B header from the power selector.
Hi.
I just bought a CAN bus shield v2.0. The instruction manual clearly explains how to connect two CAN nodes, but I need to have 3 nodes in my setup and I am wondering if I need to add resistors manually. A CAN bus requires 120 Ohm termination resistors at each end of the bus. Do Seeed-studio CAN bus shields have built in termination resistors? What about connecting my setup to an existing CAN bus, e.g. a real car CAN bus, that already has termination resistors?
I would appreciate if someone shed some light on the matter.
//Nasser
TFT Touch Shield V2.0 is a resistive touch screen, compatible with Arduino/Seeeduino/Arduino Mega/SAMD21 platforms. It can be used as display device or sketch pad. Compared with the previous version, 2.8''TFT Touch Shield V1.0, we upgraded the screen driver to a more professional chip, ILI9341 driver, providing different pin-saving SPI communication without sacrificing the data transmitting speed. Due to the communication method change, programs developed for the original version are needed for modification before being transplanted to the new version. With a SD card module integrated on this shield, this shield reserves capability for other expansions of your project.
Click to download the Touch Screen Driverthen please click on below button to download the library and install it, if you don't know how to install an Arduino library, please refer to the tutorial (HOW TO INSTALL AN ARDUINO LIBRARY).
The backlight is always default on, if you want to change the backlight, you need to do some hacking on the board. Please look at the back side of the board. There's a BACKLIGHT label. One side is named as ON, and the other side is named D7. We need to cut the wire between middle pad and ON pad, solder middle pad with D7 pad. As shown below.
Thank you for choosing our products! We are here to provide you with different support to ensure that your experience with our products is as smooth as possible. We offer several communication channels to cater to different preferences and needs.
So I came with the idea of making it by myself and share it for fritzing (since I liked it). Using some templates from fritzing along with some part of v2.4 svg, I finished the breadboard for the v2.0.
It is usually best to upload the .fzpz file (obtained by exporting the created part). That is really a zip file that contains all the svgs and the fzp file that defines the part. The upload button is the 7th icon from the left on the reply menu. To upload an svg file it is usually best to rename it to .fzpz and tell us it is really a svg as the forum sometimes has trouble rendering svg files (which is what it tries to do with them). Given the fzpz file I or someone else will point out problems and how to fix them. There is also a python part checking script available on github (although I need to do some updating of it when I get time) that will point out some issues that it can find.
Yeah, I noticed something like that while looking for the .svg files and .fzb of arduino mega 2560 rev3 part. They defined every pin used on the connectors tab and assigned the pin based on that. Looks like a ton of work for me
It is true that I do use the editor exclusively but it is also true that I do not use Breadboard at all and I never do modules either. The only thing I make is parts for making PCBs. This means when I do it I usually start with a generic part or a mystery part and only change the PCB svg and assign its pins. So the BB svg and SCH svg already have all their pins assigned and I only have to assign the PCB pins.
Hi mate, nice to hear that, the arduino mega shield v2.4 you designed was pretty good indeed. I tried to use it for the v2.0 one since it has similarities regarding header layout but I switched to fritzing arduino mega in order to make it fit correctly.
Okay, has been some time since I did some work for this part but I spent half day doing a lot of fixes based on the original Arduino mega board file. Basically, updated the header positioning on breadboard and pcb view and added the connector ids using Atom Editor which helped me a lot due to features like Find and replace using RegEx (and selecting all results with Alt + Enter), Sequential number package and beautifiers. The same stuff was used for all internal connection in BB view.
The CAN-BUS arduino shield v2.0 is designed for the Arduino Microcontroller. It is compatible with the Arduino standard interface and can be stacked on an Arduino UNO, arduino Leonardo or arduino MEGA board. The shield integrates an MCP2515 CAN-BUS chip on the shield and has a CAN-BUS transceiver function. With an on-board DB9 and CAN-BUS connector you can choose a suitable port according to your host device. There is also an integrated MicroSD socket for data storage - a perfect solution for data logging applications.
1. CAN-BUS Node (Device) What is CAN-BUS Node? The CAN-bus is a local area network control protocol. In a local area network there are multiple devices connected. Each device is called "Node". There is a CAN-bus protocol controller on each node (control chip). Refer to CAN-BUS WIKIPEDIA
The following is a simple scenario to demonstrate how it works: There are 5 nodes in the network; A, B, C, D and E. If Node B can only receive data from ID 0x06, when Node A wants to send "Hello world" to Node B, you can call sendMsgBuf(0x06, 0, 12, "hello world") function to implement this process. Meanwhile, what about the other nodes circumstance?
In this section we will demonstrate basic CAN BUS receiving and sending functions. Receiving uses polling mode. You can accept any ID standard data frame or extended frame. The transmitting node sends a standard data frame which ID is 0x06 per 100ms.
Receiver: output in the serial port
The received data frame has no data from ID 0x06,0x00,0x01 or 0x02 which not matched with the ID which is set by Data acceptance filter. This shows that the filter can be a single job, or a few filters working at the same time, or all of the filters working at the same time. When all filters are not in use then can receive any data.