convert some links using script, and fix some manually

This commit is contained in:
David Holdeman 2022-01-24 17:40:21 -06:00
parent 627acd18b8
commit 28390471e6
20 changed files with 40 additions and 40 deletions

View File

@ -1 +1 @@
Hello https://github.com/mck1117/atlas
Hello [https://github.com/mck1117/atlas](https://github.com/mck1117/atlas)

View File

@ -4,7 +4,7 @@
* Please do not push dead code
We make with -std=c++11 see https://github.com/rusefi/rusefi/blob/master/firmware/Makefile
We make with -std=c++11 see [the Makefile](https://github.com/rusefi/rusefi/blob/master/firmware/Makefile)
## Brackets

View File

@ -34,7 +34,7 @@
|chart|1|
|chartsize|1|Sets the size of engine sniffing buffer in ECU. Nothing would change on your screen until a new larger packet of engine sniffing would arrive from ECU.|
|get date|0 |Gets current real time clock|
|set date XXX|1|XXX is time in seconds sins Unix epoch - see http://www.epochconverter.com|
|set date XXX|1|XXX is time in seconds sins Unix epoch - see [EpochConverter](http://www.epochconverter.com)|
|echo|1|Just prints out the parameter - this is useful for troubleshooting connectivity|
|fatal|0 |This command would cause the firmware to halt. I am not sure that you want to try this one :)|
|fadc|0|

View File

@ -9,8 +9,8 @@ suggestions on how to design and work with things like a PCB layout.
## Basic principles
We are developing hardware using [KiCad EDA Suite](http://www.kicad-pcb.org/)
Our file repository for hardware is https://github.com/rusefi/rusefi/tree/master/hardware
For now we are developing hardware as individual functional modules. While all individual modules are in-depended from each over, the use the share the same component library which is located at https://github.com/rusefi/kicad-libraries
Our file repository for hardware is [here](https://github.com/rusefi/rusefi/tree/master/hardware)
For now we are developing hardware as individual functional modules. While all individual modules are in-depended from each over, the use the share the same component library which is located at [https://github.com/rusefi/kicad-libraries](https://github.com/rusefi/kicad-libraries)
## Collaboration process
Since patch files do not work well for hardware projects, our collaboration process is pulling whole folders from the SVN where board author would develop them into the central SVN which is the unified repository. That's a poor man workaround over the lack of free SVN hosting with directory user permissions.

View File

@ -4,7 +4,7 @@ We love our engines and we want them to live a long & happy life. That's why we
* built-in trigger signal simulation
* [Simulator](Virtual-simulator)
For current coverage report see https://rusefi.com/docs/unit_tests_coverage/
For current coverage report see [the coverage page](https://rusefi.com/docs/unit_tests_coverage/)
## Hardware Continuous Integration
@ -13,7 +13,7 @@ Since 2015 there is always a stm32f4 board listening for VCS updates running rus
Anyone can execute real hardware test suite by invoking. This command would detect rusEFI hardware automatically and invoke
https://github.com/rusefi/rusefi/blob/master/java_console/autotest/src/com/rusefi/RealHwTest.java
[broken link](https://github.com/rusefi/rusefi/blob/master/java_console/autotest/src/com/rusefi/RealHwTest.java)
``java -jar rusefi_console.jar functional_test``

View File

@ -25,7 +25,7 @@ Tunerstudio output channels are handled completely manually, as opposed to setti
Adding channels to tunerstudio_outputs.h induces offsets which are kept track of in comments next to each channel.
In the OutputChannels section of rusefi.input, these values are 3rd token in the configuration string.
http://www.tunerstudio.com/index.php/manuals/63-changing-gauge-limits
[Changing gauge limits](http://www.tunerstudio.com/index.php/manuals/63-changing-gauge-limits)
in order to use CONFIG macro you need EXTERN_CONFIG and include engine_configuration.h
@ -59,11 +59,11 @@ sharedLogger is a generally available logger object, which is passed (by referen
### Discovery pinout with usable pins
https://docs.google.com/spreadsheets/d/1pnU3Migcc7JEezvpVt3TcVCbuE5dIXXwrYFGZI97GNM/edit#gid=0
[stm32f4 discovery pinout with functions](https://docs.google.com/spreadsheets/d/1pnU3Migcc7JEezvpVt3TcVCbuE5dIXXwrYFGZI97GNM/edit#gid=0)
### Debugging
http://www.openocd.org/doc/html/GDB-and-OpenOCD.html
[GDB and OpenOCD](http://www.openocd.org/doc/html/GDB-and-OpenOCD.html)
Using openocd and gdb on STM32F407G-DISC1 requires modifying stm32f4discovery.cfg to source stmlink-v2-1.cfg

View File

@ -1,21 +1,21 @@
* As on Jan 2016 we are still migrating from KiCad version 2013-07-07 BZR 4022 to KiCad 4.0.1+ libraries etc. If it doesn't open well in 4.01, try BZR 4022.
* Current versions of boards are published in individual subfolders of https://github.com/rusefi/rusefi/tree/master/hardware
Some latest modular boards now live at separate repositories like https://github.com/rusefi/hw_modular and https://github.com/rusefi/hw_microRusEfi
* Current versions of boards are published in individual subfolders of [https://github.com/rusefi/rusefi/tree/master/hardware](https://github.com/rusefi/rusefi/tree/master/hardware)
Some latest modular boards now live at separate repositories like [https://github.com/rusefi/hw_modular](https://github.com/rusefi/hw_modular) and [https://github.com/rusefi/hw_microRusEfi](https://github.com/rusefi/hw_microRusEfi)
* We are trying to reuse common libraries at https://github.com/rusefi/kicad-libraries - so, there could be relative path to libraries and make sure you've downloaded submodules.
* We are trying to reuse common libraries at [https://github.com/rusefi/kicad-libraries](https://github.com/rusefi/kicad-libraries) - so, there could be relative path to libraries and make sure you've downloaded submodules.
* Silk screen should include board revision space permitting.
* Silk screen should include header information when possible, things like PA1, or PE4. Resistors and caps should be ref designators and a revision level. Of course a URL for more information and using the free bill boards is suggested.
* Prefer 0805 packages over 0603 and 1206 packages. 0603 is small and kind of hard to handle, 1205 has about a 50% failure rate when thermally stressed over an industrial temperature range. 0805 is as large as you can go with out getting into potential thermal expansion issues.
* We are targeting at DIY so BGA package is not an option.
* 1oz copper suggested
* Trace/via temperature rise should be 10C or less. That's based on UL 105C max while MFG's often allow up to 150C, and UL's 130C max solder joints. We are allowing for 95C board temps to dump to a +85C ambient. It is common a PCB has a rated temperature up to 125C, you need to check the substrate's datasheet. Look for peel strength, and Glass Transition (Tg) temperatures. When in doubt, typically 105C is a safe max temperature.
* Thermal relief's as noted here https://web.pa.msu.edu/hep/atlas/l1calo/hub/hardware/components/power/synqor_thermal_relief_study.pdf Archive [here](PDFs/Synqor_thermal_relief_study.pdf)
* Thermal relief's as noted [here](https://web.pa.msu.edu/hep/atlas/l1calo/hub/hardware/components/power/synqor_thermal_relief_study.pdf) Archive [here](PDFs/Synqor_thermal_relief_study.pdf)
* Suggested to use 12/12 traces and setback's such that low cost MFG houses can produce quality product. This can not always be followed, especially when you have a chip with 7 mil spacing, but if you try to follow this 12/12 rule, you'll get a higher yield from your PCB's. Even an 8/8 house can have issues as 8/8 is X/Y, a 45 degree angled traces would have a tolerance of √(8² + 8²)= 11.3, which rounds up to 12 mil. Most PCB layout programs will keep your angled setbacks at 8 mill instead of 12 mil. So you should set your setbacks to 12 to prevent MFG issues.
* Test points are suggest as a way to diagnose various potential issues.
* Any signal of about 1kHz or higher, will have GND currents that try to follow the adjacent trace. Use this practice to follow current loops and to prevent signals from coupling.
* GND plane should not have physical barriers, signals and chips should be routed accordingly such that they do not cross naturally. GND plane barriers are almost never needed unless you get into RF circuits with strip line requirements. Which is not very likely with an automotive PCB. See this Maxim tutorial http://www.maximintegrated.com/en/app-notes/index.mvp/id/5450 archived copy [here](PDFs/Successful_PCB_Grounding_with_Mixed-Signal_Chips_-_Follow_the_Path_of_Least_Impedance_-_Tutorial_-_Maxim.pdf)
* GND plane should not have physical barriers, signals and chips should be routed accordingly such that they do not cross naturally. GND plane barriers are almost never needed unless you get into RF circuits with strip line requirements. Which is not very likely with an automotive PCB. See [this Maxim tutorial](http://www.maximintegrated.com/en/app-notes/index.mvp/id/5450) archived copy [here](PDFs/Successful_PCB_Grounding_with_Mixed-Signal_Chips_-_Follow_the_Path_of_Least_Impedance_-_Tutorial_-_Maxim.pdf)
* Name caps with pF and uF, avoid nF. Also include leading 0's. Example, 0.1uf instead of 100nF or .1uF. Also 2.2uF instead of 2u2F. Also 2.2k instead of 2k2. Naming conventions are important as scripts need this kind of consistency.
* Ideally components available at both http://digikey.com/ and http://www.mouser.com/ should be used
* Ideally components available at both [DigiKey](http://digikey.com/) and [Mouser](http://www.mouser.com/) should be used
* Via sizing for via's to contain a wire, if solid should 10% larger than the diameter. As well stranded wire takes a larger diameter than solid. Use the below chart to approximate the stranded diameter, then add at least 10%. For example 20AWG wire, per that chart has a max diameter of 0.037in, 10% is 0.0037, and via plating is about 0.001, which means we need a min via drill diameter of 0.037in + 0.0037 + 0.001 + 0.001 = 0.0427 in diameter. [Stranded Wire Chart](PDFs/Stranded_Wire_Chart.pdf)
* High speed stuff like USB should follow Intel's recommendations found in [hs_usb_pdg_r1_0.pdf](PDFs/Hs_usb_pdg_r1_0_zjnjtx.pdf) also [this guide](PDFs/Power_delivery_motherboards.pdf) for the power signals.

View File

@ -10,23 +10,23 @@ Test mule #1 2004 760 AndreyB
Test mule #2 2006 760 Zeiss HeinrichG
Recordings of both buses by Zeiss HeinrichG https://github.com/HeinrichG-V12/E65_ReverseEngineering - see [E65 CAN](https://wiki.rusefi.com/E65-CAN-bus/) for description
Recordings of both buses by Zeiss HeinrichG [here](https://github.com/HeinrichG-V12/E65_ReverseEngineering) - see [E65 CAN](https://wiki.rusefi.com/E65-CAN-bus/) for description
Some packets with formats E90 https://www.loopybunny.co.uk/CarPC/k_can.html
Some packets with formats E90 [here](https://www.loopybunny.co.uk/CarPC/k_can.html)
Need to decode message format: Smaller list of names in English https://www.m5board.com/threads/lets-talk-dct-conversion.461873/page-21#post-7596717
Need to decode message format: Smaller list of names in English [here](https://www.m5board.com/threads/lets-talk-dct-conversion.461873/page-21#post-7596717)
Need to decode message format: Huge list in German https://www.bimmerforums.com/forum/showthread.php?2298830-E90-Can-bus-project-%28E60-E65-E87-%29&p=29628499#post29628499
Need to decode message format: Huge list in German [here](https://www.bimmerforums.com/forum/showthread.php?2298830-E90-Can-bus-project-%28E60-E65-E87-%29&p=29628499#post29628499)
https://github.com/damienmaguire/BMW-E65-CANBUS
[BMW E65 CANBUS](https://github.com/damienmaguire/BMW-E65-CANBUS)
E90 https://www.bimmerforums.com/forum/showthread.php?2298830-E90-Can-bus-project-(E60-E65-E87-)
[E90](https://www.bimmerforums.com/forum/showthread.php?2298830-E90-Can-bus-project-(E60-E65-E87-))

View File

@ -15,7 +15,7 @@ step 4) ``stm32-flash-dfu.bat``
# Old way - GUI application via DFU or SWD
TODO: try https://github.com/danielinux/stm32f7-dualbank-tool
TODO: try [https://github.com/danielinux/stm32f7-dualbank-tool](https://github.com/danielinux/stm32f7-dualbank-tool)
At the moment we only know how to deal with it via Stm32CubeProgrammer
@ -24,4 +24,4 @@ At the moment we only know how to deal with it via Stm32CubeProgrammer
![x](HOWTO/nDBANK/stm32prog-result.png)
https://github.com/rusefi/rusefi_external_utils/ has a backup copy of en.stm32cubeprg-win64_v2-7-0.zip
[https://github.com/rusefi/rusefi_external_utils/](https://github.com/rusefi/rusefi_external_utils/) has a backup copy of en.stm32cubeprg-win64_v2-7-0.zip

View File

@ -1,4 +1,4 @@
https://en.wikipedia.org/wiki/Honda_Element
[Wikipedia - Honda Element](https://en.wikipedia.org/wiki/Honda_Element)
# 2003 K24A4

View File

@ -1,10 +1,10 @@
https://rusefi.com/forum runs with a number of plug-ins:
[https://rusefi.com/forum](https://rusefi.com/forum) runs with a number of plug-ins:
* Button menu
* Clipboard Image
* Quick Title Edition deprecated or not supported? https://www.phpbb.com/customise/db/mod/qte/
* Quick Title Edition deprecated or not supported? [https://www.phpbb.com/customise/db/mod/qte/](https://www.phpbb.com/customise/db/mod/qte/)
Random Notes
Disable Signature for new members
https://www.phpbb.com/community/viewtopic.php?p=12821097#p12821097
[New Register User Signature Disable](https://www.phpbb.com/community/viewtopic.php?p=12821097#p12821097)

View File

@ -1,7 +1,7 @@
0280002565 w124 m119 e420 1994-1995
https://en.wikipedia.org/wiki/Mercedes-Benz_M119_engine
[Wikipedia - Mercedes-Benz M119 Engine](https://en.wikipedia.org/wiki/Mercedes-Benz_M119_engine)
Same case?

View File

@ -1,4 +1,4 @@
4.2L https://en.wikipedia.org/wiki/Ferrari_F136_engine V8
4.2L [Ferrari F136 Engine - Wikipedia](https://en.wikipedia.org/wiki/Ferrari_F136_engine) V8
2006 MASERATI QUATTROPORTE 4.2
2009 05 06 07 08 Ferrari F430
@ -8,4 +8,4 @@ Maserati GranTurismo
4.7 is a different story https://www.youtube.com/watch?v=WyWRyvbx4aU
4.7 is a different story [Maserati Granturismo ECU/ECM Engine computer removal](https://www.youtube.com/watch?v=WyWRyvbx4aU)

View File

@ -1,3 +1,3 @@
https://github.com/rusefi/proteus-80-pin-vag-adapter
[Proetus 80 pin VAG adapter](https://github.com/rusefi/proteus-80-pin-vag-adapter)
[Proteus Manual](Proteus-Manual)

View File

@ -2,4 +2,4 @@
[SpringRC SM-S4303R Continuous Rotation Servo](https://www.pololu.com/product/1248)
See also https://rusefi.com/forum/viewtopic.php?f=4&t=775
See also [rusEFI Display](https://rusefi.com/forum/viewtopic.php?f=4&t=775)

View File

@ -1,4 +1,4 @@
https://docs.google.com/spreadsheets/d/1gp8SxGU_EFDkwlBPFXN4ttVlmq59eoG-xVRPyHyjpw8
[https://docs.google.com/spreadsheets/d/1gp8SxGU_EFDkwlBPFXN4ttVlmq59eoG-xVRPyHyjpw8](https://docs.google.com/spreadsheets/d/1gp8SxGU_EFDkwlBPFXN4ttVlmq59eoG-xVRPyHyjpw8)
# 2004

View File

@ -1,6 +1,6 @@
![x](OEM-Docs/Mercedes/mercedes_170.png)
https://en.wikipedia.org/wiki/Mercedes-Benz_M113_engine
[Wikipedia - Mercedes-Benz M113 Engine](https://en.wikipedia.org/wiki/Mercedes-Benz_M113_engine)
# 2000 S430

View File

@ -1,7 +1,7 @@
Ecotec
https://www.ecotecmiata.ca/how-to
[Ecotec Miata How-to](https://www.ecotecmiata.ca/how-to)
http://www.bowtie6.com/ecotec-ecm-tuning-intro/
[Ecotec ECM tuning intro](http://www.bowtie6.com/ecotec-ecm-tuning-intro/)
http://speed.academy/mazda-miata-ecotec-swap-part-8-header-exhaust-system/
[Ecotec Swap header & exhaust system](http://speed.academy/mazda-miata-ecotec-swap-part-8-header-exhaust-system/)

View File

@ -1,5 +1,5 @@
48 pin case
See also https://rusefi.com//wiki/index.php?title=Vehicle:Mazda_Miata_1994
See also [1994 Mazda Miata](Mazda-Miata-1994)
https://www.miataforumz.com/1990-200-Miata-Wiring/95sys.pdf

View File

@ -1,6 +1,6 @@
[64 pin Connector](OEM-connectors#64-pin)
http://rusefi.com/forum/viewtopic.php?f=3&t=467
[Mazda MX5 1.8 1999 AE](http://rusefi.com/forum/viewtopic.php?f=3&t=467)
[Mazda Miata NB1 Trigger](All-Supported-Triggers#mazda-miata-nb1)