Release ED-Intelligent Boardcomputer Extension

Well I have only RN running. I can export the CSV if it helps.

From what I found, it is not related to EDDN ;)

Here is my log for coffee:
Code:
[COLOR=#000000][FONT=Courier New]         | Receiving commodity-v1 message...         |     - Converting to v2...         |     - Software: RegulatedNoise__DJ / v1.84_0.25         |         - AUTHORISED         |     - Checking System: Jeterait         |         - System found: 10107         |     - Checking Station: Barnard Port         |         - Station found: 10791         |     - Checking Commodities:         |         - Checking commodity: Coffee         |             - Commodity found: 15         |         - Updating commodity price         |             - Sell Price: 1351         |             - Demand: 7958[/FONT][/COLOR]

And the EDDN message:
Code:
{    "header": {
        "softwareVersion": "v1.84_0.25",
         "gatewayTimestamp": "2015-06-02T21:22:34.727186",
         "softwareName": "RegulatedNoise__DJ",
         "uploaderID": "Carrahaar"
    },
     "$schemaRef": "http://schemas.elite-markets.net/eddn/commodity/1",
     "message": {
        "buyPrice": 0,
         "timestamp": "2015-06-02T23:22:00+02:00",
         "stationStock": 0,
         "systemName": "Jeterait",
         "stationName": "Barnard Port",
         "demand": 7958,
         "sellPrice": 1351,
         "itemName": "Coffee"
    }
}
[FONT=Verdana]

RN seems to put you with a -1 ^^[/FONT]
 
From what I found, it is not related to EDDN ;)

Here is my log for coffee:
Code:
[COLOR=#000000][FONT=Courier New]         | Receiving commodity-v1 message...         |     - Converting to v2...         |     - Software: RegulatedNoise__DJ / v1.84_0.25         |         - AUTHORISED         |     - Checking System: Jeterait         |         - System found: 10107         |     - Checking Station: Barnard Port         |         - Station found: 10791         |     - Checking Commodities:         |         - Checking commodity: Coffee         |             - Commodity found: 15         |         - Updating commodity price         |             - Sell Price: 1351         |             - Demand: 7958[/FONT][/COLOR]

And the EDDN message:
Code:
{    "header": {
        "softwareVersion": "v1.84_0.25",
         "gatewayTimestamp": "2015-06-02T21:22:34.727186",
         "softwareName": "RegulatedNoise__DJ",
         "uploaderID": "Carrahaar"
    },
     "$schemaRef": "http://schemas.elite-markets.net/eddn/commodity/1",
     "message": {
        "buyPrice": 0,
         "timestamp": "2015-06-02T23:22:00+02:00",
         "stationStock": 0,
         "systemName": "Jeterait",
         "stationName": "Barnard Port",
         "demand": 7958,
         "sellPrice": 1351,
         "itemName": "Coffee"
    }
}


RN seems to put you with a -1 ^^

:(((

Thanks for looking into it!
In the meanwhile I erased the database and so far everything looks to be okay.
 
It seems that the "Station" information has disappeared from the log files now that v1.3 has gone live.
Not a big problem, just makes the "Commanders Log" isnt as good.
 
i have had to install rn , on another pc, everything seems to work as should except in calibration, it just says error , so i can't calibrate ,, ???????
i can still hit f10 and ocr dose its job ,,,
 
haven't used regulated noise for a while as I was out exploring. I now get implausible results almost every time I OCR despite the scanned values being correct. I don't upload to EDDN. Can I just turn this function off?? or can someone explain is child like english what is the correct way edit the upper and lower values ?


UPDATE - Don't worry seemed to have sorted it out ;)
 
Last edited:
I checked the ED 1.3 and I unfortunately ascertained
that there's no longer a information about the current location (e. G. station, ring...) in the logfiles.
It seems that the devs have kicked this information out of the logfiles.

Solution: sorry, no idea at the moment :mad:
 
I checked the ED 1.3 and I unfortunately ascertained
that there's no longer a information about the current location (e. G. station, ring...) in the logfiles.
It seems that the devs have kicked this information out of the logfiles.

Solution: sorry, no idea at the moment :mad:

Maybe start some of those help files , calibration ones ie the pricing -1 , pictures arrows, simple words, for the those of us who hate thinking too much :D, a change of pace for you, saves pulling your hair out on the 1.3 update ,
EDIT
Just remembered ,, AER , can be told ( by you) to set your current system... maybe that's way of getting the information into RN , I assume you would have to tell AER this,every time you jumped/moved systems.
 
Last edited:
how do you actually edit the commodity check price list? Ie to check if the price is out of what is normal? It seems with the new PP a lot of prices are different and i get notifications all the time.
 
there's no auto-update function at the moment. The warnlevels are one-time calculated
from the data\stations.json on first start of RN. But you can force a recalculation
by deleting "data\commodities_RN.json". On next start RN will recalculate the warnlevels.
If you get the latest prices (means the latest "station.json") from the EDDB website
before deleting "data\commodities_RN.json" you have new warnlevels.

Manually editing of warnlevels is possible on the settings tab (bottom right)
 
Last edited:
I checked the ED 1.3 and I unfortunately ascertained
that there's no longer a information about the current location (e. G. station, ring...) in the logfiles.
It seems that the devs have kicked this information out of the logfiles.

Solution: sorry, no idea at the moment :mad:

So back to OCR for the station names, then?
 
I checked the ED 1.3 and I unfortunately ascertained
that there's no longer a information about the current location (e. G. station, ring...) in the logfiles.
It seems that the devs have kicked this information out of the logfiles.

Solution: sorry, no idea at the moment :mad:

I think I am misunderstanding what you posted. I am using the latest version of RN and all my scans are going to the right places and Commanders log is showing my journeys. Unless this changed overnight because I forgot to run RN this morning. It was certainly working yesterday, 6th June, up to 16:30 at least.

What I did notice was that the price of Narcotics has gone through the roof in 1.3 so I had to manually change the warning levels.
 
I think I am misunderstanding what you posted. I am using the latest version of RN and all my scans are going to the right places and Commanders log is showing my journeys. Unless this changed overnight because I forgot to run RN this morning. It was certainly working yesterday, 6th June, up to 16:30 at least.

What I did notice was that the price of Narcotics has gone through the roof in 1.3 so I had to manually change the warning levels.

there are no "Visited" events logged anymore - only "Market Data Collocted"
and also the system data doesn't show the current station automatically.

So back to OCR for the station names, then?

should already work
 
Last edited:
there's no auto-update function at the moment. The warnlevels are one-time calculated
from the data\stations.json on first start of RN. But you can force a recalculation
by deleting "data\commodities_RN.json". On next start RN will recalculate the warnlevels.
If you get the latest prices (means the latest "station.json") from the EDDB website
before deleting "data\commodities_RN.json" you have new warnlevels.

Manually editing of warnlevels is possible on the settings tab (bottom right)

That worked to some extent but still getting problems and i don't fully understand how or rather what i should be editing when editing the warnlevels. Could you write a little guide or such you think?
I know where i do it but not what to edit.
 
its not overly difficult, presuming u already know how to get to the location to edit ...

look at the prob , and edit the value needed... E.G today i found a station with an issue with basic meds .. the warning showed for high sell price.The sell price was 446cr with the galactic average was 365cr, checked the sell price high warning , its set at about 370, i simple changed it to 450 and clicked save, problem solved.

you will encounter this a lot if you do trade CG's, as the prices they pay you are way higher then the average, at least at the start of the CG.
 
its not overly difficult, presuming u already know how to get to the location to edit ...

look at the prob , and edit the value needed... E.G today i found a station with an issue with basic meds .. the warning showed for high sell price.The sell price was 446cr with the galactic average was 365cr, checked the sell price high warning , its set at about 370, i simple changed it to 450 and clicked save, problem solved.

you will encounter this a lot if you do trade CG's, as the prices they pay you are way higher then the average, at least at the start of the CG.

My problem is i'm not sure what to edit, if it's the sell price or what else.. i sort of easily get slightly confused when there are a lot of numbers :p
 
First thing to do is to look at the implausable result and make sure its not just an OCR error. I.E it miss read (or missed totaly) a number, that easy to compare, just type in the correction and thats done.

Now assuming you check it, and all is in order, click the edit button

lets use the figures, you have scanned basic meds with a sell price of 450cr

and the warn lvls of Supply Sell Low 250 and Supply Sell high 380

instantly you can see the cause the scanned price is way above the 380 of the high value. Simple change the Supply Sell High to say... 460 and it wont happen again (unless the market goes over that in the future)

The most common problem you will find is the Supply Sell High (how much your going to earn from selling) and the Supply Buy Low (how much your going to charged to purchase) You can pretty much ignore the 4 Demand colums which pretty much only get set off with a bad ocr scan (miss reading of numbers)

You can use -1 as a value for it to ignore a value (DONT use that for prices) if you get weird or vastly changeing quantities, but it should be reserved for things that have huge range changes (and mostly valueless) like say.. chemical waste
 
First thing to do is to look at the implausable result and make sure its not just an OCR error. I.E it miss read (or missed totaly) a number, that easy to compare, just type in the correction and thats done.

Now assuming you check it, and all is in order, click the edit button

lets use the figures, you have scanned basic meds with a sell price of 450cr

and the warn lvls of Supply Sell Low 250 and Supply Sell high 380

instantly you can see the cause the scanned price is way above the 380 of the high value. Simple change the Supply Sell High to say... 460 and it wont happen again (unless the market goes over that in the future)

The most common problem you will find is the Supply Sell High (how much your going to earn from selling) and the Supply Buy Low (how much your going to charged to purchase) You can pretty much ignore the 4 Demand colums which pretty much only get set off with a bad ocr scan (miss reading of numbers)

You can use -1 as a value for it to ignore a value (DONT use that for prices) if you get weird or vastly changeing quantities, but it should be reserved for things that have huge range changes (and mostly valueless) like say.. chemical waste

Thanks :)
 
The program now crashes when i start it up. If I let it run for a while it will eventually start, but when I actually use it (using price analysis, or using the ORC interface amongst others) it crashes again. Seems like it doesn't really work anymore now with Powerplay. Anybody else ran into problems since the patch?
 
Last edited:
Back
Top Bottom