ASAM/ROD updates through the USB utility
- Thread starter jyoung8607
- Start date
- Status
It lays there until I close the utility.
Previously it was in a loop update -> done -> needs update, etc.
Edit: Checked again and it won't show up in the utility again until power is removed and re-attached.
Edit 2: Ok here's a new behaviour after reboot and checking again:
When the update hangs, is the HEX-NET mounted to the computer as a drive? If so, can you copy the file /rodlist from it and send it to me.
If I recall correctly, you mentioned seeing a "this drive was not removed correctly" type message at one point. Do you see a file system type warning like this often when doing the update?
--Shaun
If I recall correctly, you mentioned seeing a "this drive was not removed correctly" type message at one point. Do you see a file system type warning like this often when doing the update?
--Shaun
Sometimes it mounts and sometimes it doesn't.
A few tries and I got the files.
I get that warning every time the USB utility is used.
rodlist
rodlist-2
A few tries and I got the files.
I get that warning every time the USB utility is used.
rodlist
Code:
,4,EV_AdaptCruisContr2AU64X,WAURVAFD6CN014370,4H0-907-541-A,1398879865
,4,EV_ECM42FSI0114H0907560C,,4H0-907-560-C,1398879865
EV_GatewUDS_AU57.rod,5,EV_GatewUDS,WAURVAFD6CN014370,4H0-907-468-F,1398879865
,4,EV_TCMALX51011,,4H1-927-158-BR,1398879865
EV_ESPPremi_AU64.rod,5,EV_ESPPremi,,4H0-907-379-C,1398879865
EV_AirCondiFront_AU64.rod,5,EV_AirCondiFront,WAURVAFD6CN014370,4H0-820-043-H,1398879865
EV_EPHVA18AU57X0000.rod,5,EV_EPHVA18AU57X0000,WAURVAFD6CN014370,4H0-919-475-L,1398879865
,4,EV_AdaptCruisContrAU64X,WAURVAFD6CN014370,4H0-907-561-A,1398879865
,4,EV_AirbaAU10BPAAU64X,WAURVAFD6CN014370,4H0-959-655-D,1398879865
,4,EV_RBD4K,WAURVAFD6CN014370,4H0-920-980-H,1398879865
,4,EV_AirCondiHeck,WAURVAFD6CN014370,4H0-919-158-D,1398879865
EV_AirSuspe_AU64.rod,5,EV_AirSuspe,WAURVAFD6CN014370,4H0-907-553-C,1398879865
EV_SARA.rod,5,EV_SARA,WAURVAFD6CN014370,4H0-907-637,1398879865
,0,EV_DeckLidContrUnit,WAURVAFD6CN014370,4H0-959-107-R,1398879865
,4,EV_Ambie,WAURVAFD6CN014370,4H0-907-412,1398879865
,4,EV_GSM2x3Mono,WAURVAFD6CN014370,4H1-927-731-A,1398879865
,4,EV_OnBoardCamerDPC,WAURVAFD6CN014370,4G0-907-217,1398879865
EV_IVBDriveSideFrnt.rod,5,EV_IVBDriveSideFrnt,WAURVAFD6CN014370,4H0-907-182-H,1398879865
EV_IVBDriveSideFrnt.rod,5,EV_IVBPasseSideFrnt,WAURVAFD6CN014370,4H0-907-182-H,1398879865
EV_IVBDriveSideFrnt.rod,5,EV_IVBDriveSideRear,WAURVAFD6CN014370,4H0-907-182-G,1398879865
,4,EV_IVBPasseSideRear,WAURVAFD6CN014370,4H0-907-182-G,1398879865
EV_BC7.rod,5,EV_BC7,WAURVAFD6CN014370,4G0-907-107-C,1398879865
,0,EV_RGS_L,WAURVAFD6CN014370,4H0-980-945-B,1398879865
EV_RGS_R.rod,5,EV_RGS_R,WAURVAFD6CN014370,4H0-980-946-B,1398879865rodlist-2
Code:
,4,EV_AdaptCruisContr2AU64X,WAURVAFD6CN014370,4H0-907-541-A,1398879865
,4,EV_ECM42FSI0114H0907560C,,4H0-907-560-C,1398879865
EV_GatewUDS_AU57.rod,5,EV_GatewUDS,WAURVAFD6CN014370,4H0-907-468-F,1398879865
,4,EV_TCMALX51011,,4H1-927-158-BR,1398879865
EV_ESPPremi_AU64.rod,5,EV_ESPPremi,,4H0-907-379-C,1398879865
EV_AirCondiFront_AU64.rod,5,EV_AirCondiFront,WAURVAFD6CN014370,4H0-820-043-H,1398879865
EV_EPHVA18AU57X0000.rod,5,EV_EPHVA18AU57X0000,WAURVAFD6CN014370,4H0-919-475-L,1398879865
,4,EV_AdaptCruisContrAU64X,WAURVAFD6CN014370,4H0-907-561-A,1398879865
,4,EV_AirbaAU10BPAAU64X,WAURVAFD6CN014370,4H0-959-655-D,1398879865
,4,EV_RBD4K,WAURVAFD6CN014370,4H0-920-980-H,1398879865
,4,EV_AirCondiHeck,WAURVAFD6CN014370,4H0-919-158-D,1398879865
EV_AirSuspe_AU64.rod,5,EV_AirSuspe,WAURVAFD6CN014370,4H0-907-553-C,1398879865
EV_SARA.rod,5,EV_SARA,WAURVAFD6CN014370,4H0-907-637,1398879865
,0,EV_DeckLidContrUnit,WAURVAFD6CN014370,4H0-959-107-R,1398879865
,4,EV_Ambie,WAURVAFD6CN014370,4H0-907-412,1398879865
,4,EV_GSM2x3Mono,WAURVAFD6CN014370,4H1-927-731-A,1398879865
,4,EV_OnBoardCamerDPC,WAURVAFD6CN014370,4G0-907-217,1398879865
EV_IVBDriveSideFrnt.rod,5,EV_IVBDriveSideFrnt,WAURVAFD6CN014370,4H0-907-182-H,1398879865
EV_IVBDriveSideFrnt.rod,5,EV_IVBPasseSideFrnt,WAURVAFD6CN014370,4H0-907-182-H,1398879865
EV_IVBDriveSideFrnt.rod,5,EV_IVBDriveSideRear,WAURVAFD6CN014370,4H0-907-182-G,1398879865
,4,EV_IVBPasseSideRear,WAURVAFD6CN014370,4H0-907-182-G,1398879865
EV_BC7.rod,5,EV_BC7,WAURVAFD6CN014370,4G0-907-107-C,1398879865
,0,EV_RGS_L,WAURVAFD6CN014370,4H0-980-945-B,1398879865
EV_RGS_R.rod,5,EV_RGS_R,WAURVAFD6CN014370,4H0-980-946-B,1398879865
Last edited:
And back to my question:
Assuming I've scanned it in the past, no modules got their module sex on and made new baby modules... shouldn't an update at my desk [edit: via the web interface] do just that ?
Assuming I've scanned it in the past, no modules got their module sex on and made new baby modules... shouldn't an update at my desk [edit: via the web interface] do just that ?
- Joined
- Feb 25, 2014
- Messages
- 2,780
- Reaction score
- 4,490
- Location
- Cincinnati, OH
- VCDS Serial number
- C?ID=25607
Probably yes. I think we're getting to the bottom of the mystery. The USB utility "rod update" process is working off the very same dynamic queue of ROD requests as the Mobile web UI ASAM/ROD downloader. So in terms of design, those data are indeed available both OTA and USB. The Mobile web UI and the USB update utility should be in complete agreement on whether you're up to date (except the CFB and Boot objects).
In reality, neither the OTA nor the USB update process seem bulletproof yet. I'm sure that will get sorted out in due time. In the meantime, we have our answer. If OTA says we're up to date but USB says we're not, that ain't a feature -- that's a bug.
I wonder if you cleared your ASAM data cache from the Mobile Options menu, if it would get you past this hung state with the USB updater? Don't do it just yet, without the go-ahead from Shaun, because that will definitely change the internal state of your HN that he's trying to troubleshoot.
Jason
"Except CFB and Boot" means one of these things is not like the other, or not as capable yet.
See above.
Got that corn cob soaking in kerosene don't ya Jason ?
Took me three days and umpteen tries to get all that re-downloaded last time with all the skipped modules and getting dumped back to login during scans
That's how we discovered that if a scan is identical it won't overwrite the old one.
If VCDS Classic has all the data it should be able to transfer it during a cabled scan...
Pretty sure I know which lamp post to park next to at the grocery store to get a stable enough connection to VCDS-Cloud... <sigh>
- Joined
- Feb 25, 2014
- Messages
- 2,780
- Reaction score
- 4,490
- Location
- Cincinnati, OH
- VCDS Serial number
- C?ID=25607
Maybe. Step one of the adventure on this thread was figure out the intended design, because we didn't even know if we were looking at a bug. Now that we understand the design (whether or not we agree with it) we are in a better place.
I have only seen CFB and bootloader update once. I don't know what CFB does for us, but the bootloader was presumably updated in service of the USB updater tool. Given the low update frequency, irrelevance to OTA users, and the possibility of RMA-level oopsies when updating the bootloader, I don't really blame them for leaving it alone OTA at this time.
No, but I've got some Honey-Nut Cheerios here ready to go!
Er... do you really not have WiFi in your garage at home? Don't you have a WiFi camera in there?
Jason
I do, but it runs through 2 bridges and everything hides behind a single MAC address.
Works fine for hardwired camera and temperature sensor but nothing else.
Can't get close enough, even with OBD extenders, to get a decent signal from the house
If only HN had an RJ45 port... LOL
- Joined
- Feb 10, 2014
- Messages
- 207
- Reaction score
- 80
- Location
- Prescott, AZ
- VCDS Serial number
- C?ID=208765
I do, but it runs through 2 bridges and everything hides behind a single MAC address.
Works fine for hardwired camera and temperature sensor but nothing else.
Can't get close enough, even with OBD extenders, to get a decent signal from the house
If only HN had an RJ45 port... LOL
What about one from column A: http://tinyurl.com/oxv8esh maybe this one http://tinyurl.com/pbbscnc
and/or one from column B: http://tinyurl.com/q6gy5me
Last edited:
Actually, that was my original concept for it -- RJ45 ethernet and WiFi, no USB. However, the hardware people weren't keen on that.
-Uwe-
- Joined
- Feb 25, 2014
- Messages
- 2,780
- Reaction score
- 4,490
- Location
- Cincinnati, OH
- VCDS Serial number
- C?ID=25607
That probably wouldn't catch on fire, but unless HN has a USB OTG (host-mode) stack and a USB Ethernet driver and some means to configure a second interface, it's unlikely to do anything.
Jason
Ehhhh.... I'm pretty sure that was a joke.
Where there's gender benders, a cable can be devised.
Why would you design something that uses standards when you can use an ever changing, low bandwidth, driver riddled contrapticon ?
Now turn off your brain, put on your "Java is Wunnerful, Let's All Crash and Be Insecure!" dance party album and sing along like a good little sheeple.... <sigh>
- Joined
- Feb 10, 2014
- Messages
- 207
- Reaction score
- 80
- Location
- Prescott, AZ
- VCDS Serial number
- C?ID=208765
Like using this connector and a standard USB A to USB B cable. It looks like the data lines will go through but not power, however the HN gets power from the OBDII port right?
It wouldn't buy us anything.
I want ethernet, real ethernet like my Mac and everything else in the house is plugged into, instead of USB.
The only thing on WhyFi here is my iPhone, HEX-NET, and the link to the garage.
The garage will be replaced by cables in the next place in the Spring... I despise WhyFi.
Last edited:
- Joined
- Feb 10, 2014
- Messages
- 207
- Reaction score
- 80
- Location
- Prescott, AZ
- VCDS Serial number
- C?ID=208765
Won't this give you a complete cable route from your router in your house to your HN after you upgrade the garage:
Step 1: Plug the ETHERNET to USB A Female adapter into an RJ-45 jack in your garage.
Step 2: Plug the Male USB A end on the cable (included with the HN) into the Female USB A port on the adapter used in Step 1 above.
Step 3: Plug the Male USB B end on the cable used in Step 2 above into the Female USB B port on the HN.
True, it isn't 100% Cat 5e Ethernet cable, but it eliminates WiFi. You might even be able to use a long Cat 5e cable and an RJ-45 coupler for an interim cable connection from an R-45 port in your house to your garage; just coil it up when not in use.
Step 1: Plug the ETHERNET to USB A Female adapter into an RJ-45 jack in your garage.
Step 2: Plug the Male USB A end on the cable (included with the HN) into the Female USB A port on the adapter used in Step 1 above.
Step 3: Plug the Male USB B end on the cable used in Step 2 above into the Female USB B port on the HN.
True, it isn't 100% Cat 5e Ethernet cable, but it eliminates WiFi. You might even be able to use a long Cat 5e cable and an RJ-45 coupler for an interim cable connection from an R-45 port in your house to your garage; just coil it up when not in use.
Last edited:
- Status