Release ED-Intelligent Boardcomputer Extension

Hi Duke

Looking forward to the next release, which I hope works with v2.4 - I get Companion IO server not accessible ! message - drop down reports cannot comply companion interface not ready
 
Hi, the next release will come. But v0.6.6. IS working with v2.4. The problem is on the server side - no third party tool (EDMC, EDDI, ....) is working fully (cAPI) at the moment.
But FD is aware of this - see also here

Duke


Edit: Made out that v0.6.6 is not running on ED2.4 without problems but I'm working on it.
I expect the release of a new ED-IBE today (Oct, 6th) or tomorrow.
 
Last edited:
Hi Juke

I tried 0.7 but got an error message

06.10.2017 20:14:59 : ED-IBE v0.7.0.0
06.10.2017 20:14:59 : Unhandled Exception
--------------------------------------------------------------------------------
06.10.2017 20:14:59 : Error while getting data from the servers
06.10.2017 20:14:59 : at IBE.IBECompanion.CompanionData.GetProfileData(Boolean useCachedData) in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionData.cs:line 222
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
--------------------------------------------------------------------------------
06.10.2017 20:14:59 : Unexpected character encountered while parsing value: *. Path 'market', line 1, position 35168.

Can you point me in any direction?

The exception log also had:


06.10.2017 20:15:01 : 06.10.2017 20:15:01 : ED-IBE v0.7.0.0
06.10.2017 20:15:01 : Error in Form_Shown
--------------------------------------------------------------------------------
06.10.2017 20:15:01 : Error while showing status infos
06.10.2017 20:15:01 : at IBE.Form1.ShowStatus() in E:\dev\RN\ED-IBE\ED-IBE\Form1.cs:line 3854
at IBE.Form1.<Form_Shown_async>d__117.MoveNext() in E:\dev\RN\ED-IBE\ED-IBE\Form1.cs:line 1334
--------------------------------------------------------------------------------
06.10.2017 20:15:01 : Error while checking if landed
06.10.2017 20:15:01 : at IBE.IBECompanion.CompanionData.IsLanded() in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionData.cs:line 370
at IBE.Form1.ShowStatus() in E:\dev\RN\ED-IBE\ED-IBE\Form1.cs:line 3732
--------------------------------------------------------------------------------
06.10.2017 20:15:01 : Error while getting typed data value
06.10.2017 20:15:01 : at IBE.IBECompanion.CompanionData.GetValue[T](String valuePath) in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionData.cs:line 276
at IBE.IBECompanion.CompanionData.IsLanded() in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionData.cs:line 366
--------------------------------------------------------------------------------
06.10.2017 20:15:01 : Null object cannot be converted to a value type.
06.10.2017 20:15:01 : at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
at IBE.IBECompanion.CompanionData.GetValue[T](String valuePath) in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionData.cs:line 272

********************************************************************************

My install directory is C:\ED-IBE

Cheers
 
Last edited:
Hi,

please stop IBE and try to remove the "CompanionProfile_*.dat" files from your data directory.
(Assuming they are in C:\Users\<USERNAME>\AppData\Local\ED-IBE\ in your case)
Then start IBE and reconnect to the companion servers.
 
Hi Duke

I located the companion in my C:\ED-IDE - I did not have anything in the user directory - removing this forced me to verify my account - I generated the request - received the code and entered it - immediately the sotware crashed with:

06.10.2017 21:39:43 : ED-IBE v0.7.0.0
06.10.2017 21:39:43 : Error in cmdVerify_Click
--------------------------------------------------------------------------------
06.10.2017 21:39:43 : Error while getting current state
06.10.2017 21:39:43 : at IBE.IBECompanion.CompanioDataView.GetState() in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionDataView.cs:line 164
at IBE.IBECompanion.CompanioDataView.cmdVerify_Click(Object sender, EventArgs e) in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionDataView.cs:line 210
--------------------------------------------------------------------------------
06.10.2017 21:39:43 : Error while getting data from the servers
06.10.2017 21:39:43 : at IBE.IBECompanion.CompanionData.GetProfileData(Boolean useCachedData) in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionData.cs:line 222
at IBE.IBECompanion.CompanioDataView.GetState() in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionDataView.cs:line 68

What can I try next? I do not use E:\Dev folder - so does not exist.
 
I will check this.

But I've heard from other users, who still have problems connecting to the companion servers (also with EDMC etc.)
It seems to depend on the account itself.
You may check if EDMC also have trouble with your account ?

Edit: btw: "E:\Dev" is a debug information which comes from my system. Don't matter.

Edit2: There are not more debug-infos ?
Please look into the /Logs/ subfolder and send the relevant files (look on the timestamp when they'va changed the last time)
Maybe you should remove the *.dat files again, reconnect the cApi and let IBE crash - then send the files to me.



Edit 3:
@The Weasel:

Hi,

please download the version v0.7.0_D1 from Github.

Start it and doubleclick on the "Docked" LED.
A new menu "Debug" will appear.
Check "enable logging for journal messages" .

If you can't start ED-IBE delete the Companion*.dat files from your data folder.
You will need to connect to the Comapanion server again on the next start, but you will be able to start.

After that there should be a "App_*.log" in the "/Logs/" subfolder
which contains the recieved string from the servers which causes the crash.

Please send me this log and the exception log (duke.jones (ät) gmx.de )

Thank you very much.

Duke

PS: be sure to uncheck "enable logging for journal messages" after you've finished.
 
Last edited:
Hi Duke

Downloaded 0.7.0_D1 - installed - removed Companion*.dat from the ED-IBE folder - restarted - activated debug and logging journal messages - checked EDDM & EDSM appear all OK - confirmed active and connected. When I tried to connect to ED - I entered the password hit connect - immediate crash - will send logs @ duke.

Since then every time I try to open and click on IO - I get an immediate crash

07.10.2017 18:15:06 : ED-IBE v0.7.0.0
07.10.2017 18:15:06 : Error in CompanioDataView_Load
--------------------------------------------------------------------------------
07.10.2017 18:15:06 : Error while getting current state
07.10.2017 18:15:06 : at IBE.IBECompanion.CompanioDataView.GetState() in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionDataView.cs:line 164
at IBE.IBECompanion.CompanioDataView.CompanioDataView_Load(Object sender, EventArgs e) in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionDataView.cs:line 36
--------------------------------------------------------------------------------
07.10.2017 18:15:06 : Error while getting data from the servers
07.10.2017 18:15:06 : at IBE.IBECompanion.CompanionData.GetProfileData(Boolean useCachedData) in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionData.cs:line 225
at IBE.IBECompanion.CompanioDataView.GetState() in E:\dev\RN\ED-IBE\ED-IBE\IBECompanion\CompanionDataView.cs:line 68

If I delete the Companion*.dat - it will open ok [Message banner - not initialised] all seems OK - I enter user / pwd until I hit connect then crashes immediately.

The dumpfile for the error is 500Mb - so I just added the text from the exception.

Thanks for help with this.
 
Please try v0.7.0_D2
Hoping this works better.


Edit :
It'd be great if somebody gave me some feedback on the D2.
Is the Problem solved or not solved ?
 
Last edited:
I am playing around with this app, and have it setup on a second PC. I came up with a workaround for the hardcoded journal location issue. The answer is to use a symbolic directory link to mount the location of the journals on the PC with ED installed.

1. Go to Saved Games on the PC with ED installed and share the folder called Frontier Developments. This folder will contain a number of log files. The share name should be "Frontier Developments" (without the quote marks). You will need to know the network name of the PC with ED installed. You might want to change it to something more memorable.
2. On the PC with ED-IBE installed, open a command prompt with admin privileges.
3. You will need to know the location of your Saved Games folder on the ED-IBE PC. It is normally C:\Users\<your user name>\Saved Games
4. In the command prompt windows type the following (ensuring you use the paths specific your situation) mklink /d "c:\users\<your user name>\saved games" "\\<pc server>\Frontier Developments". The quote marks are important, as it allows you to use names with spaces in them.
5. This should create a folder in your saved games location on the ED-IBE PC that links to the location of the journal files on the ED PC, and allow ED-IBE to find the log files.
6. You can use standard network drive mapping for the location of the other folders ED-IBE needs to access.

I hope this helps. I know it is a bit terse. If anyone is interested I could write a more user-friendly set of instructions in the next few days.
 
Hi ive been using this for a while but im currently having issues with what seems to be the min.supply/stock tick box not working I have a tick in the box and a value of 242 t but the search results are still bringing up commodities with zero supply in a station to station search is there anything you could advise to correct this or is it a known bug any help would be appreciated from anyone but big thanks to the developer for time spent on this awesome tool
 
Sorry for the stupid question but what is the difference between ED-I and MK II please ?

No sarcasm in my question, just wondering as i am heavy user of MK2.

thanks and good work it seems.
 
@Steviec: Can you post a screenshot please ?
@Deareim: This should answer anyone who has used both tools....I havn't....
 
thanks for taking the time to have a look appreciated

OaGUb4p.jpg
 
thanks for taking the time to have a look appreciated

I've seen the zero supply entries often too too and what I've been able find out so far is that ED-IBE does not seem to select the commodities corresponding to the route selected on the right: it just apparently selects the highest profit commodity for each station regardless of if there is any supply at all or of the supply is less than set int the query options. If you select on the left a commodity (for the corresponding station) with supply large enough for your query, you'll see that that is the commodity actually used to calculate the route profit on the right side. It is quite confusing though, to even show the commodities with too small (ore zero) supply...

Another problem I've noticed in the quite short time I've been usign ED-IBE so far is that I think there is a simple flaw in the logic ED-IBE imports the commodity updates from EDDN (at least for EDMC): ED-IBE only seems to update price/supply values that are reported to EDDN - it does not seem remove commodities that do not exist on the station anymore (EDMC does not report price/supply for every and each commodity in existence every time you land on a station. EDMC as far as I know, only reports the commodities it can find on a station: there is no way it even could reliably report commodities that were there, but are there no longer (unless of course you had been there recently yourself running EDMC). I've already seen this problem several times with my quite brief experience with ED-IBE, so it's hardly anything rare, either. It seems even to be of no use to go and "verify" the markets (and update EDDB/EDDN with EDMC) with a "courier ship" and only after that going in with a trader, because only reported commodities seem ever to be updated in ED-IBE.

The remove old market data/no more existing commodities does not seem to do the work completely either: the zero supply commodities do not always seem to be removed ( I can't even understand why they both would need a number of days for the job, anyway: if the commodities are not there, just remove them, regardless of the age of the latest update). Ticking "do this every time for a station when getting new data (maybe it does not even apply to EDDN updates). In any case the data in ED-IBE database does not seem to stay up-to-date even when running the EDDN listener. This seems, unfortunately, to make ED-IBE much less useful as a trading tool, in my opinion. YMMV.
 
Back
Top Bottom