rusefi.com

We have a rusEfi own console application which is a handy monitoring, development and debugging tool. The dev console is written in java and it talks to the firmware using the plain text protocol. The console allows firmware monitoring and configuration.





If used together with the build-in position sensor emulator, the console allows some level of testing on the bench, without a real engine or any additional hardware. The most useful feature is the plain signal sniffer - both real inputs and generated signals can go into it and this is actually quite handy. Another useful feature is the text log.

You can use the console to invoke rusEfi commands and control the internal flow using the 'Messages Central' tab


This console is pretty plain, but still. Sources and binaries in corresponding bundle.

This tool is not intended to replace the 3rd party tuners, but it comes handy during development phase. I am accepting patches

rusEfi dev console required java 1.7+

rusEfi dev console would ask you to select which serial address it should use, but you can also specify it as a command line parameter

It's been too long since I've looked at Java.

Any chance you could add a scrolling graph?

jedediah_frey wrote:Any chance you could add a scrolling graph?

Can you please describe this in more detail? Just to be sure we talk about the same thing.

russian wrote:Can you please describe this in more detail? Just to be sure we talk about the same thing.

Something like:



We have them at work when we use Vector CANape (I can't find any examples on line).

Basically something like you'd see on an O-scope.

@, I am sorry but so far this is not descriptive at all. I have no idea what to look at, without the context I am missing your point

As is, signal sniffer is a great tool to validate & trouble shoot low-frequency digital signals handled & produces by the ECU without attaching an external logic analyzer. For anything serious a purposely-build software and hardware would always be better.

russian wrote:@, I am sorry but so far this is not descriptive at all. I have no idea what to look at, without the context I am missing your point

Rather than just viewing instantaneous data on the dials you can view a time log of a signal. I don't know if TunerPro has something like this.

X axis is time. So you view the last 60 seconds of data. Sometimes viewing a trail of data will be more helpful than just instantaneous.

jedediah_frey wrote:X axis is time. So you view the last 60 seconds of data. Sometimes viewing a trail of data will be more helpful than just instantaneous.

it's more or less the way it is - data arrives in chunks, you can pause and you can take a picture.

I'd like to see something similar to this http://dangerousprototypes.com/2011/07/10/sump-logic-analyzer-with-2-scope-channels/

SUMP is a JAVA based logic analyzer program very similar to Saelig's logic 16. It has several decoders. I would like to be able to see decoded serial stream data in line with analog data. I also like to see the trends. So I can see things like load is increasing, rather than just a snap shot of the gauges. Gauges are nice when you are driving, but less handy for diag and dev.

I feel something is getting lost in the translation russian.

The tool I am most familiar with at work is called Vector CANape. It allows multiple different types of windows, one of those being a "graph".

It's in the center here. So you can see the trends of data over time and compare it to other signals. For example when you let off of the accelerator does your throttle signal change appropriately?



Or this:



It would allow you to look at the change in something and watch the output of AFR for example.

We have integration with http://www.tunerstudio.com/index.php/tuner-studio

TunerStudio and the the other tools in EFI Analytics family are probably comparable with the tool set you are referring to. That would be our primary "nice" console. Analysing trend and stuff has little to do with the lowest-level, it's just the next level of the tools. This level of features for rusEfi is taken care by TunerStudio.

Our own java console here has a different role - it is more about the lowest-level debug messages and the build-in digital logic analyzer, less about the actual physical processes happening in the engine.

This would either help or make this more confusing

Back to the original topic of the dev console:

It uses a simple human-readable protocol which you can actually see in Putty or other console application. Please note that in order for the dev console to connect you would need to be NOT connected to the serial port with another console - only one thing can use the COM port.

If you can see the human-readable data with Putty you know the COM port is right, you should disconnect the Putty and connect launch the dev console. Right now the UI is still pretty lame and it is trying to guess which COM port to use which sometimes does not work out. In order to specify which COM port to use you would need to launch the console with one the .bar files - like run_com8.bat or run_com15.bat depending on what is your com port number. If there is no .bat file for you port number you would need to edit the existing one - this should get you connected

FWIW, I had to open it using the com11 file in order to get it to recognize the input. It couldn't find it on its own... so if you're not seeing anything in the dev console, try opening it with your com file first

skeeters_keeper wrote:It couldn't find it on its own...

One day someone would improve the tool and it would simply ask you which port to use on start-up... One day.

Q: I get this message when I try to open the rusefi console jar: "java.lang.illegal.state.exception expected two ports but got only one port"
A: Do you see a bunch of batch files like "run_com15.bat"? Use of the them. I guess I should change the name

What these batch files are doing they are simply passing the port name explicitly, like Once day someone would add a serial port selection dialog for the java console. One day...

How to open dev console in Eclipse Gui Designer?

Tambralinga wrote:How to open dev console in Eclipse Gui Designer?

The dev console GUI was created manually so I doubt any Gui Designed would open it

wow! what are you gonna add to dev console?

Hi, I cannot seem to get the Micro\USB port to switch to the Rusefi_DevConsole. I tried connecting PB1 to GND to swap the ports but still the Tunerstudio is connected to the MICRO/ USB. ????


Update: PB1 no longer needed as of 2019

Ian wrote:Hi, I cannot seem to get the Micro\USB port to switch to the Rusefi_DevConsole. I tried connecting PB1 to GND to swap the ports but still the Tunerstudio is connected to the MICRO/ USB. ????

What are your steps exactly and how is it failing exactly? The protocols on these ports are getting closer actually, I believe you should be able to connect rusEfi console to ANY port regardless of the jumper, it's TunerStudio which needs it's own port. I suspect that pretty soon the whole PB1<>GND thing would go away and both ports would work for both tools. Actually here you are https://sourceforge.net/p/rusefi/tickets/262/

Are you using recent version of firmware with recent version of console?

Hi,

My steps as follows. using http://rusefi.com/wiki/index.php?title=Manual:Software:User/en the instructions.
downloaded the tools,including the ST virtual Com port Driver.
programmed the ST F4 board using ST Link. with rusefi_release.bin. binary.
blue light flashing.
I am using ..\snapshot_20160204_1340_rusefi. both binary and Dev_Console
Plugged the Micro USD into the PC. The PC recognizes as COM3. all okay so far.

start rusefi_console.bin. It detects COM3 and askes me to connect. Vs.20160124. press connect.

Top of Java app. shows: DISCONNECTED CONSOLE 20160124; firmware N/A@COM3.
in the message tab.
2016-02-04 19_35: CommandQueue: SerialIO started
2016-02-04 19_35: SerialManager: Opening port: COM3
2016-02-04 19_36: SerialManager: Restarting serial IO
2016-02-04 19_36: SerialManager: Opening port: COM3
2016-02-04 19_36: SerialManager: Restarting serial IO
2016-02-04 19_36: SerialManager: Opening port: COM3
2016-02-04 19_36: SerialManager: Restarting serial IO
2016-02-04 19_36: SerialManager: Opening port: COM3
2016-02-04 19_37: SerialManager: Restarting serial IO
2016-02-04 19_37: SerialManager: Opening port: COM3
2016-02-04 19_37: SerialManager: Restarting serial IO
2016-02-04 19_37: SerialManager: Opening port: COM3

BUT tunestudio works using the same COM3.

One thing I have not done yet is connect the Links. gray jumper wire as noted above between pins PD1 and PC6. and Install the blue jumper wire as noted between pins PD2 and PA5.. Is this enough to stop the COMMS ? I need to buy some pins...


Ian

I cannot explain it, all you are doing sounds right.

You do not need any jumpers or jumper wires to connect the console. Once I get home I will try latest binaries and latest console from the build server just to be totally sure. Sounds like you have the PB1<>GND jumper since your TS connects on microUSB, have you tried without that jumper?

Just confirmed with binaries from the build server - looks good on my end. No idea. Poke me if you want me to teamviewer into your desktop.

If it helps..
TS always works regardless of PB1 open or short to GND - on the micro USB port.

I am thinking it may need a pullup on PB1 or weak pullup enabling in the ST32 micro.?? To switch the port.

I am using the ST4 discovery board right out the box, nothing connected.

I am going to look at the schematics next..

Seems stuck in TS mode.

makes no sense

can you
1) close console
2) unplug micro usb cable
3) hit reset
4) plug micro-usb
5) wait for the port to appear in device manager. is it the only serial in device manager?
6) try connecting with console?

another thing to try would be installing putty or any other terminal application and connecting to this serial port - and let me know what you get? also hit letter t on your keyboard and tell me what happens?

still no comms with Console. but it works with mitty a terminal emulator at 115200.

sounds like a Java problem or is the console setup for 115200 ?

output from mitty on Com3. using MicroUSB and PB1 O/C.

line:916:time,127.238,rpm,0,ENGINE_LOAD,41.82,MAP,41.82,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.46,MAT,52.91,time,127.440,rpm,0,ENGINE_LOAD,41.30,MAP,41.67,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.42,MAT,53.12,time,127.639,rpm,0,ENGINE_LOA
D,41.67,MAP,41.67,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.69,MAT,53.22,time,127
.839,rpm,0,ENGINE_LOAD,41.45,MAP,41.45,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
51,MAT,52.81,time,128.039,rpm,0,ENGINE_LOAD,41.23,MAP,41.60,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.78,MAT,52.91,rusEfiVersion,20160131@9480 CUSTOM 128,outpin,
t1@PC6,outpin,t2@PA5,outpin,input1@NONE,outpin,input2@NONE,outpin,c1@PE14,outpin
,i1@PB9,outpin,c2@PC7,outpin,i2@PE2,outpin,c3@PC9,outpin,i3@PB8,outpin,c4@PE10,o
utpin,i4@PB7,ckp_c,0,fuel_base,5.05,fuel_lag,1.03,fuel,0.00,timing,11.80,duty0,N
aN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,duty1,NaN,dwell1,0.00
,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:697:time,128.240,rpm,0,ENGINE_LOAD,41.23,MAP,41.23,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.24,MAT,53.38,time,128.440,rpm,0,ENGINE_LOAD,41.45,MAP,41.30,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.78,MAT,52.96,time,128.641,rpm,0,ENGINE_LOA
D,41.23,MAP,40.71,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.87,MAT,52.65,time,128
.841,rpm,0,ENGINE_LOAD,41.37,MAP,41.37,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
64,MAT,53.22,time,129.041,rpm,0,ENGINE_LOAD,41.45,MAP,41.52,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.96,MAT,53.43,ckp_c,0,fuel_base,5.05,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:740:time,129.240,rpm,0,ENGINE_LOAD,41.08,MAP,41.08,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.55,MAT,53.22,time,129.442,rpm,0,ENGINE_LOAD,41.30,MAP,41.00,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.28,MAT,53.01,time,129.641,rpm,0,ENGINE_LOA
D,41.60,MAP,41.67,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,46.79,MAT,52.70,time,129
.841,rpm,0,ENGINE_LOAD,41.08,MAP,41.37,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
60,MAT,53.17,time,130.042,rpm,0,ENGINE_LOAD,40.78,MAP,41.15,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.60,MAT,53.33,ckp_c,0,fuel_base,5.03,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,msg,WARNING: C
an't connect or mount MMC/SD,
line:697:time,130.242,rpm,0,ENGINE_LOAD,41.30,MAP,41.30,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.69,MAT,52.81,time,130.442,rpm,0,ENGINE_LOAD,41.15,MAP,41.15,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.24,MAT,53.33,time,130.643,rpm,0,ENGINE_LOA
D,41.00,MAP,41.00,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.51,MAT,53.12,time,130
.843,rpm,0,ENGINE_LOAD,41.60,MAP,41.60,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
69,MAT,53.27,time,131.042,rpm,0,ENGINE_LOAD,40.86,MAP,40.86,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.42,MAT,53.17,ckp_c,0,fuel_base,5.02,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:916:time,131.242,rpm,0,ENGINE_LOAD,40.93,MAP,40.93,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,48.10,MAT,53.22,time,131.444,rpm,0,ENGINE_LOAD,41.15,MAP,40.78,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.91,MAT,53.06,time,131.643,rpm,0,ENGINE_LOA
D,41.15,MAP,41.23,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.19,MAT,53.12,time,131
.843,rpm,0,ENGINE_LOAD,41.30,MAP,41.30,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
73,MAT,53.38,time,132.044,rpm,0,ENGINE_LOAD,41.23,MAP,41.52,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.78,MAT,53.06,rusEfiVersion,20160131@9480 CUSTOM 132,outpin,
t1@PC6,outpin,t2@PA5,outpin,input1@NONE,outpin,input2@NONE,outpin,c1@PE14,outpin
,i1@PB9,outpin,c2@PC7,outpin,i2@PE2,outpin,c3@PC9,outpin,i3@PB8,outpin,c4@PE10,o
utpin,i4@PB7,ckp_c,0,fuel_base,4.98,fuel_lag,1.03,fuel,0.00,timing,11.80,duty0,N
aN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,duty1,NaN,dwell1,0.00
,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:697:time,132.244,rpm,0,ENGINE_LOAD,41.45,MAP,40.71,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,48.01,MAT,53.27,time,132.445,rpm,0,ENGINE_LOAD,41.00,MAP,40.93,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.91,MAT,53.22,time,132.645,rpm,0,ENGINE_LOA
D,41.60,MAP,41.45,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.05,MAT,53.54,time,132
.845,rpm,0,ENGINE_LOAD,41.23,MAP,41.23,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.
01,MAT,53.54,time,133.044,rpm,0,ENGINE_LOAD,41.30,MAP,41.23,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.82,MAT,53.43,ckp_c,0,fuel_base,5.02,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:697:time,133.244,rpm,0,ENGINE_LOAD,41.45,MAP,41.45,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,48.05,MAT,53.69,time,133.445,rpm,0,ENGINE_LOAD,41.23,MAP,41.08,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.96,MAT,53.96,time,133.645,rpm,0,ENGINE_LOA
D,41.30,MAP,41.08,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.78,MAT,53.48,time,133
.845,rpm,0,ENGINE_LOAD,41.15,MAP,41.37,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.
33,MAT,53.17,time,134.046,rpm,0,ENGINE_LOAD,41.82,MAP,41.67,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,48.19,MAT,53.85,ckp_c,0,fuel_base,5.01,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:697:time,134.246,rpm,0,ENGINE_LOAD,41.60,MAP,41.60,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,48.10,MAT,53.75,time,134.447,rpm,0,ENGINE_LOAD,41.45,MAP,41.37,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.10,MAT,54.07,time,134.647,rpm,0,ENGINE_LOA
D,41.30,MAP,41.23,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.37,MAT,53.59,time,134
.847,rpm,0,ENGINE_LOAD,41.08,MAP,41.37,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.
05,MAT,53.48,time,135.046,rpm,0,ENGINE_LOAD,41.30,MAP,41.37,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,48.14,MAT,53.75,ckp_c,0,fuel_base,5.02,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:916:time,135.246,rpm,0,ENGINE_LOAD,41.08,MAP,41.08,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.87,MAT,53.27,time,135.447,rpm,0,ENGINE_LOAD,41.23,MAP,41.30,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.19,MAT,53.80,time,135.647,rpm,0,ENGINE_LOA
D,41.30,MAP,40.86,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.60,MAT,54.01,time,135
.848,rpm,0,ENGINE_LOAD,41.23,MAP,41.30,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
91,MAT,54.23,time,136.048,rpm,0,ENGINE_LOAD,41.08,MAP,41.08,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.64,MAT,53.38,rusEfiVersion,20160131@9480 CUSTOM 136,outpin,
t1@PC6,outpin,t2@PA5,outpin,input1@NONE,outpin,input2@NONE,outpin,c1@PE14,outpin
,i1@PB9,outpin,c2@PC7,outpin,i2@PE2,outpin,c3@PC9,outpin,i3@PB8,outpin,c4@PE10,o
utpin,i4@PB7,ckp_c,0,fuel_base,5.02,fuel_lag,1.03,fuel,0.00,timing,11.80,duty0,N
aN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,duty1,NaN,dwell1,0.00
,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:697:time,136.248,rpm,0,ENGINE_LOAD,41.23,MAP,41.23,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.87,MAT,53.33,time,136.449,rpm,0,ENGINE_LOAD,41.37,MAP,41.00,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.60,MAT,53.80,time,136.649,rpm,0,ENGINE_LOA
D,41.30,MAP,41.15,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.87,MAT,53.22,time,136
.848,rpm,0,ENGINE_LOAD,41.60,MAP,41.15,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
82,MAT,53.17,time,137.048,rpm,0,ENGINE_LOAD,41.30,MAP,41.08,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.96,MAT,53.38,ckp_c,0,fuel_base,5.02,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:697:time,137.248,rpm,0,ENGINE_LOAD,41.52,MAP,41.52,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.82,MAT,53.69,time,137.449,rpm,0,ENGINE_LOAD,41.15,MAP,41.15,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.46,MAT,53.48,time,137.649,rpm,0,ENGINE_LOA
D,41.15,MAP,41.08,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.01,MAT,52.86,time,137
.850,rpm,0,ENGINE_LOAD,41.23,MAP,41.30,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
91,MAT,52.81,time,138.050,rpm,0,ENGINE_LOAD,41.37,MAP,41.45,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.28,MAT,53.43,ckp_c,0,fuel_base,5.00,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:697:time,138.250,rpm,0,ENGINE_LOAD,41.00,MAP,40.86,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.78,MAT,53.80,time,138.449,rpm,0,ENGINE_LOAD,41.37,MAP,41.37,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.82,MAT,53.80,time,138.649,rpm,0,ENGINE_LOA
D,41.30,MAP,41.37,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.33,MAT,53.22,time,138
.850,rpm,0,ENGINE_LOAD,41.23,MAP,40.93,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
60,MAT,53.01,time,139.050,rpm,0,ENGINE_LOAD,41.30,MAP,41.30,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.60,MAT,53.54,ckp_c,0,fuel_base,5.04,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:959:time,139.250,rpm,0,ENGINE_LOAD,41.15,MAP,40.71,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,48.46,MAT,53.91,time,139.449,rpm,0,ENGINE_LOAD,41.30,MAP,40.86,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.23,MAT,53.59,time,139.649,rpm,0,ENGINE_LOA
D,41.15,MAP,41.00,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.19,MAT,54.01,time,139
.850,rpm,0,ENGINE_LOAD,41.37,MAP,41.23,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
82,MAT,53.59,time,140.050,rpm,0,ENGINE_LOAD,40.71,MAP,40.71,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.73,MAT,54.01,rusEfiVersion,20160131@9480 CUSTOM 140,outpin,
t1@PC6,outpin,t2@PA5,outpin,input1@NONE,outpin,input2@NONE,outpin,c1@PE14,outpin
,i1@PB9,outpin,c2@PC7,outpin,i2@PE2,outpin,c3@PC9,outpin,i3@PB8,outpin,c4@PE10,o
utpin,i4@PB7,ckp_c,0,fuel_base,4.97,fuel_lag,1.03,fuel,0.00,timing,11.80,duty0,N
aN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,duty1,NaN,dwell1,0.00
,total_dwell1,0.00,period1,0.00,advance1,NaN,msg,WARNING: Can't connect or mount
MMC/SD,
line:697:time,140.251,rpm,0,ENGINE_LOAD,41.30,MAP,41.30,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.96,MAT,53.48,time,140.451,rpm,0,ENGINE_LOAD,41.30,MAP,41.52,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.60,MAT,53.38,time,140.651,rpm,0,ENGINE_LOA
D,41.23,MAP,41.15,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.10,MAT,54.07,time,140
.850,rpm,0,ENGINE_LOAD,41.23,MAP,40.86,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.
19,MAT,54.01,time,141.050,rpm,0,ENGINE_LOAD,41.60,MAP,41.60,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.24,MAT,53.75,ckp_c,0,fuel_base,5.03,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,
line:697:time,141.251,rpm,0,ENGINE_LOAD,41.15,MAP,41.15,afr,10.01,ks,0.00,kv,0.0
0,TP,0.00,CLT,47.28,MAT,53.59,time,141.451,rpm,0,ENGINE_LOAD,41.23,MAP,41.37,afr
,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,47.78,MAT,53.48,time,141.651,rpm,0,ENGINE_LOA
D,41.23,MAP,41.30,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.23,MAT,53.43,time,141
.852,rpm,0,ENGINE_LOAD,41.60,MAP,41.60,afr,10.01,ks,0.00,kv,0.00,TP,0.00,CLT,48.
14,MAT,53.38,time,142.052,rpm,0,ENGINE_LOAD,41.30,MAP,41.30,afr,10.01,ks,0.00,kv
,0.00,TP,0.00,CLT,47.78,MAT,53.64,ckp_c,0,fuel_base,5.00,fuel_lag,1.03,fuel,0.00
,timing,11.80,duty0,NaN,dwell0,0.00,total_dwell0,0.00,period0,0.00,advance0,NaN,
duty1,NaN,dwell1,0.00,total_dwell1,0.00,period1,0.00,advance1,NaN,

Ian wrote:and PB1 O/C.

not sure what O/C means

makes no sense. any chance to try another computer with hopefully another version of java? what is your version of java? is that windows?

please install the jumper - this way there should be no text output. please hit t while in terminal.

O/C = PB1 to GND = open circuit (no jumper)

I am using windows 10. Java 1.8.0_66. tried the Microsoft and ST virtual serial port driver both work with TS. neither work with the Java Console.

with the jumper PB1 connected (PB1 to GND). both USB ports connected. Blue LED flashing at the slower rate.

Started the terminal emulator. press 't' result = "9480 ts_p_al" . what does this mean. ?

Ian wrote:press 't' result = "9480 ts_p_al" . what does this mean. ?

t is 'test' command. And we get a valid response with pretty recent 9480 firmware version. Do you want to install Jetbrains IDEA, Java JDK and let me in via teamviewer to see if I can debug this?

okay sounds like . I will all three first.. and get back to you.

you said "install Jetbrains IDEA, Java JDK and let me in via teamviewer to see if I can debug this?"

It may have to be tomorrow afternoon...

and then send you a teamviewer invite..

is this the correct version.. Download IntelliJ IDEA..

https://www.jetbrains.com/idea/download/#section=windows

?