2022 Icon programming cable

[jbloomfield]

So for the ESP32, it talks serial direct to the controller. The controller itself uses a NXP chip which uses the FreeMaster / MCB protocol. It's pretty simple from the comms side and each parameter is just a memory read or a write to set it. The trick is to know what memory address holds what value and what's worse the location of a parameter can change from one version of the software to the next. The nice thing is there's a block of fixed parameters which indicate what software version the controller is running and a version for the parameters which lets the control software change addresses based on the running version.

Anyway, in my case I have the ESP32 lock down the controller on power up so the cart won't move until it detects a bluetooth beacon from a known source. I'm just using a cheap Tile as the beacon and the ESP32 detects the presence and then unlocks the controller. I also have my phone as a known source, so it will unlock on that too. It's simple but effective.

[ATrain]

Originally Posted by jbloomfield

So for the ESP32, it talks serial direct to the controller. The controller itself uses a NXP chip which uses the FreeMaster / MCB protocol. It's pretty simple from the comms side and each parameter is just a memory read or a write to set it. The trick is to know what memory address holds what value and what's worse the location of a parameter can change from one version of the software to the next. The nice thing is there's a block of fixed parameters which indicate what software version the controller is running and a version for the parameters which lets the control software change addresses based on the running version.

Anyway, in my case I have the ESP32 lock down the controller on power up so the cart won't move until it detects a bluetooth beacon from a known source. I'm just using a cheap Tile as the beacon and the ESP32 detects the presence and then unlocks the controller. I also have my phone as a known source, so it will unlock on that too. It's simple but effective.

This sounds like it'd be an excellent thread to create with some how-to's. I'd never even heard of an ESP before so this sounds complex on the surface.

[BobInDaytona]

Originally Posted by jbloomfield

So for the ESP32, it talks serial direct to the controller. The controller itself uses a NXP chip which uses the FreeMaster / MCB protocol. It's pretty simple from the comms side and each parameter is just a memory read or a write to set it. The trick is to know what memory address holds what value and what's worse the location of a parameter can change from one version of the software to the next. The nice thing is there's a block of fixed parameters which indicate what software version the controller is running and a version for the parameters which lets the control software change addresses based on the running version.

Anyway, in my case I have the ESP32 lock down the controller on power up so the cart won't move until it detects a bluetooth beacon from a known source. I'm just using a cheap Tile as the beacon and the ESP32 detects the presence and then unlocks the controller. I also have my phone as a known source, so it will unlock on that too. It's simple but effective.

Just Curious - where did you get the info that revealed the NXP chip and protocol?

[jbloomfield]

Originally Posted by BobInDaytona

Just Curious - where did you get the info that revealed the NXP chip and protocol?

Just sniffing the traffic across the com port with IconLive connected. The first message it sends to the controller is a MCB_CMD_GETINFO which you guessed it, returns info about the controller. The response from the controller contained the text FreeMASTER when then lead me to https://www.nxp.com/design/software/...ool:FREEMASTER

From there it didn't take long to find the protocol documentation (MCB), which I compared to the traffic across the port to make sure it was correct.

[BobInDaytona]

Originally Posted by jbloomfield

Just sniffing the traffic across the com port with IconLive connected. The first message it sends to the controller is a MCB_CMD_GETINFO which you guessed it, returns info about the controller. The response from the controller contained the text FreeMASTER when then lead me to https://www.nxp.com/design/software/...ool:FREEMASTER

From there it didn't take long to find the protocol documentation (MCB), which I compared to the traffic across the port to make sure it was correct.

Figured it was something like that... Not having a cart makes it rather difficult to explore...

[rfagundo]

Hi Bobby. Do you make the adapter cable for sale?

[ATrain]

Originally Posted by rfagundo

Hi Bobby. Do you make the adapter cable for sale?

I think I'll have one available on Amazon soon. Anyone else can obviously sell them. I'm not trying to control the market or anything.

The hard part for any of these cables is mass producing them cheaply and distributing them easily.

I've got one finished prototype that I'm going to test next week and verify it works. If it does, I'll order 50-100 sets of components, which takes roughly 1- 2 weeks, then I'll send them to Amazon where it takes them 1-3 weeks to process.

If you want to wait for the one I'll sell on Amazon I'd guess roughly 20-45 days before you can 2-day order it.

Amazon can be slow to intake stuff. My prototype might not work. Few things could change that number though.

[rfagundo]

I bought the device Bobby suggested. And i have purchased the cables you had on Amazon last month before i understood they are for the 2021 models. Does your cable set require any modification that a layman can do?

[KRAZYMATT]

Originally Posted by ATrain

Yes I've confirmed it separately. I'm actually looking to see if I can get a custom cable made that would work for both with an attachment.

Small order quantities make it a pain though.

For now if you have a 2022, you'll have to make your own cable and buy the little device.

PM sent.

[KRAZYMATT]

Originally Posted by BobInDaytona

Attached are a couple of pictures of the cable I made.
One shows the pinout on the device, one shows the end of the cable, and one
is a hand drawing of which wire goes to which pin - the labels rx,tx,vcc,gnd match the labels on the circuit board on the device.
The 4 pin ribbon cable that is attached to the device comes with it...
This is the same molex connector that is used on the NEOS cable.

Bob does it have to use this FDI adapter or would a standard Serial to rs232 adapter work with a db9 connected with the mating molex connector?