The goal is dash control (speedo, tacho and boost gauge) with additional sensors, like EGT and knock.
I go for basic and through hole because I am not sure about me, if it's fine, I can change the BOM and pick and place for more or less options. The problem stays the 2 boards to buy.
Actually I pay 6$ for through holes part for power supply, and 8$ for 2xTC4427 (I don't want 3 for now, and I don't want it on the testing board), 2$ for TPIC8101, 18$ for 8 VNP5N07 and 18$ for 1 box with connectors (the second board is only for testing)
It's a little more than 100$
I was tempted to put a CJ125 from bosch on the board, for testing, but the stm that i choose for the GPIO board is SPI limited.
I really like the MicroRusEFI, I want just to complete it.
The STM from basic part aren't for Industrial Use, mean less heat range. I prefer not use them for an ECU.
The problem with your project is more software, I think proteus has already all you want. But I don't see enough tuning options for so much input and output in tuner studio. RusEFI focus on engine control, but there is somme cool transmisions part.
Why do you want ch340 ? what's wrong with the USB from stm ?
What is your goal ?! Active suspension ?
If my basic GPIO works fine and that I can trust my PCB making and JLC, I will take a look for a more advanced simple board with extended parts.
For now, I don't know, and I don't think I can be of good advice.
Full JLC PCB
Re: Full JLC PCB
gepro, now it becomes clear - i probably have missed that part
mck1117, f0 don't have canbus, do they?
405 seems overkill for my purpose, however, for a batch of 5 boards the cost difference would be under $8 - probably, not that much. still, why should I choose them if the one from blue pill works just fine? plus lots of ready to go codebase for monkey-style google-coding
mck1117, f0 don't have canbus, do they?
405 seems overkill for my purpose, however, for a batch of 5 boards the cost difference would be under $8 - probably, not that much. still, why should I choose them if the one from blue pill works just fine? plus lots of ready to go codebase for monkey-style google-coding
-
- running engine in first post
- Posts: 1494
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: Full JLC PCB
some f0 do - I know the f042 does. I think all of the F0x2 chips have it.
Re: Full JLC PCB
ha! thank you for this hint
STM32F042K6T6
even though it is in extended parts, for a batch of 5 boards it will be even cheaper.
STM32F042K6T6
even though it is in extended parts, for a batch of 5 boards it will be even cheaper.
- AndreyB
- Site Admin
- Posts: 14332
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Full JLC PCB
Have you placed an order?
"Full JLC PCB" probably means that MAX9926 is not an option?
"Full JLC PCB" probably means that MAX9926 is not an option?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: Full JLC PCB
Yeah ! That's already send from JLC. And I have the majority of the parts "through holes", but I don't have TPIC8101 for now.
In fact, it is more a "Full Basic JLC with through holes components"
The MAX9926 is a board from speeduino, I have already done it with my microrusefi, but it isn't soldered on the board I use the plug from my megasquirt... Here is picture of the horror !
I won't use the VR from TLE, because I made a lot of test on the MAX9926 with a picoscope, and I know it well.
I see that GP1-4 from microrusefi can be push pull now, so Okay for PWM fan, tacho and speedo out, this GPIO starts to have less interests to me
In fact, it is more a "Full Basic JLC with through holes components"
The MAX9926 is a board from speeduino, I have already done it with my microrusefi, but it isn't soldered on the board I use the plug from my megasquirt... Here is picture of the horror !
I won't use the VR from TLE, because I made a lot of test on the MAX9926 with a picoscope, and I know it well.
I see that GP1-4 from microrusefi can be push pull now, so Okay for PWM fan, tacho and speedo out, this GPIO starts to have less interests to me
Re: Full JLC PCB
Just for information. This board is a big fail.
I put 5v for VIO on the canbus chip... The canbus can't be use, the stm32 is 5V tolerant only for digital input.
I have set the battery input voltage on a non ADC pins And lot of shits like that...
The EGT chip gives nothing, it is a fatal error when I set it. Probably PC10 conflict with "connections". And the TPIC gives nothing, It is probably a mistake to not pin the analog out of the chip !
The TLV chip for analog out turbo pressure wasn't received for now But like there is no CAN? it is not really a problem
Except that, the PCB from JLC has really great quality, soldering the TPIC was doable, the DFU flashing is simple, the communication on TS is fine, and the outputs all look to work well. (lowside and high side)
I put 5v for VIO on the canbus chip... The canbus can't be use, the stm32 is 5V tolerant only for digital input.
I have set the battery input voltage on a non ADC pins And lot of shits like that...
The EGT chip gives nothing, it is a fatal error when I set it. Probably PC10 conflict with "connections". And the TPIC gives nothing, It is probably a mistake to not pin the analog out of the chip !
The TLV chip for analog out turbo pressure wasn't received for now But like there is no CAN? it is not really a problem
Except that, the PCB from JLC has really great quality, soldering the TPIC was doable, the DFU flashing is simple, the communication on TS is fine, and the outputs all look to work well. (lowside and high side)
Re: Full JLC PCB
you mean to say pb5 and pb6 of stm32f405rg56 are not 5v tolerant? according to the datasheet, they are! or they are only 5v tolerant as general GPIO, but not for CAN purpose?
is it a 2 layer or a 4-layer board? you can still use it: replace the can transceiver with 3.3v-powered one, cut the 5V supply voltage trace and wire it to the 3v3 bus, voilà
btw, what's wrong with the thermocouple chip?
is it a 2 layer or a 4-layer board? you can still use it: replace the can transceiver with 3.3v-powered one, cut the 5V supply voltage trace and wire it to the 3v3 bus, voilà
btw, what's wrong with the thermocouple chip?
-
- running engine in first post
- Posts: 1494
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: Full JLC PCB
AFAIK the only difference between 3.3v inputs and 5v inputs is the high side ESD/clamp diode. 3.3v pins have a plain diode from the pin to the positive supply rail. 5v tolerant pins have a ~2.5v zener from the pin to the positive supply rail, clamping at ~5.5-6 volts instead of the ~3.8-4 of 3.3v only pins. The datasheet doesn't explicitly say that it's ok to put 5v on those pins when in AF mode, but you can deduce from the GPIO pin block diagram that it probably is indeed safe.
Re: Full JLC PCB
Hum, I know that STM32 is 5V tolerant only for Digital in. But canbus is sort of digital.
I don't try it, because I don't want to kill the STM32. But I have a second board with no through hole components and plug. I will try canbus on it ! If it don't work, I will try 3.3v soldering on chip.
The thermocouple chip's SPI does a fatal error, there is trouble with PC10, "console TX conflict", and when I don't have trouble the stm becomes completely bricked, and I can't no more reflash with rusefi tools.
I have to completely reflash it with STM32CubeProgrammer. (I load the DFI file, and it works fine)
I try it on the 2 boards, same thing for EGT and TPIC. But I don't try every rusefi firmware.
I think I will do a more simple board, 2 layers, with different 5V supply (no more external through holes components) and BSP76 for LowSide.
I will use the same pin mapping than official boards.
Thank you very much for help
I don't try it, because I don't want to kill the STM32. But I have a second board with no through hole components and plug. I will try canbus on it ! If it don't work, I will try 3.3v soldering on chip.
The thermocouple chip's SPI does a fatal error, there is trouble with PC10, "console TX conflict", and when I don't have trouble the stm becomes completely bricked, and I can't no more reflash with rusefi tools.
I have to completely reflash it with STM32CubeProgrammer. (I load the DFI file, and it works fine)
I try it on the 2 boards, same thing for EGT and TPIC. But I don't try every rusefi firmware.
I think I will do a more simple board, 2 layers, with different 5V supply (no more external through holes components) and BSP76 for LowSide.
I will use the same pin mapping than official boards.
Thank you very much for help