Sponsored

FCSP RS485 port access Success!

ericpullen

Well-known member
First Name
Eric
Joined
Jan 4, 2022
Threads
31
Messages
269
Reaction score
490
Location
Louisville, KY
Vehicles
22 F-150 Lightning & 22 Mach-E
For everyone following along, I'm going to create a new thread about the code I've written to check the state of the FCSP. Right now that's the only valuable info I can gleam, but as we find more ways to use it, I'll update the code.
Sponsored

 

Aminorjourney

Well-known member
Joined
Jun 6, 2022
Threads
12
Messages
261
Reaction score
480
Location
Internet
Vehicles
vehicles that go
Time to dig this threat out of the cobwebs, in time for Halloween!

Had to do a 'brain transplant' today with our FCSP, as the one on the side of the house stopped connecting to wifi or advertising its Wifi.

I had a spare, so I swapped out the board and put the previous working unit (now broken) in my lab space (edit suite).

Swapping out the board took me about 45 minutes - but that did include filming a video about it for the channel. I'm going to be looking back on the threads written here, because I'd very much like to try and wake up this darned dead WiFi unit and figure out what's what.

In switching out the unit's main board though, I did notice something interesting, namely that boards have an SD card slot on the back. I wonder if that could be used to boatload fresh firmware? I'm about 95% sure this issue was caused by a software update gone wrong.
 

Ekiehn

Well-known member
First Name
Eric
Joined
Jan 8, 2023
Threads
1
Messages
140
Reaction score
127
Location
34997
Vehicles
2023 F-150 Lightning Latiat, 2008 Ford Explorer, 2006 Ford Escape Hybrid
Occupation
IT
Time to dig this threat out of the cobwebs, in time for Halloween!

Had to do a 'brain transplant' today with our FCSP, as the one on the side of the house stopped connecting to wifi or advertising its Wifi.

I had a spare, so I swapped out the board and put the previous working unit (now broken) in my lab space (edit suite).

Swapping out the board took me about 45 minutes - but that did include filming a video about it for the channel. I'm going to be looking back on the threads written here, because I'd very much like to try and wake up this darned dead WiFi unit and figure out what's what.

In switching out the unit's main board though, I did notice something interesting, namely that boards have an SD card slot on the back. I wonder if that could be used to boatload fresh firmware? I'm about 95% sure this issue was caused by a software update gone wrong.
Fantastic... you have inspired me to order a backup unit but also one that I can track down the biggest issue i.e. the week bluetooth signal. If I can track down the bluetooth signal and add the appropriate external antenna, I think 90 percent of issues would be solved..
 

Sponsored

Aminorjourney

Well-known member
Joined
Jun 6, 2022
Threads
12
Messages
261
Reaction score
480
Location
Internet
Vehicles
vehicles that go
Fantastic... you have inspired me to order a backup unit but also one that I can track down the biggest issue i.e. the week bluetooth signal. If I can track down the bluetooth signal and add the appropriate external antenna, I think 90 percent of issues would be solved..

I mean, the Bluetooth is probably on-chip on the A8.

BUT, I did break out my serial adapter, and we have some bad news. Like so many before me, I can't get into the thing to diagnose.

So, here's the boot log:

Code:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.126-g259f2e0422 (oe-user@oe-host) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11) ) #1 PREEMPT Wed May 18 21:18:56 UTC 2022
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt:Machine model: TI AM335x EVM-SK
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 48 MiB at 0xbd000000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] AM335X ES2.1 (neon)
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260416
[    0.000000] Kernel command line: console=ttyO0,115200n8 root=PARTUUID=d7921b5a-02 rw rootfstype=ext4 rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 976280K/1048576K available (8192K kernel code, 325K rwdata, 2772K rodata, 1024K init, 287K bss, 23144K reserved, 49152K cma-reserved, 212992K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0900000   (9184 kB)
[    0.000000]       .init : 0xc0c00000 - 0xc0d00000   (1024 kB)
[    0.000000]       .data : 0xc0d00000 - 0xc0d51568   ( 326 kB)
[    0.000000]        .bss : 0xc0d51568 - 0xc0d9941c   ( 288 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] OMAP clockevent source: timer2 at 24000000 Hz
[    0.000030] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000076] clocksource: timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000099] OMAP clocksource: timer1 at 24000000 Hz
[    0.000496] clocksource_probe: no matching clocksources found
[    0.000871] Console: colour dummy device 80x30
[    0.000936] Calibrating delay loop... 298.59 BogoMIPS (lpj=1492992)
[    0.067636] pid_max: default: 32768 minimum: 301
[    0.067898] Security Framework initialized
[    0.067982] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.068008] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.069764] CPU: Testing write buffer coherency: ok
[    0.070482] Setting up static identity map for 0x80100000 - 0x80100060
[    0.072568] EFI services will not be available.
[    0.076127] devtmpfs: initialized
[    0.107531] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.108429] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.108483] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.115438] pinctrl core: initialized pinctrl subsystem
[    0.118313] NET: Registered protocol family 16
[    0.122678] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.157778] omap_hwmod: debugss: _wait_target_disable failed
[    0.227721] cpuidle: using governor ladder
[    0.257704] cpuidle: using governor menu
[    0.273339] OMAP GPIO hardware version 0.1
[    0.312381] No ATAGs?
[    0.312426] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.378811] edma 49000000.edma: TI EDMA DMA engine driver
[    0.386850] SCSI subsystem initialized
[    0.387613] usbcore: registered new interface driver usbfs
[    0.387939] usbcore: registered new interface driver hub
[    0.388195] usbcore: registered new device driver usb
[    0.389060] omap_i2c 44e0b000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c0_pins, deferring probe
[    0.389175] omap_i2c 4802a000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c1_pins, deferring probe
[    0.389269] omap_i2c 4819c000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c2_pins, deferring probe
[    0.389575] pps_core: LinuxPPS API ver. 1 registered
[    0.389595] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[    0.389656] PTP clock support registered
[    0.391399] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400
[    0.393297] Bluetooth: Core ver 2.22
[    0.393421] NET: Registered protocol family 31
[    0.393442] Bluetooth: HCI device and connection manager initialized
[    0.393475] Bluetooth: HCI socket layer initialized
[    0.393503] Bluetooth: L2CAP socket layer initialized
[    0.393571] Bluetooth: SCO socket layer initialized
[    0.394491] clocksource: Switched to clocksource timer1
[    0.420823] NET: Registered protocol family 2
[    0.422467] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.422698] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.422916] TCP: Hash tables configured (established 8192 bind 8192)
[    0.423125] UDP hash table entries: 512 (order: 1, 8192 bytes)
[    0.423195] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
[    0.423530] NET: Registered protocol family 1
[    0.424419] RPC: Registered named UNIX socket transport module.
[    0.424449] RPC: Registered udp transport module.
[    0.424465] RPC: Registered tcp transport module.
[    0.424676] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.426629] hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available
[    0.432168] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.454014] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.458814] NFS: Registering the id_resolver key type
[    0.458905] Key type id_resolver registered
[    0.458925] Key type id_legacy registered
[    0.459036] ntfs: driver 2.1.32 [Flags: R/O].
[    0.472437] bounce: pool size: 64 pages
[    0.472948] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    0.472977] io scheduler noop registered
[    0.472996] io scheduler deadline registered
[    0.473366] io scheduler cfq registered (default)
[    0.477144] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.643728] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
[    0.652852] omap_uart 44e09000.serial: no wakeirq for uart0
[    0.653286] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 158, base_baud = 3000000) is a OMAP UART0
[    1.318271] console [ttyO0] enabled
[    1.323183] omap_uart 48024000.serial: no wakeirq for uart2
[    1.329601] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 159, base_baud = 3000000) is a OMAP UART2
[    1.340659] omap_uart 481a8000.serial: no wakeirq for uart4
[    1.346917] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 160, base_baud = 3000000) is a OMAP UART4
[    1.359304] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20
[    1.366611] [drm] Initialized
[    1.403669] brd: module loaded
[    1.423103] loop: module loaded
[    1.435170] libphy: Fixed MDIO Bus: probed
[    1.442796] QCA7000 probe start
[    1.446307] qcaspi spi1.0: ver=0.2.7-i, clkspeed=8000000, burst_len=5000, pluggable=0
[    1.454728] QCA7000 mode=3, clkspeed=8000000, irq=56, mac=00:01:87:08:21:54
[    1.462097] QCA7000 reading signature value
[    1.466740] QCA7000 reading signature Success
[    1.471351] Registering QCA7000 Device
[    1.476827] QCA7000 Registartion Success: eth0
[    1.483318] PPP generic driver version 2.4.2
[    1.488495] PPP BSD Compression module registered
[    1.493453] PPP Deflate Compression module registered
[    1.498863] PPP MPPE Compression module registered
[    1.503906] NET: Registered protocol family 24
[    1.508674] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[    1.516696] usbcore: registered new interface driver pegasus
[    1.522816] usbcore: registered new interface driver r8152
[    1.528803] usbcore: registered new interface driver asix
[    1.534669] usbcore: registered new interface driver ax88179_178a
[    1.541195] usbcore: registered new interface driver cdc_ether
[    1.547541] usbcore: registered new interface driver smsc75xx
[    1.553744] usbcore: registered new interface driver smsc95xx
[    1.559954] usbcore: registered new interface driver net1080
[    1.566071] usbcore: registered new interface driver cdc_subset
[    1.572409] usbcore: registered new interface driver zaurus
[    1.578510] usbcore: registered new interface driver cdc_ncm
[    1.586944] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.593817] ehci-pci: EHCI PCI platform driver
[    1.598726] ehci-platform: EHCI generic platform driver
[    1.604684] ehci-omap: OMAP-EHCI Host Controller driver
[    1.610419] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.617012] ohci-pci: OHCI PCI platform driver
[    1.621834] ohci-platform: OHCI generic platform driver
[    1.628777] usbcore: registered new interface driver cdc_acm
[    1.634795] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    1.643342] usbcore: registered new interface driver uas
[    1.649168] usbcore: registered new interface driver usb-storage
[    1.655803] usbcore: registered new interface driver usbserial
[    1.662035] usbcore: registered new interface driver usbserial_generic
[    1.669046] usbserial: USB Serial support registered for generic
[    1.675512] usbcore: registered new interface driver cp210x
[    1.681463] usbserial: USB Serial support registered for cp210x
[    1.687836] usbcore: registered new interface driver ftdi_sio
[    1.693972] usbserial: USB Serial support registered for FTDI USB Serial Device
[    1.701800] usbcore: registered new interface driver option
[    1.707811] usbserial: USB Serial support registered for GSM modem (1-port)
[    1.715273] usbcore: registered new interface driver pl2303
[    1.721225] usbserial: USB Serial support registered for pl2303
[    1.727597] usbcore: registered new interface driver qcserial
[    1.733734] usbserial: USB Serial support registered for Qualcomm USB modem
[    1.741198] usbcore: registered new interface driver sierra
[    1.747200] usbserial: USB Serial support registered for Sierra USB modem
[    1.754435] usbcore: registered new interface driver ti_usb_3410_5052
[    1.761346] usbserial: USB Serial support registered for TI USB 3410 1 port adapter
[    1.769536] usbserial: USB Serial support registered for TI USB 5052 2 port adapter
[    1.777807] usbcore: registered new interface driver usbtest
[    1.788403] 47401300.usb-phy supply vcc not found, using dummy regulator
[    1.817770] usbip_core: USB/IP Core v1.0.0
[    1.823879] i2c /dev entries driver
[    1.832031] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    1.840541] device-mapper: uevent: version 1.0.3
[    1.846439] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: [email protected]
[    1.855460] Bluetooth: HCI UART driver ver 2.3
[    1.860143] Bluetooth: HCI UART protocol H4 registered
[    1.865638] Bluetooth: HCI UART protocol LL registered
[    1.871891] cpu cpu0: OPP-v2 not supported, cpufreq-dt will attempt to use legacy tables.
[    1.881113] cpuidle: enable-method property 'ti,am3352' found operations
[    1.889232] sdhci: Secure Digital Host Controller Interface driver
[    1.895799] sdhci: Copyright(c) Pierre Ossman
[    2.055165] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.066312] usbcore: registered new interface driver usbhid
[    2.072183] usbhid: USB HID core driver
[    2.076705] omap_hsmmc 47810000.mmc: card claims to support voltages below defined range
[    2.086722] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    2.088509] ip_tables: (C) 2000-2006 Netfilter Core Team
[    2.089701] NET: Registered protocol family 10
[    2.099053] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    2.100822] NET: Registered protocol family 17
[    2.100932] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    2.101287] Bluetooth: RFCOMM TTY layer initialized
[    2.101317] Bluetooth: RFCOMM socket layer initialized
[    2.101378] Bluetooth: RFCOMM ver 1.11
[    2.101531] 8021q: 802.1Q VLAN Support v1.8
[    2.101626] Key type dns_resolver registered
[    2.102052] omap_voltage_late_init: Voltage driver support not added
[    2.125776] Key type encrypted registered
[    2.200376] random: fast init done
[    2.206976] mmc0: new high speed SDIO card at address 0001
[    2.214905] tps65910 0-002d: No interrupt support, no core IRQ
[    2.225339] vrtc: supplied by vbat
[    2.233530] vio: supplied by vbat
[    2.239374] vdd1: supplied by vbat
[    2.245714] vdd2: supplied by vbat
[    2.253574] vdig1: supplied by vbat
[    2.259471] vdig2: supplied by vbat
[    2.265271] vpll: supplied by vbat
[    2.271018] vdac: supplied by vbat
[    2.276837] vaux1: supplied by vbat
[    2.282663] vaux2: supplied by vbat
[    2.288520] vaux33: supplied by vbat
[    2.294415] vmmc: supplied by vbat
[    2.300225] vbb: supplied by vbat
[    2.306023] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[    2.314181] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 100 kHz
[    2.346321] bq32k 2-0068: Enabled trickle RTC battery charge.
[    2.354096] bq32k 2-0068: rtc core: registered bq32k as rtc0
[    2.360209] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz
[    2.384057] musb-hdrc musb-hdrc.0: MUSB HDRC host driver
[    2.389786] musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
[    2.398080] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.405293] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.412892] usb usb1: Product: MUSB HDRC host driver
[    2.418154] usb usb1: Manufacturer: Linux 4.9.126-g259f2e0422 musb-hcd
[    2.425054] usb usb1: SerialNumber: musb-hdrc.0
[    2.431625] hub 1-0:1.0: USB hub found
[    2.435840] hub 1-0:1.0: 1 port detected
[    2.558069] bq32k 2-0068: setting system clock to 2025-10-26 19:04:27 UTC (1761505467)
[    2.569241] vwl1837: disabling
[    2.572576] vdd2: disabling
[    2.581019] Waiting for root device PARTUUID=d7921b5a-02...
[    2.632483] mmc2: new high speed MMC card at address 0001
[    2.639802] mmcblk2: mmc2:0001 W62704 3.53 GiB
[    2.645331] mmcblk2boot0: mmc2:0001 W62704 partition 1 2.00 MiB
[    2.652159] mmcblk2boot1: mmc2:0001 W62704 partition 2 2.00 MiB
[    2.660778]  mmcblk2: p1 p2 p3
[    2.864779] EXT4-fs (mmcblk2p2): recovery complete
[    2.870779] EXT4-fs (mmcblk2p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.879479] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    2.890377] devtmpfs: mounted
[    2.897745] Freeing unused kernel memory: 1024K
[    3.225135] systemd[1]: systemd 234 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hy)
[    3.248420] systemd[1]: Detected architecture arm.

Welcome to Arago 2018.10!

[    3.286090] systemd[1]: Set hostname to <SWA452JF>.
[    3.592192] systemd-fstab-generator[106]: Checking was requested for "i/dev/root", but it is not a device.
[    4.301283] random: systemd: uninitialized urandom read (16 bytes read)
[    4.308826] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[    4.345061] random: systemd: uninitialized urandom read (16 bytes read)
[    4.352875] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[    4.394984] random: systemd: uninitialized urandom read (16 bytes read)
[    4.408342] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[    4.446049] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    4.485503] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    4.518174] systemd[1]: Created slice System Slice.
[  OK  ] Created slice System Slice.
[    4.558755] systemd[1]: Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Reached target Slices.
         Mounting Temporary Directory (/tmp)...
[  OK  ] Created slice system-getty.slice.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket.
         [    4.944762] usb 1-1: new high-speed USB device number 2 using musb-hdrc
Starting Remount Root and Kernel File Systems...
         Starting Journal Service...
         Starting Load Kernel Modules...
[    5.154003] EXT4-fs (mmcblk2p2): re-mounted. Opts: (null)
[  OK  ] Listening on Process Core Dump Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[    5.300580] cryptodev: loading out-of-tree module taints kernel.
[    5.337512] cryptodev: driver 1.9 loaded.
         Mounting Kernel Debug File System...
[    5.367006] usb 1-1: New USB device found, idVendor=0b95, idProduct=1790
[    5.374098] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
         Mounting POSIX Message Queue Fil[    5.427551] usb 1-1: Product: AX88179A
e System...
[    5.474935] usb 1-1: Manufacturer: ASIX
[    5.479009] usb 1-1: SerialNumber: 00A0CEC88FE230
[  OK  ] Mounted Kernel Debug File System.
[    5.560797] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0002: -32
[  OK  ] Mounted POSIX Message Queue File System.
[    5.593895] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0002: -32
[  OK  ] Mounted Temporary Directory (/tmp).
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Load Kernel Modules.
         Starting Apply Kernel Variables...
[    5.843174] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
         Mounting Kernel Configuration File System...
         Starting udev Coldplug all Devices...
[    6.002975] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x0006: -32
         Starting Create Static Device Nodes in /dev...
[    6.076710] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0005: -32
[    6.163105] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[  OK  ] Mounted Kernel Configuration File System.
[    6.214864] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[  OK  ] Started Apply Kernel Variables.
[    6.274174] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[    6.339312] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[    6.393137] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0002: -32
[  OK  ] Started Create Static Device Nodes in /dev.
[    6.444122] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[  OK  ] Started Journal Service.
[    6.475436] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0002: -32
[    6.512409] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x0001: -32
         Starting Flush Journal to Persistent Storage...
[    6.563420] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[    6.617255] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x001f: -32
         Starting udev Kernel Device Manager...
[    6.685411] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x0019: -32
[  OK  ] Reached target Local File Systems (Pre).
[    6.747105] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x001f: -32
[    6.800896] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x000d: -32
         Mounting /media/ram...
[    6.858138] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x000e: -32
         [    6.938254] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x000d: -32
Mounting /var/volatile...
[    7.003294] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x000e: -32
[    7.062674] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x000d: -32
[  OK  ] Mounted /media/ram.
[    7.116467] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x000e: -32
[  OK  ] Mounted /var/volatile.
[    7.161694] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x000d: -32
[  OK  ] Started udev Kernel Device Manager.
[    7.230682] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to write reg index 0x000e: -32
[    7.273068] ax88179_178a 1-1:2.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x0000: -32
[    7.319160] ax88179_178a 1-1:2.0 eth1: register 'ax88179_178a' at usb-musb-hdrc.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 76:00:3b:1a:5d:a4
[    7.408399] systemd-journald[116]: Received request to flush runtime journal from PID 1
         Starting Load/Save Random Seed...
[    7.478050] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0002: -32
[  OK  ] Reached target Local File Systems.
[    7.534214] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0002: -32
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Load/Save Random Seed.
[    7.812661] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
         Starting Create Volatile Files and Directories...
[    8.001860] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to read reg index 0x0006: -32
[    8.092942] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0005: -32
[    8.191028] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[    8.277803] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[    8.348999] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[    8.421681] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[    8.495609] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0002: -32
[  OK  ] Started Create Volatile Files and Directories.
[    8.563996] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[    8.647985] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0002: -32
         Starting Update UTMP about System Boot/Shutdown...
[    8.719187] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to read reg index 0x0001: -32
[    8.803163] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0001: -32
[    8.874204] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x001f: -32
[    8.952574] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x0019: -32
[    9.032200] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x001f: -32
[    9.092153] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x000d: -32
[    9.176155] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x000e: -32
[    9.241562] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x000d: -32
[    9.328363] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to read reg index 0x000e: -32
[    9.394099] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x000d: -32
[[    9.466709] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x000e: -32
  OK  ] Started Update UTMP about System Boot/Shutdown.
[    9.523537] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x000d: -32
[    9.611742] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to write reg index 0x000e: -32
[    9.658902] ax88179_178a 1-1:2.1 (unnamed net_device) (uninitialized): Failed to read reg index 0x0000: -32
[    9.730572] ax88179_178a 1-1:2.1 eth2: register 'ax88179_178a' at usb-musb-hdrc.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 76:00:3b:1a:5d:a4
[   10.689486] usb 1-1: USB disconnect, device number 2
[   10.711282] ax88179_178a 1-1:2.0 eth1: unregister 'ax88179_178a' usb-musb-hdrc.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet
[   10.774984] ax88179_178a 1-1:2.0 eth1 (unregistered): Failed to write reg index 0x0002: -19
[   10.783878] ax88179_178a 1-1:2.0 eth1 (unregistered): Failed to write reg index 0x0001: -19
[   10.835012] ax88179_178a 1-1:2.0 eth1 (unregistered): Failed to write reg index 0x0002: -19
[   10.855326] ax88179_178a 1-1:2.1 eth2: unregister 'ax88179_178a' usb-musb-hdrc.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet
[   10.914940] ax88179_178a 1-1:2.1 eth2 (unregistered): Failed to write reg index 0x0002: -19
[   10.923775] ax88179_178a 1-1:2.1 eth2 (unregistered): Failed to write reg index 0x0001: -19
[   10.964988] ax88179_178a 1-1:2.1 eth2 (unregistered): Failed to write reg index 0x0002: -19
[   11.624723] usb 1-1: new high-speed USB device number 3 using musb-hdrc
[   11.949091] usb 1-1: New USB device found, idVendor=0b95, idProduct=1790
[   11.964592] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   11.972167] usb 1-1: Product: AX88179A
[   11.994664] usb 1-1: Manufacturer: ASIX
[   11.998763] usb 1-1: SerialNumber: 00A0CEC88FE230
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Reached target System Initialization.
[   12.718021] ax88179_178a 1-1:1.0 (unnamed net_device) (uninitialized): Failed to read reg index 0x0040: -32
         Starting sshd.socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
         Starting Network Service...
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[   13.088309] ax88179_178a 1-1:1.0 eth1: register 'ax88179_178a' at usb-musb-hdrc.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 6c:6e:07:1e:c2:6a
[  OK  ] Listening on sshd.socket.
[   13.925226] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc1
[  OK  ] Found device /dev/ttyO0.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Login Service...
         Starting Network Time Service (one-shot ntpdate mode)...
         Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started A userspace daemon that run…ns under the eCryptfs mount point.
[  OK  ] Reached target Containers.
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Periodic Command Scheduler.
         Starting LSB: System logger...
[  OK  ] Started Network Service.
[  OK  ] Started Network Time Service (one-shot ntpdate mode).
[   18.559461] remoteproc remoteproc0: wkup_m3 is available
[   18.926136] remoteproc remoteproc0: powering up wkup_m3
[   18.982506] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 224708
[   19.145091] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x192
[   19.152370] remoteproc remoteproc0: remote processor wkup_m3 is now up
[   20.075861] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   20.082298] eth0: SPI thread created
[   21.022349] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[   21.117285] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[   21.171983] omap-aes 53500000.aes: will run requests pump with realtime priority
[   21.204842] QCA7000 Reading signature
[   21.204910] QCA7000 read signature Pass
[   21.204943] QCA7000 sync Success
[   21.205229] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Login Service.
[FAILED] Failed to start LSB: System logger.
See 'systemctl status syslog.service' for details.
         Starting drivers.service...
         Starting evse-startup.service...
[  OK  ] Reached target Network.
         Starting Network Time Service...
         Starting Permit User Sessions...
         Starting DNS forwarder and DHCP server...
         Starting Network Name Resolution...
[  OK  ] Started Permit User Sessions.
[  OK  ] Started DNS forwarder and DHCP server.
[  OK  ] Started Network Time Service.
[   24.808773] reset_miscdev.minor=55
[   24.841903] reset driver prm[2]: 0x00000001
[   24.884715] reset driver scratch: 0x00000000
[   24.889239] reset driver scratch verify: 0xAAAA5555
[   24.894367] reset driver prm[2]: 0x00000000
[   25.029357] reset driver ret=0
[  OK  ] Started Network Name Resolution.
[   25.782181] gpio_miscdev.minor=54
[   25.804696] FactoryReset state is currently: 1
[   25.809401] Button: The button is mapped to IRQ: 97
[   25.892466] ret=0
[   25.895918] Flash Thread has started running
[  OK  ] Started drivers.service.
[   27.001229] open from factory_reset.s
[   27.073885] Request from user: reset
[   27.099377] release from factory_reset.s
[   28.107982] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl1271-nvs.bin failed with error -2
[   28.466314] ax88179_178a 1-1:1.0 eth1: Failed to read reg index 0x0040: -32
[   28.576457] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   28.809394] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   28.861075] wlcore: loaded
[   29.785678] wlcore: PHY firmware version: Rev 8.2.0.0.245
[   29.940854] wlcore: firmware booted (Rev 8.9.0.0.88)
[   30.016099] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   30.748589] EXT4-fs (mmcblk2p3): recovery complete
[   30.765483] EXT4-fs (mmcblk2p3): mounted filesystem with ordered data mode. Opts: (null)
[*     ] A start job is running for evse-startup.service (27s / 5min 18s)[   32.124740] random: crng init done
[   32.128376] random: 7 urandom warning(s) missed due to ratelimiting
         Starting helios_service.service...
[  OK  ] Reached target Host and Network Name Lookups.
         Starting The NGINX HTTP and reverse proxy server...
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyO0.
[  OK  ] Reached target Login Prompts.
         Starting Synchronize System and HW clocks...
[  OK  ] Started helios_service.service.
[  OK  ] Started Synchronize System and HW clocks.
         Starting Time & Date Service...
[  OK  ] Started Time & Date Service.
[  OK  ] Started evse-startup.service.
         Starting LSB: background process to monitor the wifi connection...
[  OK  ] Started The NGINX HTTP and reverse proxy server.


####### #     #  #####  #######
#       #     # #     # #
#       #     # #       #
#####   #     #  #####  #####
#        #   #        # #
#         # #   #     # #
#######    #     #####  #######


FIRMWARE_VERSION: 4.1.0.AB
SWA452JF login: [   58.532195] open from python
[   58.541467] Request from user: blue off
[   58.564702] Red set to OFF
[   58.568352] Request from user: green slow flash
[   58.573141] Green set to FLASH
[   58.584895] Request from user: red slow flash
[   58.589512] Red set to FLASH
[   58.605269] open from python
[   58.608496] read from python
[   58.644898] release from python
[   94.924119] NET: Registered protocol family 38
and it does show some interesting things:

1) It does see the Ethernet adapter I have plugged in - yay! (As others have found, you can *see* the device show up on the network, it shows up in the Charge Station Pro setup app, but you can't use the connection to do anything. Additionally, the IP address in a browser of the Ethernet adapter gives you a web page, but it's all errors due to a lack of authentication (which I think is down to how its NGINX reverse proxy is configured).

2) There's certainly an issue with the wifi:

Code:
[   28.107982] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl1271-nvs.bin failed with error -2
[   28.466314] ax88179_178a 1-1:1.0 eth1: Failed to read reg index 0x0040: -32
[   28.576457] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   28.809394] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Now, there are two explanations for this: a) I reset the firmware (and the non-volatile file mentioned doesn't exist because it's been reset - most likely)

or b) There's just something weird going on with the wifi chip.

3) Later on, the wifi loads..., making me think 2) is just a normal response when the factory reset happens.

Code:
[   28.861075] wlcore: loaded
[   29.785678] wlcore: PHY firmware version: Rev 8.2.0.0.245
[   29.940854] wlcore: firmware booted (Rev 8.9.0.0.88)
[   30.016099] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   30.748589] EXT4-fs (mmcblk2p3): recovery complete
[   30.765483] EXT4-fs (mmcblk2p3): mounted filesystem with ordered data mode. Opts: (null)
[*     ] A start job is running for evse-startup.service (27s / 5min 18s)[   32.124740] random: crng init done
[   32.128376] random: 7 urandom warning(s) missed due to ratelimiting
         Starting helios_service.service...
[  OK  ] Reached target Host and Network Name Lookups.
         Starting The NGINX HTTP and reverse proxy server...
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyO0.
[  OK  ] Reached target Login Prompts.
         Starting Synchronize System and HW clocks...
[  OK  ] Started helios_service.service.
[  OK  ] Started Synchronize System and HW clocks.
         Starting Time & Date Service...
[  OK  ] Started Time & Date Service.
[  OK  ] Started evse-startup.service.
         Starting LSB: background process to monitor the wifi connection...
[  OK  ] Started The NGINX HTTP and reverse proxy server.
The wifi does load its firmware, and does connect, but isn't linked because it's not been set up or associated with anything - and it does load a background process to monitor the wifi. However, I don't *see* any WAP appear.

BUT there's no wifi access point.

I'm going to go and take my frustration out on a piece of metal... and just leave it power up on the bench to see if it actually brings the wifi access up - but I don't hold much hope.
 

Aminorjourney

Well-known member
Joined
Jun 6, 2022
Threads
12
Messages
261
Reaction score
480
Location
Internet
Vehicles
vehicles that go
Still hoping someone can crack enabling DC output so it can be used without the flustercluck of defunct equipment entirely 😛
Honestly, there are better products now in the field. Patrick and Liv (don't think they're on this forum) from The Electric Duo did a video just before their trip to Munich in which they did V2G with their MME. Pretty sure that would work with the Lightning too.



And this system is DC charging/Discharging. Yes, I'm guessing it's going to be expensive, but seems to be reliable and follows official standards (which the FCSP and Home Integration System don't, AFAIK)

I'll ping them and see if they can add anything else to the info ;)
 
  • Like
Reactions: chl

Mach-E_Vlog

Active member
First Name
Patrick
Joined
Jun 21, 2022
Threads
4
Messages
25
Reaction score
24
Location
Oceanside, CA
Website
theelectricduo.com
Vehicles
Mustang Mach-E
Honestly, there are better products now in the field. Patrick and Liv (don't think they're on this forum) from The Electric Duo did a video just before their trip to Munich in which they did V2G with their MME. Pretty sure that would work with the Lightning too.



And this system is DC charging/Discharging. Yes, I'm guessing it's going to be expensive, but seems to be reliable and follows official standards (which the FCSP and Home Integration System don't, AFAIK)

I'll ping them and see if they can add anything else to the info ;)
We didn't get to see them use it with a Lightning, but they have tested it. A couple of weeks ago, we visited another house for a Signergy demo. They demonstrated the system working with a Mach-E, Gen 1 and Gen 2 Rivian, a CyberTruck, a 2017 Model X with CCS upgrade, and a Kia Niro. We'll have a video on that soon (it was a hectic day, so editing that video is a bear).

I think the only brand giving them problems right now is GM. Once it starts discharging, the GM software shuts it down after about 30 seconds.

The system seems just so flexible and versatile. You can tie it into a system that has no solar, or AC solar, or DC solar. I hope we see more systems that work with multiple brands.
 

Aminorjourney

Well-known member
Joined
Jun 6, 2022
Threads
12
Messages
261
Reaction score
480
Location
Internet
Vehicles
vehicles that go
Did some more digging.

TLDR: I don't think we can interrupt the boot process to try and circumvent the stock login requirement.

I was able to get the MCU UART spitting out something, but all I see is the

Code:
******* Self Test Library Init BOOTLOADER 
******* Start-up CPU Test OK Start-up 
FLASH 32-bit CRC OK 
Control Flow Checkpoint 1 OK 
Full RAM Test OK 
Clock frequency OK 
Control Flow Checkpoint 2 OK 

******* Self Test Library Init Application 
******* Start-up CPU Test OK Pin 
reset IWDG reset WWDG reset ... WWDG reset, WDG test completed ... 
Start-up FLASH 32-bit CRC OK 
Control Flow Checkpoint 1 OK 
Full RAM Test OK 
Clock frequency OK 
Control Flow Checkpoint 2 OK 

** Siemens Industry Inc. Copyright 2018-19 *
* Diagnostics - VersiChargeSG Version 5.0.25 
** Required Bootloader Version 1.3 or Above 
HELP: H 
Lock Front Panel: LCKFP [<None>|LOCK|UNLK <key>] 
Start BootLoader: STARTBL STF>
Last reset type : Performing the Power ON self test 
..... Metering Chip Firmware Version is: 4 49 1 
STF>EEPROM self test success 
FRAM self test success Meter chip self test success 
USNAP self test SuccessPin reset
However, if you bridge the RS485 SEL switch, you can get additional info - but you can't give the system an alternative boot option.

Code:
** Siemens Industry Inc. Copyright 2018-19
** Diagnostics - VersiChargeSG Version 5.0.25 
** Required Bootloader Version 1.3 or Above 
HELP: H 
Lock Front Panel: LCKFP [<None>|LOCK|UNLK <key>] 
Start BootLoader: STARTBL 

STF>Last reset type : Performing the Power ON self test ..... 

Metering Chip Firmware Version is: 4 49 1 
STF>EEPROM self test success 

FRAM self test success 
Meter chip self test success 
USNAP self test Success 
Firmware CRC (calculated,Reference): C8698697, C8698697 Dev ID: 469, Rev ID: 2003 Command interpreter locked
It's not *unusual* to get this, but aside from me physically trying to read the memory and do a dump for further analysis, I'm not sure what else to do.
 
OP
OP

cjueden

Member
Joined
May 29, 2024
Threads
2
Messages
20
Reaction score
16
Location
USA
Vehicles
23 ER XLT
Have you tried the "DEBUG UART" connection to see if there's any output.
I haven't had time to get back to this yet.
 

Sponsored

Aminorjourney

Well-known member
Joined
Jun 6, 2022
Threads
12
Messages
261
Reaction score
480
Location
Internet
Vehicles
vehicles that go
Have you tried the "DEBUG UART" connection to see if there's any output.
I haven't had time to get back to this yet.
Yup.

Debug UART gives you output from the A8 chip - which is *post* boot.

You get the usual linux boot messages scrolling by, then a login prompt. But again, without login, nada.
 
OP
OP

cjueden

Member
Joined
May 29, 2024
Threads
2
Messages
20
Reaction score
16
Location
USA
Vehicles
23 ER XLT
Im sorry it's been a while since I looked at this. I ment the MTR_CON
 

chl

Well-known member
First Name
CHRIS
Joined
Dec 16, 2022
Threads
7
Messages
2,074
Reaction score
1,262
Location
alexandria virginia
Vehicles
2001 FORD RANGER, 2023 F-150 LIGHTNING
Honestly, there are better products now in the field. Patrick and Liv (don't think they're on this forum) from The Electric Duo did a video just before their trip to Munich in which they did V2G with their MME. Pretty sure that would work with the Lightning too.



And this system is DC charging/Discharging. Yes, I'm guessing it's going to be expensive, but seems to be reliable and follows official standards (which the FCSP and Home Integration System don't, AFAIK)

I'll ping them and see if they can add anything else to the info ;)
SigEnergy Sigen EVDC V2X Module Bidirectional DC Charger | 150~1000V | 25kW Bi-directional Charging | V2H V2G | Wide EV Compatibility
Vendor: PointGuard Energy
SKU: S-SigenV2XS1-US
Availability : In Stock
  • V2X ready technology, future proof
  • Max. 25 kW bi-directional charging
  • 150V~1000V charging, wide EV compatibility
  • Charge EV with solar power
  • Track charging on myPointGuard App
  • NEMA 4X system enclosure

$3,599.00 Save $2,819.00


https://www.self2solar.com/products...ficate-cec-listed-copy?variant=50768981721363
 

tearitupsports

Well-known member
First Name
Russell
Joined
Jun 1, 2024
Threads
8
Messages
327
Reaction score
301
Location
Houston, TX
Vehicles
2023 F-150 Lightning Lariat ER
Occupation
Industrial Automation & Controls
SigEnergy Sigen EVDC V2X Module Bidirectional DC Charger | 150~1000V | 25kW Bi-directional Charging | V2H V2G | Wide EV Compatibility
Vendor: PointGuard Energy
SKU: S-SigenV2XS1-US
Availability : In Stock
  • V2X ready technology, future proof
  • Max. 25 kW bi-directional charging
  • 150V~1000V charging, wide EV compatibility
  • Charge EV with solar power
  • Track charging on myPointGuard App
  • NEMA 4X system enclosure

$3,599.00 Save $2,819.00


https://www.self2solar.com/products...ficate-cec-listed-copy?variant=50768981721363
Just to advise that this requires a few other components to work. It is not a stand alone product. It is an amazing system though. I am reinstalling the extra electrical this week and should have the V2X module within about 3 weeks.
 
  • Like
Reactions: chl

chl

Well-known member
First Name
CHRIS
Joined
Dec 16, 2022
Threads
7
Messages
2,074
Reaction score
1,262
Location
alexandria virginia
Vehicles
2001 FORD RANGER, 2023 F-150 LIGHTNING
Just to advise that this requires a few other components to work. It is not a stand alone product. It is an amazing system though. I am reinstalling the extra electrical this week and should have the V2X module within about 3 weeks.
When you get it all done, post some pics!

And gives us the bottom line cost too, if you don't mind.

If my budget allows I might go for it.

I am set up with a manual transfer switch and the PPOB (240V 30A outlet in bed) which was very economical, but integrating solar, battery, V2X is interesting.
Sponsored

 
 







Top