rusefi.com

wrong PID parameters that don't count for wear and tear of that exact throttle body?

So, that's a tight balancing act not in terms of the right injector choice, but rather in the number of available pins on the mcu for FB, and its computational resources (vs using a standalone specialized driver with buil-in bells and whisltes)

do you have an inspection mirror?

an opamp to amplify voltage?

I would like to connect rusEfi to my android head unit with MSDroid for tuning some values

which values?

roughly one or two updates per second at 9600kbps?

Booth 1539? %-)

cool stuff is this nylon! probably feels even better than it seems!

that is yet another good question, and if 10degC is enough, probably it won't matter what sort of connector you use

Thanks a lot! The only question is there are no PF4/PF5 pins in stm32f407vgt6 - there is no PF port at all. Is software knock processing at all supported in 407 chip?

so, do I get it right that the hip9011 solution has now become officially obsolete in rusefi? in this thread there are two almost similar schemes - with mcp6004 and with two LMV321IDBVR - which one is better? where do I get the Vmid (VREF2) signal and what to which pin of stm32f407 should i connect ...

late followup. I just started the recent rusefi image on this board! (used jlink to flash it, had to solder on a 3k pull-up to pa12). I was surprised to see a usb disk with probably useful stuff)

finding the proper connector for the thermocouple of a certain type is a quest in itself. however, if you look at cheap thermocouple plugs used in some multimeters - you might think there is nothing special in them - the wire's end forms a loop, which is just fixed to the plug with a screw. but you ...

where do I read more about that CAN-to-serial-to-TunerStudio bridge? If it works fine, it might be a good idea to implement it on board, so that the ecu can be completely sealed?

in mazda rx7 there are two fuel level sensors: the main one and the auxiliary one (the fuel tank is somewhat split, afaik), and they are not in series, but are rather connected to separate inputs in the dashboard.

can a small mosfet be used instead of BC337 in this case? (with a flyback diode across the coil)

this is probably offtopic here ;-) nothing particular. just saw a usb connector, which reminded me of some pronounced ideas of moving to can bootloader (still under construction?) besides, when recently my brother was chip-tuning his diesel citroen, the garage guy soldered some wires to the ecu dire...

size and orientation of the sensor's core does matter! using a scope to check the signal consistency might also be a good idea..

GD -
Is USB still a primary way of communications with TS / devconsole?

to be placed on a valve cover? is it triggered from a special sprocket, or just from a normal cam? + what type os sensor is that?

may be this is something worth looking at?
https://community.silabs.com/s/question/0D51M00007xeRO9SAM/spp-over-ble-windows-drivers?language=en_US

wtf?? is there any rationale behind that decision by eBay?

okay. don't know how to comment on github. The bluetooth module in alphax is definitely a BLE device (bursts of data, rather than old-style SPP profile) After you connect it to the MCU, (MCU's TX to WL9981TC RX, MCU's RX to WL's TX, Paragraph 4 of the datasheet), after power up you should see 'READY...

nrf5822?

From my understanding, with alphax, you need first to flash "serial to BT" firmware to that chip (before soldering it onto the board). Then you'll need some special software supporting BLE on the PC side.
my bad. just found the datasheet on jlcpcb. will comment later.

Yes, hate the blue pill with clone MCU on it. In my case I have a CKS32F103… instead of STM32F103… However, if you do end up with one, there is a way to get it working with OpenOCD. >> 1. Use OpenOCD as your debugger (GDB will not work) 2. Find the config file : stm32f1x.cfg Location is similar to ...

is it not late, when the temperature is 900ºC?

ps. are you trying to upload the same very .bin file you used with stm32? afaik, gd chips have sligthly different registers and addresses, so, the firmware should be different.

segger worked just fine for me with 190, but you'd probably have to reflash your stlink into jlink (google for that free reflash tool, the operation is reversable)
btw, with segger you'd have to choose the proper µcu.

Mr. Markov:
https://en.wikipedia.org/wiki/Andrey_Markov
Mr. Markov's chain:
https://en.wikipedia.org/wiki/Markov_chain

why is it all about stm32f1x.cpu?