rusefi.com

Posted: **Wed Feb 01, 2017 7:22 am**

argh. my bad! I thought it was 0805. Soldering 1206 instead of 0805 is a pain, at least on Frankenstein and at least for certain 1206s with smaller (narrower?) connectors.

Posted: **Wed Feb 01, 2017 7:30 am**

puff wrote:argh. my bad! I thought it was 0805. Soldering 1206 instead of 0805 is a pain, at least on Frankenstein and at least for certain 1206s with smaller (narrower?) connectors.

Ok i thought as much.

How about this http://www.digikey.com/product-detail/en/taiyo-yuden/TMK212BBJ106KGHT/587-4334-1-ND/5400908

TMK212BBJ106KGHT

Posted: **Wed Feb 01, 2017 11:06 am**

I see R0.5 has DIGI,490-3905-1-ND and I'm not quite sure what @russian gets populated on the assembled boards. It looks like I need to update the R0.4 BOM. I think the Chinese populate this cap, so it likely not the exact one in the BOM.

Can @russian confirm if the populated one use a 1206? Or do the populated ones use an 0805? However what I really care about, should I update the BOM to what is in R0.5?

Posted: **Wed Feb 01, 2017 12:53 pm**

kb1gtt wrote:I see R0.5 has DIGI,490-3905-1-ND and I'm not quite sure what @russian gets populated on the assembled boards. It looks like I need to update the R0.4 BOM. I think the Chinese populate this cap, so it likely not the exact one in the BOM.

Can @russian confirm if the populated one use a 1206? Or do the populated ones use an 0805? However what I really care about, should I update the BOM to what is in R0.5?

Chinese were the ones pointing at couple of these issues with wrong values or wrong packages

So we have fixed the BOM in the email with them and in 0.5 development.

Let's fix 0.4 BOM. I would not be overriding the PCB file - that I was to stay 100% as it was the moment we send to fab - but schematics and BOMs I will update.

Posted: **Wed Feb 01, 2017 5:17 pm**

Ah, are there other caps that might be of concern or other components? Do you want me to update the R0.4 BOM, or do you think I'm just a middle man on this one? I've got it on my radar to update the schematic symbol for the electrolyte / polarity thing. Not change to PCB layout, but schematic can change. If you change caps, I would want to update the schematic properties as well, such that if someone uses the schematic to make the BOM, they get a proper BOM.

Posted: **Wed Feb 01, 2017 5:49 pm**

I think only absolutely neccesary things should be touched on 0.4

Not pcb for sure
Probably not wrong symbol probably not the right scale

But BOM has caused enough pain to be fixed in the 0.4 folder

Posted: **Sat Feb 04, 2017 3:14 am**

Feedback from http://forums.turbobricks.com/showthread.php?p=5554425#post5554425

it's great that you're using a lightweight RTOS, especially for open source development with vastly different talent levels. But I gotta say that one of my pet peeves is schematics that use flying/hidden connections -- please take the time to draw every wire, and even list the connecting pages -- everyone, other than the original designer, will thank you for your efforts.

Posted: **Sat Feb 04, 2017 3:59 am**

I wish I knew a better way. I agree the schematics I make are not as easy to read as I wish they were. I pay very close attention to PCB current loops, and I start that with the schematic. Even worse is that I put the circuit layout as higher priority than the schematic, and even higher priority than the enclosure which will hold it. So as I get into the layout, I often will make a change in the schematic to make the layout net do what I want. After it's designed, I wish I could make a separate schematic which would be more signal flow related. If I could do this second schematic easily enough, I think it would make it much easier for people to diagnose. Right now we have a designers schematic, what we need is a diagnostics schematic.

Posted: **Sat Feb 04, 2017 12:56 pm**

getting this feedback again and again from the Subaru side of the fence so

131) between items #111, #127 and #128 we should keep stepper motor in mind and ideally have a space to mount it with minimal wiring

Posted: **Mon Feb 06, 2017 7:03 pm**

As long as the silkscreening is legible any color is fine.
The silkscreening on the frankenso 0.4 board isnt the easiest to read.

Posted: **Mon Feb 06, 2017 8:17 pm**

I have seen a Frankenso R0.2 and R0.3 board, but have not seen the R0.4. I believe the silk screen is basically the same for all three boards. This might seem odd, but I haven't seen a R0.4. I'm kind of proud that so many people have made good use of the R0.4 with out me touching it. Any how, can you elaborate about why it's hard to read? Do you mean contrast, size of text, other? On the R0.2 If possible I might be able to help resolve silk screen issues on future spins.

Posted: **Mon Feb 06, 2017 8:21 pm**

The size is ok but the font is not crisp. There are many misprints (portions of characters missing).

I'd have to compare it to an inkjet printer running low on ink and having some clogged nozzles.

Posted: **Mon Feb 06, 2017 8:40 pm**

Let's take examples from http://rusefi.com/images/Frankenso/ to the Frankenso topic. I will move existing posts, please continue there

Posted: **Mon Feb 06, 2017 8:42 pm**

kb1gtt wrote:I have seen a Frankenso R0.2 and R0.3 board, but have not seen the R0.4

Well, you were investigating the one with exploded hip9011 chip? It was a 0.4

Posted: **Mon Feb 06, 2017 9:51 pm**

Ah, I did see an R0.4 for something like a week.

Posted: **Sun Feb 12, 2017 10:06 am**

russian wrote:getting this feedback again and again from the Subaru side of the fence so
131) between items #111, #127 and #128 we should keep stepper motor in mind and ideally have a space to mount it with minimal wiring

I just did the below line item, I think this is the same as your suggested 131). Let me know if 131 includes something different.

Code: Select all

93) RESOLVED IN R0.5 added pololu DRV8880 and A4988 stepper driver Perhaps should be an add-on board.

Posted: **Mon Feb 13, 2017 12:48 am**

Have not looked at the changes yet but here's another one sorry:

132) Add vias to PE5 & PE6 traces (these are input capture options on TIM9)

Posted: **Mon Feb 13, 2017 1:06 am**

132 done

Posted: **Mon Feb 13, 2017 6:35 am**

kb1gtt wrote:
russian wrote:getting this feedback again and again from the Subaru side of the fence so
131) between items #111, #127 and #128 we should keep stepper motor in mind and ideally have a space to mount it with minimal wiring
I just did the below line item, I think this is the same as your suggested 131). Let me know if 131 includes something different.
Code: Select all
93) RESOLVED IN R0.5 added pololu DRV8880 and A4988 stepper driver Perhaps should be an add-on board. 

Great!
I've modified a bit this part of PCB. I think such traces layout would be better.
Another question. How can we connect 1A,1B,2A,2B from DRV8880 with main connector? Can we do it on internal layers?

Posted: **Mon Feb 13, 2017 10:41 am**

I was keeping the higher frequency digital signal bundled together, but your right, those 2 traces can be moved with out causing any real issues. So I moved them and got the 12V supply completely on an external layer.

Routing on internal layers should be avoided if possible. The power and ground planes have many current loops, adding breaks or barriers in these flood planes forces currents loops to get larger which causes noise issues. Currently there are no signal traces on the GND layer. The below are the breaks in the power plane.

: Capture.PNG (15.13 KiB) Viewed 21973 times

Notice the breaks are far away from the power supply, and they are as short as possible. The longer traces are at the edge of the board where the power supply current loops are not likely. I do not like having these breaks, but in that area those are digital signals which can commonly functional survive this kind of layout.

Long breaks near the analog components would very likely cause noise issues for everyone, just so the stepper folks can have a more pretty board. Hmmm, perhaps an L shaped add-on board could be used which would rest on top of the hi/lo drivers. This might be handy as it could also function as a heat sink for the hi/lo's which would be good for helping to keep them cool. Either that or a bunch of jumper wires could be added for folks who need to put something there. After all they are probably going to be adding trurbo's, or other random stuff. So they are probably going be adding a bunch of jumper wires any how.

Posted: **Fri Mar 17, 2017 8:27 pm**

135) CANH silkscreen position is wrong

CANL silkscreen is fine, CANH is not

Posted: **Fri Mar 24, 2017 3:14 am**

Biggest rusEfi order so far

Posted: **Fri Mar 24, 2017 12:34 pm**

russian wrote:Biggest rusEfi order so far

Uuuuu sexy ...

Posted: **Fri Mar 24, 2017 12:35 pm**

Abricos wrote:Uuuuu sexy ...

I am now looking at these pictures. Between these two button holes and the little brain USB hole we need to make a smily-face I think.

Posted: **Fri Mar 24, 2017 4:08 pm**

I think we are already there with this one. One blue eye one black eye, funky mouth. Perhaps it needs a circle to show the face outline.

Posted: **Fri Apr 14, 2017 11:51 pm**

Courtesy of @ https://www.micron.com/products/managed-nand/emmc/automotive-emmc#/ SD-card replacement but it's always BGA

Posted: **Sat Apr 15, 2017 1:12 am**

I highly sugges to look at quadspi flashes. Current chip does not support qspi. But some of stm32f4-series support. All of STM32F7 support. One more reason to look closely to stm32f7**.

Profit:
SO8 package
direct memory maping (up to 256M) - so maps can be moved here.
4 pins only (eMMC usualy 8 + 1)
quite fast

http://www.st.com/content/ccc/resource/technical/document/application_note/group0/b0/7e/46/a8/5e/c1/48/01/DM00227538/files/DM00227538.pdf/jcr:content/translations/en.DM00227538.pdf

Posted: **Sat Apr 15, 2017 4:43 am**

STM32F7x5 and STM32F7x6 I want 2 ...

Posted: **Sat Apr 15, 2017 8:48 pm**

Just added http://rusefi.com/wiki/index.php?title=Manual:Current_Status#FAQ hopefully I did not miss any major rusEfi limitations?

Posted: **Fri Apr 21, 2017 12:29 am**

Code: Select all

139)                  add an app note regarding not having separate injector/analog/else GND on Frankenso

rusefi.com

Frankenso - ECU shield compatible with OEM case / official

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: stm32f4 MPU module LQFP 100

Re: stm32f4 MPU module LQFP 100

Re: stm32f4 MPU module LQFP 100

Re: stm32f4 MPU module LQFP 100

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case

Re: Frankenso - ECU shield compatible with OEM case