General support questions thread

[filip5]

Hello there. I am new here so I have this question. Does anybody know if the outputs of Frankenso board of the ignition (spark) test and injection test match the displayed outputs on the Rusefi console? It does not seem to match. Also the Tuner Studio does not seem to activate on its test bench what Rusefi seem to activate. I tried the latest hex but that seem to control totally different outputs/ Any thoughts ? Thanks

[AndreyB]

Hello there. I am new here so I have this question. Does anybody know if the outputs of Frankenso board of the ignition (spark) test and injection test match the displayed outputs on the Rusefi console? It does not seem to match.

There is a known bug with TS test buttons - see https://github.com/rusefi/rusefi/issues/307 - unfortunately it's not documented nicely, I am not sure what exactly was the problem I was experiencing but sounds similar. Please provide more details, I am not exactly sure what exactly you are doing and what exactly seems to be expected and actual result.

My suggestion would be to try console bench buttons since these provide detailed output.

[filip5]

It's okay. I am not sure what happened but I loaded the hex again and seem to work fine. The Tuners Studio does the test 3 times in 3 sec increments and one needs to wait as opposed to Rusefi that does it one time. The only issue I see is that there are no LEDs for the Ignition 3(PE10) and ignition 4(PE8). Also there is no output for radiator fan, idle valve and fuel pump(NONE) at least in test mode. Is this correct?

[AndreyB]

I suspect the four ingnition transistors are not set same on the board, some probably have vp 5v jumper added while some do not? That would explain lack of led impulses.

Will check default output mapping but it should be adjustable via ts or console.

[filip5]

Hello there,

I need to configure an output for the radiator fan( possibly 2 fans independently of each other) and output for the idle valve and an output for the fuel pump.
I would also need another temperature sensor input for the intake air.

Can someone advise how to configure these thru Rusefi console or Tuner Studio?

Thanks

[AndreyB]

Once you install TunerStudio and create a project based on our custom rusefi.ini project definition file my recommendation is to go over all menu items in order to see what options are there. One day we will record a video showing all these UI dialogs under https://github.com/rusefi/rusefi/issues/373

I think all the pins you are interested in at under "Engine" menu:

[filip5]

Okay thanks . Seem to work fine.

[filip5]

Is there any restriction which of the pins can be configured as input and which can be configured as output?

[AndreyB]

PS: some pin changes still require ECU full reboot with either reset button or power cycle. Work in progress on allowing more changes to happen on the fly.

Most of the pins you are allowed to select via TS would work - as long as your chip and your hardware have the the pins. As long as you are using a standard board your options are pretty limited by the board design.

[filip5]

Some pins are floating from what I noticed. They are working but when this unit is placed in a car the I/O pins should be grounded with a high value resistor so no false activity happens. This is my opinion though. I will do this in my board.

[AndreyB]

Some pins are floating from what I noticed.

It would be easier to focus on one specific pin. What specific pin are you concerned about?

Frankenso 0.4 has pull-downs on low-side lines, next board would have pull-downs on both low-side and high-side drivers.

[filip5]

Pins PE14 and pins PE12 are floating and the outputs are coming on falsely and that is problematic.
These are so far 2 pins that I have seen because they have LED on output and that can be seen. I will advise if I see more. I do not know if the inputs have problems or if they are pulled down.
All input should be pulled down with at least 10k to 20k resistor.

[AndreyB]

Pins PE14 and pins PE12

Exactly, that's addressed on future board version Frankenso 0.5

There are pull-downs inside the MCU but these are only configured once the firmware is running, these pins are floating while firmware is starting.

[filip5]

Pins PD8 PD9 are also floating , if that helps.

[AndreyB]

Pins PD8 PD9 are also floating , if that helps.

It's eight "high" pins - see http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board#Default_Pinout

[filip5]

I see that they are spares but I plan to use them.2 outputs are for radiator fans and one output for the idle valve. Radiator fans can start without a reason
but idle valve is critical.

[filip5]

Some issues with the Frankenso schematic pins of inputs and outputs. The board is not effected, just the wiring diagram. If anyone sees anything wrong with this
please advise.

[AndreyB]

Page 1:

PE0<>PD5 and PE1<>PD3 already changed on https://github.com/rusefi/rusefi/blob/master/hardware/frankenso/frankenso_schematic.pdf which would be version 0.5 PDF one day

PE14 why do you think it should be HI #3 and not HI #2?

On the other hand HL2 silkscreen is definitely on the wrong connector pin.

HL7 silkscreen is missing.
HL8 silkscreen is missing.

It could be that you are talking about a different issue?

[AndreyB]

On your PDF the bottom-right corner is always trankated - it shows 2014 file date but does not show file revision. Just to be clear - what is the exact source of this revision of this file?

[AndreyB]

Just modified wiki page. It used to show latest and 0.2 schematics, now it has links for latest, 0.2 and 0.4

http://rusefi.com/wiki/index.php?title=Manual:Hardware_Frankenso_board#Overview

[AndreyB]

INP1 as CLT we already have on 0.4 schematics

INP2 as IAT we already have on 0.4 schematics

[AndreyB]

Well, this is a bit weird. @ is also puzzled.

[filip5]

Just some labeling need swapping in the schematic.

[kb1gtt]

Thank you for the feedback, much appreciated. You have surfaced many issues.

One item worth noting, it appears you are working with an older schematic for R0.4. Some of your comments have already been resolved. We believe you had the wrong PDF because of a bad link on the wiki page. Please note this PDF indicates R0.4.2 in the bottom right of the drawing. That wiki page has been updated. See PDF found here.
https://raw.githubusercontent.com/rusefi/rusefi/master/hardware/rusefi_hardware_history/frankenso_rev00.40/frankenso/frankenso_schematic.pdf

We are currently reviewing your PDF, and we plan to have updated information this weekend, or sooner.

[filip5]

Thanks kb1gtt, the first thing of order is to make sure that all schematic is absolutely correct if this have to work properly. Next is software.

[filip5]

kb1gtt, on PG2 swap H_In2 with H_In3 on both sides. H_In2 connects to PC9 and H_In3 connects to PE14

[filip5]

"PE14 why do you think it should be HI #3 and not HI #2?"
Because (PE14) or HI3 is connected to IC U602 if you follow the path InA(pin2) and that leads to HL3 or W7 on P99A connector. You can swap the marking at the connector
P99A or at the insert PG2. I think would be easier to do at PG2 insert.

[AndreyB]

We believe schematic is technically correct but it was super confisuin because "channel 3 input" was becoming "channel 1 output". 7 out of 8 pins were... weird:

old>new

3>1 69 PC9
1>2 67 PC7
2>3 68 PE14
4>4 70 PE12

6>5 72 PE10
5>6 71 PE8
8>7 74 PD9
7>8 73 PD8

silkscreen was not correct

Working on fixing it now

[filip5]

You are correct. All the ignition outputs PC9,PC7, PE14, PE12,PE10, PE8, PD9 and PD8 do not float as soon as they are configured in the controller, so no pull down resistors are required.
Is that possible to configure these outputs in the controller to be outputs whether they are configured in Tuner Studio or Rusefi console or not? These are outputs to begin with so I think would be
helpful to have them as such if possible either when they are used or not. Just a thought. I do not like to see them floating when they are not configured.

[AndreyB]

do not float as soon as they are configured in the controller, so no pull down resistors are required.

Still need them for while firmware is booting - you can hear a PUFF once in a while on a real car.

https://www.youtube.com/watch?v=2DCj6zreIRc