[Almaretto]

@fanboy130: never was a fan of these "codingapps". For low level users, okay, but for the most here to "simple".
I know only 2 coding apps for iOS, but both are not able to write custom Hex.

Regards,

I am currently testing a "Pro" feature in my app, which allows you to do FDL coding just like you would with E-Sys. The app restricts values to not exceed the bit mask like E-Sys does at the moment, but I just could deactivate that feature for testing. Could someone send me the NBT ncd so I can have a look at the coding data? I would test myself, but I only have a 1st gen NBT.

You can generate any NCD your want with E-sys Coding-Verification. What do you mean by 1st gen NBT? Do you mean you are looking for HU_NBT2 (AKA HU_NBT_EVO)?

[fanboy130]

@fanboy130: never was a fan of these "codingapps". For low level users, okay, but for the most here to "simple".
I know only 2 coding apps for iOS, but both are not able to write custom Hex.

Regards,

I am currently testing a "Pro" feature in my app, which allows you to do FDL coding just like you would with E-Sys. The app restricts values to not exceed the bit mask like E-Sys does at the moment, but I just could deactivate that feature for testing. Could someone send me the NBT ncd so I can have a look at the coding data? I would test myself, but I only have a 1st gen NBT.

You can generate any NCD your want with E-sys Coding-Verification. What do you mean by 1st gen NBT? Do you mean you are looking for HU_NBT2 (AKA HU_NBT_EVO)?

I have a HU_NBT in my car. I had a look into the CAFD and the missing two bits are not occupied by any other function, so one could just edit the raw ncd, update the checksums and the signature (if necessary) like described here or if anyone has an iOS device available try it with an enhanced version of my app.

[chris8868]

Hu_nbt2 is: cafd_00001ef6_006_020_007.ncd

[fanboy130]

Hu_nbt2 is: cafd_00001ef6_006_020_007.ncd

Thanks, just found it myself

[Almaretto]

I am currently testing a "Pro" feature in my app, which allows you to do FDL coding just like you would with E-Sys. The app restricts values to not exceed the bit mask like E-Sys does at the moment, but I just could deactivate that feature for testing. Could someone send me the NBT ncd so I can have a look at the coding data? I would test myself, but I only have a 1st gen NBT.

You can generate any NCD your want with E-sys Coding-Verification. What do you mean by 1st gen NBT? Do you mean you are looking for HU_NBT2 (AKA HU_NBT_EVO)?

I have a HU_NBT in my car. I had a look into the CAFD and the missing two bits are not occupied by any other function, so one could just edit the raw ncd, update the checksums and the signature (if necessary) like described here or if anyone has an iOS device available try it with an enhanced version of my app.

Then HU_NBT is no different whether from 2013 or 2016 (ie both (CAFD_00000DED). See this PDF.

Unless your app calculates for user, then checksum & signature would have to be updated.

How is vehicle communicating with IOS device?

[Hermi]

Got all the stuff here, ICOM, enet, wifi-dongles etc.
But same question like Almaretto, what interface is necessary? Special one?
Checksum & signature is the problem at the moment for these "developer signed .ncd's.

@fanboy130 If you want, you can pm me the name of your app.

[fanboy130]

The app is working with a generic WiFi OBD adapter, but since the Vgate adapters seem to be the most reliable, I restricted the app to work with the iCar 2 and 3 devices.

[fanboy130]

When no one is interested in testing the iOS app, you could just send me your ncd and I could alter it with the FF value for the speed lock and update the checksums and the signature.

[NeRkO20]

Sorry, I would..but I never used apple products and I will never...so I am not really a help

.:: Gesendet von meinem Galaxy S7 ::.

[Hermi]

@fanboy130 please pm me some details.


Regards,