Proteus v12 club

Your chance to introduce yourself and your vehicle
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Proteus v12 club

Post by AndreyB »

"STMicroelectronics Virtual COM Port" means you have not switched device to DFU mode. Use the button or use console UI or use console command line.
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
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

AndreyB wrote:
Sun May 31, 2020 1:38 am
"STMicroelectronics Virtual COM Port" means you have not switched device to DFU mode. Use the button or use console UI or use console command line.
okay thanks!
i pushed the "prog" and the "reset" buttons at same time, and it seemed to work

is this the proper code? or is there an error?
it does not seem to change the TunerStudio "base engine"-- still says 8 cylinders

thanks
!!!

pi@raspberrypi:~ $ dfu-util --list
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Found DFU: [0483:df11] ver=2200, devnum=9, cfg=1, intf=0, path="1-1.4", alt=3, name="@Device Feature/0xFFFF0000/01*004 e", serial="358034793038"
Found DFU: [0483:df11] ver=2200, devnum=9, cfg=1, intf=0, path="1-1.4", alt=2, name="@OTP Memory /0x1FFF7800/01*512 e,01*016 e", serial="358034793038"
Found DFU: [0483:df11] ver=2200, devnum=9, cfg=1, intf=0, path="1-1.4", alt=1, name="@Option Bytes /0x1FFFC000/01*016 e/0x1FFEC000/01*016 e", serial="358034793038"
Found DFU: [0483:df11] ver=2200, devnum=9, cfg=1, intf=0, path="1-1.4", alt=0, name="UNKNOWN", serial="358034793038"

pi@raspberrypi:~ $ dfu-util -a 0 -D /home/pi/Downloads/proteus-f4/rusefi_proteus-f4.dfu
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Match vendor ID from file: 0483
Match product ID from file: df11
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
dfu-util: Could not read name, sscanf returned 0
dfu-util: Failed to parse memory layout


pi@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Bus 001 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 003: ID 1c4f:0026 SiGma Micro Keyboard
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:~ $
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Proteus v12 club

Post by AndreyB »

I was able to upload via DFU into my discovery board
pi@raspberrypi:~/rusefi/snapshot_20200514_234601_stm32f407_rusefi $ dfu-util -a 0 -D rusefi.dfu
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Match vendor ID from file: 0483
Match product ID from file: df11
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash "
file contains 1 DFU images
parsing DFU image 1
image for alternate setting 0, (1 elements, total size = 343236)
parsing element 1, address = 0x08000000, size = 343228
Download [=========================] 100% 343228 bytes
Download done.
done parsing DfuSe file
pi@raspberrypi:~/rusefi/snapshot_20200514_234601_stm32f407_rusefi $
All the commands I've used are now at https://github.com/rusefi/rusefi/wiki/Useful-Linux-Commands
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
puff
contributor
contributor
Posts: 2961
Joined: Mon Nov 11, 2013 11:28 am
Location: Moskau

Re: Proteus v12 club

Post by puff »

seems, osx is nearly as same as popular as linux here)
you didn't mention that you can enter dfu mode by shorting BOOT to vcc (?) and resetting the board (I did it today to flash it). though, chip erase was a bit different story.

(as an alternative to that java line)
mck1117
running engine in first post
running engine in first post
Posts: 1493
Joined: Mon Jan 30, 2017 2:05 am
Location: Seattle-ish

Re: Proteus v12 club

Post by mck1117 »

puff wrote:
Sun May 31, 2020 7:46 pm
seems, osx is nearly as same as popular as linux here)
you didn't mention that you can enter dfu mode by shorting BOOT to vcc (?) and resetting the board (I did it today to flash it). though, chip erase was a bit different story.

(as an alternative to that java line)
yes - that's what the push button marked "PROG" is for. If that button is held while USB is connected (or held while reset is pressed & released), then the MCU will enter DFU mode instead of loading our firmware.
Abricos
contributor
contributor
Posts: 849
Joined: Mon Aug 18, 2014 12:32 am
Location: Carteret, NJ 07008

Re: Proteus v12 club

Post by Abricos »

bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

AndreyB wrote:
Sun May 31, 2020 6:26 pm

All the commands I've used are now at https://github.com/rusefi/rusefi/wiki/Useful-Linux-Commands
i ran those commands,
and the JAR file has the port as AMA0
but my computer is using ACM0 -- which is the standard arduino port setup...

and i don't know how to change it...

angst...


pi@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Bus 001 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 003: ID 1c4f:0026 SiGma Micro Keyboard
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:~ $ lsusb | grep DFU
Bus 001 Device 006: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
pi@raspberrypi:~ $ java -jar /home/pi/Downloads/rusefi_console.jar reboot_dfu
2020-05-31_20_09_30_576<EOT>: Trying [/dev/ttyAMA0]
2020-05-31_20_09_30_588<EOT>: [SerialIoStreamJSerialComm] openPort /dev/ttyAMA0
2020-05-31_20_09_30_636<EOT>: protocol.plain: false
2020-05-31_20_09_30_637<EOT>: Sending packet 53
2020-05-31_20_09_30_638<EOT>: header: waiting for 2 byte(s)
2020-05-31_20_09_35_586<EOT>: /dev/ttyAMA0: Closing port...
2020-05-31_20_09_35_587<EOT>: /dev/ttyAMA0: Closed port.
rusEFI not detected

pi@raspberrypi:~ $
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Proteus v12 club

Post by AndreyB »

I have a very important question and I would need a precise answer if possible:

If your rusEFI is already in DFU mode (probably via hardware switch), why are you trying to switch it into DFU programmatically mode once again?
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
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

delete
Last edited by bill on Sat Jun 13, 2020 12:17 am, edited 1 time in total.
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

AndreyB wrote:
Mon Jun 01, 2020 12:23 am
I have a very important question and I would need a precise answer if possible:

If your rusEFI is already in DFU mode (probably via hardware switch), why are you trying to switch it into DFU programmatically mode once again?
i put it into DFU mode with the hardware switch, true.

i thought you needed to do that for the JAVA console
you do need to hit the hardware switch to run dfu-util.

i ran the java console again with the board in virtual com port mode
and here is the code printout

did it work okay??
Last edited by bill on Sat Jun 13, 2020 12:17 am, edited 1 time in total.
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Proteus v12 club

Post by AndreyB »

Please download latest bundle since new command was added recently

please do

java -jar rusefi_console.jar detect

this new command would print rusEFI firmware version.

thank you for your patience, we are learning how to support users on the go
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
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

delete
Last edited by bill on Sat Jun 13, 2020 12:16 am, edited 1 time in total.
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

delete
Last edited by bill on Sat Jun 13, 2020 12:16 am, edited 1 time in total.
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Proteus v12 club

Post by AndreyB »

I have just DFU programmed my F7 proteus and I am getting

*** rusEFI v20200531@23324
*** Chibios Kernel: 5.1.0
*** Compiled: May 31 2020 - 18:45:23

my newer F4 proteus still does not have USB connector so I cannot validate that. I believe it's time for you to start asking for help at https://app.slack.com/client/T4NJHQ8QZ/CKEGKCQ4U/details/pins
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
Abricos
contributor
contributor
Posts: 849
Joined: Mon Aug 18, 2014 12:32 am
Location: Carteret, NJ 07008

Re: Proteus v12 club

Post by Abricos »

Maybe you need check if it work on PC ... Maybe raspberry 🥧 have different USB power or Linux don't have stm drivers ...
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

delete
Last edited by bill on Sat Jun 13, 2020 12:15 am, edited 1 time in total.
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

**** FINAL LINUX FIX !!!******

i did get this stm32 cube program to work on ubuntu 18.04
https://www.st.com/en/development-tools/stm32cubeprog.html

i erased the chip and reloaded the firmware, finally!
using this .BIN
https://github.com/rusefi/rusefi/wiki/Download
the Proteus 0.3 and newer (STM32F4)

there is a bug in dfu-util 0.9 on
ubuntu 18.04
and also Raspbian -- newest version
do not use!

apparently in Ubuntu 20.04.... dfu-util works fine

for your information ...
Last edited by bill on Fri Jun 12, 2020 1:36 am, edited 1 time in total.
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

the V-12 has some nissan / hitachi throttle bodies.
the bodies fit fine on the long direction-- 68mm.
The 58mm dimension-- i need to elongate the mounting holes a bit.
the BMW hole is 60MM diameter, but he nissan is ~70MM.
so its got an oversize throttle body. -- 2 of them, actually
Both are from a v-6 - 3.2L-- 2003 altima.
IMG_20200610_094904174.jpg
IMG_20200610_094904174.jpg (1.57 MiB) Viewed 20159 times
IMG_20200610_094838311.jpg
IMG_20200610_094838311.jpg (2.25 MiB) Viewed 20159 times
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

some pics-->
IMG_20200617_200026265.jpg
IMG_20200617_200026265.jpg (1.41 MiB) Viewed 19552 times
IMG_20200617_200135852.jpg
IMG_20200617_200135852.jpg (1.19 MiB) Viewed 19552 times
IMG_20200617_200039560.jpg
IMG_20200617_200039560.jpg (1.45 MiB) Viewed 19552 times
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

okay

i am wiring up the engine now... so a few questions

1-- which pin does the crankshaft sensor go?
Variable Reluctance #1 negative?
or DIGITAL 1 Digital trigger/switch input ?

2-- camshaft sensor... same??

3-- coolant temp sensor? pin # ?

4-- throttle body.. 2 of them...

5-- gas pedal..

6-- MAP or MAF sensor

7-- idle air?

etc... any thing that someone would like to standardize, that would be useful

Thanks!!
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

also,
anybody know how the IDLE AIR is handled on the BMW? i have nissan throttle bodies with nothing built in for idle air.
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

lastly

i have Coil on Plug i grabbed from a SAAB 9-3. It has Ionic sensing.
take a look at the pictures.
i believe that the 2 heavy gauge --Red and Black --wires are for the coil power
and the other two are the trigger/signal wires...
the wire going to the black ground is probably the signal ground
leaving the last wire as the signal IN
Is that right?
and the wires coming out of the ION sensor are just "not used/ connected" for now

thanks
Attachments
IMG_20200618_111113088.jpg
IMG_20200618_111113088.jpg (2.75 MiB) Viewed 19509 times
IMG_20200618_110303377.jpg
IMG_20200618_110303377.jpg (2.08 MiB) Viewed 19509 times
IMG_20200618_111123266.jpg
IMG_20200618_111123266.jpg (2.93 MiB) Viewed 19509 times
IMG_20200618_110207011.jpg
IMG_20200618_110207011.jpg (2.29 MiB) Viewed 19509 times
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Proteus v12 club

Post by AndreyB »

That's too many areas at the same time.

Let's start with pedal and throttle bodies. Please read wiki pages and let know what questions remains after reading ETB pages.

Idle air is handled by ETBs
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
Simon@FutureProof
contributor
contributor
Posts: 413
Joined: Tue Jul 24, 2018 8:55 pm
Github Username: Orchardperformance
Slack: Orchardperformance

Re: Proteus v12 club

Post by Simon@FutureProof »

bill wrote:
Thu Jun 18, 2020 7:19 pm
okay

i am wiring up the engine now... so a few questions

1-- which pin does the crankshaft sensor go?
Variable Reluctance #1 negative?
or DIGITAL 1 Digital trigger/switch input ?

2-- camshaft sensor... same??

3-- coolant temp sensor? pin # ?

4-- throttle body.. 2 of them...

5-- gas pedal..

6-- MAP or MAF sensor

7-- idle air?

etc... any thing that someone would like to standardize, that would be useful

Thanks!!
I think it is all on the wiki page below. Let me know if anything is missing.

https://github.com/rusefi/rusefi/wiki/Hardware_Proteus_Wiring_v03
Now keeping MRE in stock in the UK - https://www.FutureProofPerformance.com
Simon@FutureProof
contributor
contributor
Posts: 413
Joined: Tue Jul 24, 2018 8:55 pm
Github Username: Orchardperformance
Slack: Orchardperformance

Re: Proteus v12 club

Post by Simon@FutureProof »

bill wrote:
Thu Jun 18, 2020 7:21 pm
also,
anybody know how the IDLE AIR is handled on the BMW? i have nissan throttle bodies with nothing built in for idle air.
Idle air on the BMW is normally done with a Bosch 3 wire (duel circuit) IAC valve. I am not sure if the V12 used the ETB for idle, Andrey may be able to confirm.
You may be able to do idle by ITB.

https://github.com/rusefi/rusefi/wiki/HOWTO_electronic_throttle_body

https://github.com/rusefi/rusefi/wiki/HOWTO_electronic_throttle_body_configuration
Now keeping MRE in stock in the UK - https://www.FutureProofPerformance.com
mck1117
running engine in first post
running engine in first post
Posts: 1493
Joined: Mon Jan 30, 2017 2:05 am
Location: Seattle-ish

Re: Proteus v12 club

Post by mck1117 »

Even if that engine has IAC(s), just use the etb. We support idle control with the etb which is much smoother than using and idle valve.
User avatar
AndreyB
Site Admin
Posts: 14292
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: Proteus v12 club

Post by AndreyB »

I believe M73 OEM uses ETB for IAC. And we support this and we want to use it this way.
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
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

AndreyB wrote:
Thu Jun 18, 2020 10:26 pm
I believe M73 OEM uses ETB for IAC. And we support this and we want to use it this way.
okay good.
bill
Posts: 219
Joined: Sun Mar 29, 2020 1:44 pm
Location: DC usa

Re: Proteus v12 club

Post by bill »

OrchardPerformance wrote:
Thu Jun 18, 2020 9:40 pm
bill wrote:
Thu Jun 18, 2020 7:19 pm
okay

i am wiring up the engine now... so a few questions

1-- which pin does the crankshaft sensor go?
Variable Reluctance #1 negative?
or DIGITAL 1 Digital trigger/switch input ?

2-- camshaft sensor... same??

3-- coolant temp sensor? pin # ?

4-- throttle body.. 2 of them...

5-- gas pedal..

6-- MAP or MAF sensor

7-- idle air?

etc... any thing that someone would like to standardize, that would be useful

Thanks!!
I think it is all on the wiki page below. Let me know if anything is missing.

https://github.com/rusefi/rusefi/wiki/Hardware_Proteus_Wiring_v03
everything i listed is missing
i already wired up everything listed on the wiki
photo to follow

check the wiki wiring pinout... none of these are listed ...
thanks ...

see that white connector and small black connector are mighty sparse
IMG_20200618_193929608.jpg
IMG_20200618_193929608.jpg (2.88 MiB) Viewed 19551 times
IMG_20200618_193938883.jpg
IMG_20200618_193938883.jpg (2.39 MiB) Viewed 19551 times
Post Reply