Davinci Jr Repetier Port (Page 4 of 9)

Also, wouldn't putting this unit into a RAMPS setup require mapping the pins anyway? You'd still need to have that data handy to effectively wire the opposite end of the ribbon cable and keep it clean.

Always nice to learn something new! I'm kinda glad I've started to dabble in the engineering end of this lump of crap known as the JR.

The existing panel will not work with a Ramps.  It uses a different communication protocol that the Ramps cannot provide. I was one of the first to convert my 1.0 to  Ramps and the LCD that comes with them. I just made an enclosure that mounted to the outside over where the stock display and buttons where.  I then bought the parts to make two 6 foot ten pin ribbon cables in order to connect the LCD to the Ramps mounted in the back where the stock board was. 6 feet is required for such routing similar to stock routing.

You will also nerd to buy three optical or mechanical endstops. The existing ones are not compatible with a Ramps as they do not have current limiting resistors installed. Those are on the stock mainboard as well.

No offense, but this is appearing to be beyond your understanding of electronics. On all circuit boards there is a power bus, ground bus , and other common busses. In many cases you could even have multiple grounds such as analog and digital which are actually different from each other. You can have multiple power busses such as +12VDC, -12VDC, +5VDC, -5VDC, +3.3Vdc. and so on. These will run to all devices that need those busses but it does not mean that device has any control of that bus. 

In your case those pins you are seeing are power and ground on all of the devices on that board. They are simply sharing those connections. They are not controlled by that Atmel chip that chip simply shares those busses with the other parts.

The only thing the Atmel chip does is it tells the controller in the printer that it is a printer head versus an engraving head versus a router head like the 3 in 1 would use. XYZ uses the same controller in all of their machines so this is how that controller can tell what kind of machine it is in and what functions it needs to support. It serves no other purpose or function.

That little board in the extruder serves no purpose except to be a pass through  from the ribbon cable to each connector for the fan, the heater, and the thermistor which is what you call the NTC. This type of connection system is more flexible and durable and it give them a place to solder and connect the filament sensor which is the device in the middle of the board.
There are only two active devices on that board. Those are the sensor and the Atmel chip. They do not talk to each other nor do they interact with or control anything else on that board. They only talk to the mainboard through the ribbon cable. The connections you marked for them are again just shared but not controlled busses.

To be blunt, ignore the Atmel chip. It serves no purpose on the model of printer you have. Yes it is connected as it is on all models. But it is not supported on your model and seves no purpose.

RepRap DuetWiFi and DuetEthernet use the same Atmel ATSAM4E8E chip, RepRapFirmware supporting RepRap DuetWiFi and DuetEthernet is open source
https://github.com/dc42/RepRapFirmware/ … rc/DuetNG/

Is there anything we can use to help such as bootloader or pin mapping?
https://github.com/arduino/ArduinoModul … /sam4e8e.h

Can we use this as IDE instead of Arduino 1.8.4 if the board support and bootloader is a problem?
http://www.visualmicro.com/page/Arduino … dio-7.aspx
Please install Visual Micro from within the Atmel Studio 7 IDE using "Tools>Extensions and Updates>Available Downloads>All"
A free Arduino extension for Atmel Studio. Arduino compatible build and Atmel Studio debugging. A paid version is available at low cost with many additional features.
Atmel Studio with Visual Micro offers Arduino compatible project build alongside hardware and simulated debuggers. Visual Micro ensures project codes stays cross-platform Arduino compatible and also allows the Atmel platform specific tools to be used when required.
Visual Micro in Atmel Studio works the same as it does in Visual Studio (apart from shared projects and editing of libraries) but also combines Atmel programming, debugging and simulators.
Using Atmel Studio Device Programming With Arduino Builds
Visual Micro, in Atmel Studio 7, provides an additional Arduino programmer called "Atmel Studio Device Programming".
Selecting this option will use the standard Atmel project configuration settings (instead of Arduino programmers or bootloader).

@yizhou.he

Sweet! I'll give this a try and see how it goes. It should help with starting the pin tracing at the least

Using Toshiba  TB62269FTG stepper driver (U10-U15)

NXP Cortex-M0 Microcontroller U17: LPC1115
^ I believe this is handling NFC as well as a couple of things on the print head.

I'm currently probing traces and keeping track on a google sheets spreadsheet: https://docs.google.com/spreadsheets/d/ … sp=sharing

I'll continue updating this sheet as I work. Pins highlighted in green have been traced from SAM to their destinations

Edit:
The FET controlling the heater is currently connected to a voltage comparator circuit (U9 LM2903 TSOP8)
Based on the pinout tracing I've done so far, it looks like the voltage comparator is being used as noted in the "Limit Comparator" Curcuit (replacing the Lamp with the heating element) and the input is coming from the Cortex-M0 microcontroller.

Too late, those pins were the first ones I traced. I'm making good progress on it though. It looks like there's going to be some complicated messiness involved because a good portion of the print head is managed by U17 (Cortex-M0 Micro) so we'll have to figure out how that's interfaced first.

I'm going for the functional pins before I start poking at the LCD stuff. I just figured out the interface to the M0 is over serial (using RXD/TXD on pins 46 and 47). Now working on tracing that back to the ATSAM.

The last two pins on J115 (unpopulated header) are also connected to the M0's serial pins, so I could hook up a header and try capturing some data off it

Found a few more of the IC's and pulling values and schematics for them now.

U21/22 are RT7248 DC step-down converters. Currently working out the voltage divider on those to see what they are supposed to put out

Edit: U21 puts out the board's +5V supply, while U22 puts out the board's +3.3V supply. Both are current limited to 2A each

If nothing else it could be used to sniff serial traffic between U2 and U17

for end stops we have them already if you check my post