Please make sure you read Rules! and DO NOT upload/post any illegal softwares or Pirated Material , Thank you for understanding :)
  1. Martech

  2. ATM - Balkan

    atm balkan file service
  3. Porsche piwis

  4. MOD FILES

  5. ProCarDiag

  6. ECU CHIPS

  7. NBE Files



Post Reply 
Ultimate Ediabas/ISTA+ voltage control V3
12-03-2017, 13:13 PM
Post: #31
RE: Ultimate Ediabas/ISTA+ voltage control V2
It is not the presentation of a voltage which is the problem, it is the firmware routine to measure the voltage
Find all posts by this user
Quote this message in a reply
12-03-2017, 13:19 PM (This post was last modified: 12-03-2017 14:34 PM by Node.)
Post: #32
RE: Ultimate Ediabas/ISTA+ voltage control V2
This is not for measuring. It can only tell yes/no. K+DCAN cables can't measure voltage (well, theoretically they could measure, but there is no protocol to tell a measured value to a computer using standart OBD cable driver). Even for measuring transistor connected as that I think would introduce big non-linearity with quite wide spread over transistor parameters. Why would someone do that in his right mind, I have no idea, I mean we don't need to measure milivolts here.
Find all posts by this user
Quote this message in a reply
12-03-2017, 15:58 PM
Post: #33
RE: Ultimate Ediabas/ISTA+ voltage control V2
My presentation was to show how the INPA (Ediabas sees the tension of the KL15 and Kl30)
Construction of interface K-dcan which measures the voltage on the real
KL15 and Kl30 not make sense,
  surely be cheaper to buy ICOM,
For k-dcan KL15 is only the state that the voltage ON or OFF
ISTA it should have options for VCI Ediabas KL15 ON or OFF
or, as here, a colleague did shows the tension that wynka deceive the terminal,
but actually it is only KL15 ON or OFF even though it shows some tension,

I wonder if omitec has functions to reading voltage directly works with ISTA
http://cartechnology.co.uk/showthread.php?tid=19713

to give interest.
I myself only has integrated interface K-dcan voltmeter with display
to see the voltage on pins Kl30 (4.5> 16) after replacing the housing k-can

If my post helped you hit the thanks and reputation button!under
Find all posts by this user
Quote this message in a reply
12-03-2017, 16:48 PM (This post was last modified: 12-03-2017 16:54 PM by Node.)
Post: #34
RE: Ultimate Ediabas/ISTA+ voltage control V2
K+DCAN interface which could read actual voltage would not be any more expensive as it is. If it has any MCU inside, most of them have internal ADC. And external components required are two resistors for minimum design. Premium design would include one more capacitor and, depending on MCU input properties, maybe a protection diode would be needed.
Now, if interface could read actual voltage it's not difficult to pass that to ISTA+ with some additional code. However ISTA+ itself does
not even try to read voltage via Ediabas functionality so it will not work with omitec or any other thing without outside help. Only ICOM is supported for that natively in ISTA+ and it uses another asynchronous IP communication channel for that (SDP protocol, I guess the same that IToolRadar uses to display info about ICOM state in the bottom window), different from the data channel.
What my updated dll does is it multiplexes requests from ISTA and my own voltage control code into single Ediabas' command sequence going into cable driver.
Find all posts by this user
Quote this message in a reply
 Thanks given by: dieseldog
12-03-2017, 18:09 PM (This post was last modified: 12-03-2017 18:11 PM by DNK76.)
Post: #35
RE: Ultimate Ediabas/ISTA+ voltage control V2
I have a schematic PCB terminals without DCAN
you can suggest additional elements pcb to monitor voltage
KL15


Attached File(s)
Schematic CAN interface.pdf
File Type: .pdf
Downloaded: 78 times
Size: 144.81 KB


If my post helped you hit the thanks and reputation button!under
Find all posts by this user
Quote this message in a reply
12-03-2017, 18:27 PM
Post: #36
RE: Ultimate Ediabas/ISTA+ voltage control V2
Looking at FT245BM datasheet it seems it was designed without any support for additional COM port signals. There is no way to do that without serious redesign.
Find all posts by this user
Quote this message in a reply
20-04-2017, 06:19 AM
Post: #37
RE: Ultimate Ediabas/ISTA+ voltage control V2
I cannot get this to work, ISTAgui.exe keeps crashing...

renamed c:\ediabas\bin\obd32.dll to ob23debas.dll
then copied all files from v2 zip file to c:\ediabas\bin

started then nothing happens, then tracked the ediabas.exe that is in the taskbar to d:\ISTA-D\ediabas\bin, so I then renamed that obd32.dll to obd32ebas.dll and copied the files there, then ISTAgui.exe crash once you identify via OBD.

can someone please tell me what im doing wrong. I have ISTA 4.03.31
Find all posts by this user
Quote this message in a reply
20-04-2017, 07:10 AM (This post was last modified: 20-04-2017 07:17 AM by snypertje.)
Post: #38
XZBMW RE: Ultimate Ediabas/ISTA+ voltage control V2
(20-04-2017 06:19 AM)Jakes300 Wrote:  I cannot get this to work, ISTAgui.exe keeps crashing...

renamed c:\ediabas\bin\obd32.dll to ob23debas.dll
then copied all files from v2 zip file to c:\ediabas\bin

started then nothing happens, then tracked the ediabas.exe that is in the taskbar to d:\ISTA-D\ediabas\bin, so I then renamed that obd32.dll to obd32ebas.dll and copied the files there, then ISTAgui.exe crash once you identify via OBD.

can someone please tell me what im doing wrong. I have ISTA 4.03.31

copy all files from v2 zip file to

C:\Rheingold\Ediabas\Bin

rename existing obd32.dll to obd32.ebas.dll.
wink

Software works perfectly!!rock
Find all posts by this user
Quote this message in a reply
20-04-2017, 14:37 PM (This post was last modified: 20-04-2017 14:42 PM by Jakes300.)
Post: #39
RE: Ultimate Ediabas/ISTA+ voltage control V2
That's how I copied it now, still getting ISTAgui.exe stopped working....

extract from logs...

Application: ISTAGUI.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Runtime.InteropServices.SEHException at <Module>.AcquireValues(Boolean*, UInt16*, Boolean*, UInt16*, Int32*) at NodeISTAVoltageControl.Controller.OnTimer(System.Object, System.EventArgs) at System.Windows.Threading.DispatcherTimer.FireTick(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Obje​ct) at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext,​ System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingE​xecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.Di​spatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.Dispa​tcherFrame) at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.Dispatche​rFrame) at System.Windows.Window.ShowHelper(System.Object) at System.Windows.Window.Show() at System.Windows.Window.ShowDialog() at BMW.Rheingold.PresentationFramework.DialogBase.ShowDialog() at BMW.Rheingold.PresentationFramework.MessageDialog+<>c__DisplayClass14_0.<Show>b__0() at BMW.Rheingold.CoreFramework.Extensions.InvokeIfNoAccess(System.Windows.Threading​.Dispatcher, System.Action) at BMW.Rheingold.PresentationFramework.MessageDialog.Show(BMW.Rheingold.CoreFramewo​rk.Message) at BMW.Rheingold.PresentationFramework.CommandBase.Execute(System.Object) at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(System.Windows.​Input.ICommandSource, Boolean) at System.Windows.Controls.Primitives.ButtonBase.OnClick() at System.Windows.Controls.Button.OnClick() at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows​.Input.MouseButtonEventArgs) at System.Windows.UIElement.OnMouseLeftButtonUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs) at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent) at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs) at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs) at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventAr​gs) at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputRep​ort) at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32) at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.Di​spatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.Dispa​tcherFrame) at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.Dispatche​rFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at System.Windows.Application.Run(System.Windows.Window) at BMW.Rheingold.ISTAGUI.App.Main()
Find all posts by this user
Quote this message in a reply
20-04-2017, 14:57 PM
Post: #40
RE: Ultimate Ediabas/ISTA+ voltage control V2
So what did you actually rename it to? In one place you say ob23debas.dll, another obd32ebas.dll when it should be obd32.ebas.dll
Reputation: +1 - intel123 [+1]
Find all posts by this user
Quote this message in a reply
Post Reply 


Bookmarks

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
XZBMW ISTA-P (3.63.0.400) - MEGA in shawnsheridan 50 4,838 Yesterday 21:36 PM
Last Post: CarlosF11
XZBMW ISTA-D 4.08.21 Standalone / SQLiteDBs 4.08.20 in spider80 51 4,356 Yesterday 21:19 PM
Last Post: Gatsby79
XZBMW Release Notes ISTA-P_3.63.1_4.08.2x_ENG in Czozen 3 207 Yesterday 18:18 PM
Last Post: shawnsheridan
XZBMW ISTA/P Loader 6.1F (Rev1) in beemerboy88 102 33,852 Yesterday 12:01 PM
Last Post: Node
XZBMW ISTA/P Loader V6.3 Lite in beemerboy88 90 18,116 20-11-2017 23:36 PM
Last Post: kmbeatz
  Error in ISTA when calculating measures plans in dracon 7 313 20-11-2017 18:26 PM
Last Post: dracon
XZBMW [SOLVED] E91 N43 Engine malfunction - reduced power after ISTA-P 3.59.2.001 flashing in CarlosF11 30 5,707 20-11-2017 16:24 PM
Last Post: ayerkn
XZBMW ENET Cable not showing Voltage in EasyConnect in mcrussell 6 278 19-11-2017 19:54 PM
Last Post: sebastianfernandes
XZBMW Ista instaler in pdc 2 254 19-11-2017 08:39 AM
Last Post: pdc
XZBMW ISTA-P (3.62.0.500 - 3.62.1.003) - Mega in shawnsheridan 33 4,871 19-11-2017 05:23 AM
Last Post: BMWLorenz

Forum Jump:


User(s) browsing this thread:
1 Guest(s)

Return to TopReturn to Content